WO2024114192A1 - Quality of service management method and apparatus - Google Patents

Abstract

The present application discloses a quality of service management method and apparatus. The method is applied to a data analysis functional entity, and comprises: receiving first service experience information of a latency- and/or reliability-sensitive service from an application functional entity or a terminal device; and receiving first service transmission information of the latency- and/or reliability-sensitive service from a first network entity, and sending a quality of service management policy to a second network entity according to the first service experience information, the first service transmission information, and service experience demand information of the latency- and/or reliability-sensitive service, for instructing the second network entity to modify or adjust a resource configuration policy or parameter configuration, so that the difference between second service experience information of the latency- and/or reliability-sensitive service and the service experience demand information falls within a preset threshold range. Embodiments of the present application provide processes of a quality of service management method of a latency- and/or reliability-sensitive service, achieving effective management of the quality of service.

Description

Service quality management method and device

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on November 30, 2022, with application number 202211520999.3 and invention name “Business Quality Management Method and Device”, the entire contents of which are incorporated by reference in this application.

Technical Field

The present application relates to the field of wireless communication technology, and in particular to a service quality management method and device.

Background technique

Quality of experience (QoE) is the user experience or user perception of the service performance provided by the mobile network by the end user, mainly referring to the user's satisfaction with the network. Key quality indicators (KQI) (or QoE indicators) are service quality parameters characterized from different dimensions of user experience, such as the page display or file transfer speed, audio quality, image quality, video continuity, audio/video synchronization, etc. that users should achieve in network services. The QoE level information (such as very good, good, average, poor, and very poor) can be evaluated through the weighted calculation of KQI.

QoS (Quality of Service) is the management and differentiation of services provided from the perspective of the network. Network entities handle different services according to different quality requirements. It can be understood as performance indicators of data transmission, such as latency, jitter, bandwidth, bit error, etc. Key performance indicators (KPI) are mainly based on the description of the performance of network elements and other equipment at the network level. They are composed of a set of parameter data that can be monitored and measured. They are the measurement methods used by operators to manage the network, such as commonly used accessibility and mobility. QoS and KPI affect the end-user's quality of experience QoE from the network level.

For latency and/or reliability-sensitive services, such as ultra-reliable and low-latency communication (URLLC) services, better management of service quality requires meeting their low-latency and/or high-reliability service experience requirements. How to implement the service quality management process for such services is a technical problem that needs to be solved urgently.

Summary of the invention

The embodiments of the present application provide a service quality management method and device, which realizes effective management of the service quality of delay and/or reliability sensitive services by providing a service quality management method process for such services.

In a first aspect, a service quality management method is provided, which is applied to a data analysis function entity, the method comprising: receiving first service experience information of a delay and/or reliability sensitive service from an application function entity or a terminal device, and receiving first service transmission information of a delay and/or reliability sensitive service from a first network entity, the first service experience information being a quality parameter that affects the user's perception of the delay and/or reliability sensitive service, and the first service transmission information being measurement information that characterizes service transmission performance during the transmission of the delay and/or reliability sensitive service; sending a service quality management policy to a second network entity according to the first service experience information, the first service transmission information, and service experience requirement information corresponding to the delay and/or reliability sensitive service; wherein the service quality management policy is used to instruct the second network entity to modify or adjust a resource configuration policy or parameter configuration of the delay and/or reliability sensitive service, so that the difference between the second service experience information and the service experience requirement information of the delay and/or reliability sensitive service after the modification or adjustment operation is within a preset threshold range.

It can be seen that in the embodiment of the present application, for delay and/or reliability sensitive services, the first service experience information is obtained from the application function or terminal device through the data analysis function entity, and the first service transmission information is obtained from the first network entity, and then a service quality management policy is generated according to the first service experience information, the service experience requirement information of the delay and/or reliability sensitive service and the first service transmission information, and the service quality management policy is sent to the second network entity, and the resource configuration policy or parameter configuration of the delay and/or reliability sensitive service is modified or adjusted through the service quality management policy, so that the re-acquired second service experience information can meet the requirements of the service experience requirement information as much as possible. This process provides method steps for service quality management of delay and/or reliability sensitive services, and ensures the effectiveness of service quality management of delay and/or reliability sensitive services.

In combination with the first aspect, in one possible design, the service experience information of delay and/or reliability sensitive services includes delay parameters and reliability parameters.

In combination with the first aspect, in one possible design, the delay parameter includes one or more of the following: transmission delay, escape delay, interaction delay, round-trip time (RTT) jitter, packet interval, or interruption rate.

In combination with the first aspect, in one possible design, the first service transmission information includes service quality QoS measurement information of delay and/or reliability sensitive services; or the first service transmission information also includes network performance measurement information corresponding to delay and/or reliability sensitive services.

In combination with the first aspect, in a possible design, the data analysis functional entity is an enhanced management data analysis service eMDAS.

In combination with the first aspect, in one possible design, the first network entity includes a core network network slice subnet management function entity CN NSSMF, and/or an access network network slice subnet management function entity RAN NSSMF; and/or

The first network entity includes a network slice management function entity NSMF; and/or

The first network entity includes a network data analysis function entity NWDAF.

In combination with the first aspect, in one possible design, the second network entity includes CN NSSMF and/or RAN NSSMF, or the second network entity also includes NSMF.

In combination with the first aspect, in one possible design, the data analysis functional entity is a network data analysis functional entity NWDAF.

In combination with the first aspect, in a possible design, the first network entity is a user plane function entity UPF; and/or the second network entity is a policy control function entity PCF.

In combination with the first aspect, in one possible design, modifying or adjusting the resource configuration strategy of the delay and/or reliability sensitive service includes at least one of the following: turning on or off a specific resource strategy switch, increasing or decreasing the number of redundant retransmission links or the number of retransmissions in the radio access network RAN or the core network CN; and/or

Modifying or adjusting the parameter configuration of delay and/or reliability sensitive services includes at least one of the following: modifying the number or location information of reserved resources, modifying the CN bandwidth resource configuration, modifying the wireless resource configuration, activating the resource pre-scheduling strategy, increasing the number and resources of pre-scheduled resources, or modifying the terminal device UE switching strategy.

In combination with the first aspect, in one possible design, modifying or adjusting the resource allocation strategy of delay and/or reliability sensitive services includes modifying the routing selection strategy; modifying or adjusting the parameter configuration of delay and/or reliability sensitive services includes modifying the QoS requirement information of delay and/or reliability sensitive services.

In a second aspect, a communication device is provided, the communication device comprising a module or unit for implementing the method of the first aspect and any possible design thereof. The module or unit may be a hardware circuit, or software, or a combination of a hardware circuit and software. The device may include:

A transceiver unit, configured to receive first service experience information of a delay and/or reliability sensitive service from an application function entity or a terminal device, and receive first service transmission information of a delay and/or reliability sensitive service from a first network entity, wherein the first service experience information is a quality parameter that affects a user's perception of a delay and/or reliability sensitive service, and the first service transmission information is measurement information characterizing service transmission performance during transmission of a delay and/or reliability sensitive service;

A processing unit is used to send a service quality management policy to a second network entity based on the first service experience information, the first service transmission information and the service experience requirement information corresponding to the delay and/or reliability sensitive service; wherein the service quality management policy is used to instruct the second network entity to modify or adjust the resource configuration policy or parameter configuration of the delay and/or reliability sensitive service, so that the difference between the second service experience information and the service experience requirement information of the delay and/or reliability sensitive service after the modification or adjustment operation is within a preset threshold range.

In combination with the second aspect, in one possible design, the service experience information of delay and/or reliability sensitive services includes delay parameters and reliability parameters.

In combination with the second aspect, in one possible design, the delay parameters include one or more of the following: transmission delay, escape delay, interaction delay, round-trip time (RTT) jitter, packet interval, or interruption rate.

In combination with the second aspect, in one possible design, the first service transmission information includes service quality QoS measurement information of delay and/or reliability sensitive services; or the first service transmission information also includes network performance measurement information corresponding to delay and/or reliability sensitive services.

In combination with the second aspect, in one possible design, the data analysis functional entity is an enhanced management data analysis service eMDAS.

In combination with the second aspect, in one possible design, the first network entity includes a core network network slice subnet management function entity CN NSSMF, and/or an access network network slice subnet management function entity RAN NSSMF; and/or

The first network entity includes a network slice management function entity NSMF; and/or

The first network entity includes a network data analysis function entity NWDAF.

In combination with the second aspect, in one possible design, the second network entity includes CN NSSMF and/or RAN NSSMF, or the second network entity also includes NSMF.

In combination with the second aspect, in one possible design, the data analysis functional entity is a network data analysis functional entity NWDAF.

In combination with the second aspect, in a possible design, the first network entity is a user plane function entity UPF; and/or the second network entity is a policy control function entity PCF.

In combination with the second aspect, in one possible design, modifying or adjusting the resource configuration strategy of the delay and/or reliability sensitive service includes at least one of the following: turning on or off a specific resource strategy switch, increasing or decreasing the number of redundant retransmission links or the number of retransmissions in the radio access network RAN or the core network CN; and/or

Modifying or adjusting the parameter configuration of delay and/or reliability sensitive services includes at least one of the following: modifying the number or location information of resource reservations, Modify CN bandwidth resource configuration, modify radio resource configuration, activate resource pre-scheduling strategy, increase the number and resources of pre-scheduling resources, or modify terminal device UE switching strategy.

In combination with the second aspect, in one possible design, modifying or adjusting the resource allocation strategy of delay and/or reliability sensitive services includes modifying the routing selection strategy; modifying or adjusting the parameter configuration of delay and/or reliability sensitive services includes modifying the QoS requirement information of delay and/or reliability sensitive services.

According to a third aspect, a communication device is provided, comprising a processor, wherein the processor is configured to execute the method described in the first aspect or any aspect of the first aspect and possible designs thereof by executing computer instructions or by a logic circuit.

In one possible design, the communication device includes a memory for storing computer instructions. Optionally, the memory is integrated with the processor.

In one possible design, the communication device also includes a transceiver, which is used to receive and/or send signals, and the signal can carry signaling or data.

In a fourth aspect, an embodiment of the present application provides a chip system, comprising: a processor, the processor is coupled to a memory, the memory is used to store programs or instructions, when the program or instructions are executed by the processor, the chip system implements the method of the above-mentioned first aspect or any aspect of the first aspect.

Optionally, the chip system also includes an interface circuit for interacting computer instructions with the processor.

Optionally, there may be one or more processors in the chip system, and the processor may be implemented by hardware or software. When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc. When implemented by software, the processor may be a general-purpose processor implemented by reading software code stored in a memory.

Optionally, the memory in the chip system may be one or more. The memory may be integrated with the processor or may be separately provided with the processor, which is not limited in the present application. Exemplarily, the memory may be a non-transient processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip or may be provided on different chips. The present application does not specifically limit the type of memory and the arrangement of the memory and the processor.

In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program or instructions stored thereon. When the computer program or instructions are executed, the computer executes the method of the first aspect or any aspect of the first aspect.

In a sixth aspect, an embodiment of the present application provides a computer program product. When a computer reads and executes the computer program product, the computer executes the method in the above-mentioned first aspect or any possible implementation manner of the first aspect.

In a seventh aspect, an embodiment of the present application provides a communication system, which includes the device of the second aspect mentioned above.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments are briefly introduced below.

FIG1 is a schematic diagram of the structure of an eMDAS and NWDAF provided in an embodiment of the present application;

FIG2 is a schematic diagram of an interaction process between NWDAF and AF provided in an embodiment of the present application;

FIG3 is a flow chart of a service quality management method provided in an embodiment of the present application;

FIG4A is a schematic diagram of a data analysis function entity communication architecture provided in an embodiment of the present application;

FIG4B is a schematic diagram of another data analysis function entity communication architecture provided in an embodiment of the present application;

FIG4C is a schematic diagram of another data analysis function entity communication architecture according to an embodiment of the present application;

FIG5A is a flow chart of another service quality management method provided in an embodiment of the present application;

FIG5B is a flow chart of another service quality management method provided in an embodiment of the present application;

FIG6 is a structural block diagram of a communication device provided in an embodiment of the present application;

FIG. 7 is a schematic diagram of the hardware structure of a communication device in an embodiment of the present application.

Detailed ways

The terms "first", "second", "third" and "fourth" etc. in the specification and claims of the present application and the drawings 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 optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

Reference to "embodiment" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiment may be included in at least one embodiment of the present application. The appearance of the phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive of other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments. Combined with examples.

"Multiple" means two or more. "And/or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character "/" generally indicates that the related objects are in an "or" relationship.

First, the professional terms involved in the embodiments of the present application are introduced.

Terminal: A mobile device that supports 5G NR, which can specifically refer to user equipment (UE), access terminal, subscriber unit, user station, mobile station, customer-premises equipment (CPE), remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent or user device. The terminal device can also be a satellite phone, a cellular phone, a smart phone, a wireless data card, a wireless modem, a machine type communication device, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a communication device carried on a high-altitude aircraft, a wearable device, a drone, a robot, a smart point of sale (POS) machine, a terminal in device-to-device communication (D2D), a vehicle-to-everything This application does not limit the terminals in vehicle to everything (V2X), virtual reality (VR) terminal equipment, augmented reality (AR) terminal equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home or terminal equipment in future communication network, etc.

5G base station: refers to the radio access network (RAN) node (or device) in the 5G network that connects the terminal to the wireless network. It can also be called access network equipment, network equipment, or evolved node B (gNB). It mainly provides wireless access services, schedules wireless resources to access terminals, and provides reliable wireless transmission protocols and data encryption protocols. Network equipment can be a node in the wireless access network, which can also be called a base station or a RAN node (or device). The network equipment can be an evolved Node B (eNB or eNodeB) in LTE; or a next generation node B (gNB) in a 5G network or a base station in a future evolved public land mobile network (PLMN), a broadband network gateway (BNG), an aggregation switch, or a non-3rd generation partnership project (3GPP) access device. Optionally, the network equipment in the embodiments of the present application may include various forms of base stations, such as: macro base stations, micro base stations (also called small stations), relay stations, access points, devices that implement base station functions in communication systems that evolve after 5G, transmission points (transmitting and receiving points, TRP), transmitting points (transmitting points, TP), mobile switching centers, and devices that assume base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, etc., and may also include centralized units (CU) and distributed units (DU) in cloud access network (C-RAN) systems, and network equipment in NTN communication systems, that is, they can be deployed on high-altitude platforms or satellites. The embodiments of the present application do not specifically limit this.

5G core network: refers to the equipment in the core network (CN) that provides service support for terminal devices in the 5G network. It is used for user access control, mobility management, session management, user security authentication, billing and other services. It consists of multiple functional units, which can be divided into management plane functional entities, control plane functional entities and data plane (user plane) functional entities. The control plane functional entities include, for example, the policy control function (PCF), which is used to provide policy rules to the system control plane function. The management plane functional entities include, for example, the session management function (SMF), which is used for session management; the access and mobility management function (AMF), which is used for access and mobility management, including registration management, mobility management, access authentication, etc. The user plane functional entities include, for example, the user plane function (UPF), which is used for packet routing and forwarding, packet detection, execution of user plane policy rules, allocation of IP addresses for terminal devices, etc.

Network Slice Management Function (NSMF): is a management plane functional entity. It can be used to manage the life cycle of network slices, monitor the performance and alarms of network slices, and/or ensure the achievement of service level specification (SLS) requirements of network slices. A network slice is an end-to-end logical network that may include a wireless access network (RAN) network slice subnet, a core network (CN) network slice subnet, and a transmission network (TN) network slice subnet. The RAN network slice subnet consists of one or more RAN network elements, the CN network slice subnet consists of a series of CN network elements, such as a core network consisting of AMF, SMF, UPF, PCF, and UDM, and the TN network slice subnet includes TN network elements and transmission links.

NWDAF: A control plane functional entity. It can collect data from 5GC network functions (NF), AF, and (operation administration and maintenance, OAM) (i.e., management plane functional entity), and can also analyze the results (statistics and predictions) The output is used by consumers to make subsequent action decisions.

Enhanced management data analytics service (eMDAS): is a management plane functional entity. eMDAS can use the performance data, alarm data, and/or NWDAF analysis data reported by each network element in the 5G network as input information to analyze or predict the service experience of terminal users on the network slice, and give the reasons for abnormal service experience (the difference between service experience information and service experience demand information is too large), such as reduced service experience due to wireless cell coverage quality problems.

Please refer to Figure 1, which is a schematic diagram of the composition structure of an eMDAS and NWDAF provided in an embodiment of the present application. As shown in Figure 1, the 3GPP network architecture may include a cross-domain eMDAS entity and a domain eMDAS entity. The domain eMDAS entity represents a CN domain eMDAS entity and/or a RAN domain eMDAS entity. The cross-domain eMDAS entity can be used to connect to and manage the domain eMDAS entity. Correspondingly, the 3GPP network architecture may include a cross-domain eMDAS consumer and a domain eMDA consumer. The cross-domain eMDAS consumer can be connected to the cross-domain eMDAS entity, or to the domain eMDA consumer. Then the cross-domain eMDAS entity (or domain eMDAS consumer) is connected to the domain eMDAS entity. The eMDAS service is provided through the MnS interface, and the eMDAS service is consumed through the MDA MnS. Among them, the CN domain eMDAS entity is a management function entity located above the CN domain. In the CN, NWDAF is included, and NWDAF can communicate with the CN domain eMDAS entity through the Nwdaf interface. NWDAF can also connect and communicate with other 5GC NFs.

It should be noted that in a 3GPP network architecture, cross-domain eMDAS entities and domain eMDAS entities can be included at the same time, or cross-domain eMDAS entities or domain eMDAS entities can be included separately, and the eMDAS therein can connect to eMDAS consumers (including AF or UE), and can also perform corresponding functions of managing and analyzing data. Therefore, the embodiments of the present application do not distinguish between cross-domain eMDAS entities and domain eMDAS entities.

The following is an introduction to the service quality optimization process for high-traffic services such as streaming video.

Please refer to FIG. 2 , which is a schematic diagram of the interaction process between NWDAF and AF provided in an embodiment of the present application. As shown in FIG. 2 , NWDAF in CN can be used for service experience analysis and optimization of terminal users. NWDAF obtains QoE information of certain service types (such as high-traffic services such as streaming video) from NF and AF in CN, and supports collecting QoE indicator information of certain service types on UE through AF. For example, 3GPP dynamic adaptive streaming over HTTP (DASH) based on HTTP, etc., whose QoE indicators include average throughput, initial playout delay, buffer level, etc. Then, NWDAF compares the QoE information with the QoE demand information based on the input of QoE information of certain service types obtained from AF, and analyzes and optimizes the QoS configuration strategy of CN or the network slice selection strategy of UE according to the comparison results, for example, to improve the accuracy of QoS policy configuration, instruct UE to reselect a more suitable network slice, etc. By selecting a better QoS parameter combination, and/or configuring more reasonable network bandwidth resources, and/or instructing the UE to a more appropriate network slice selection strategy, the service experience of the UE on the 5G network/network slice is improved.

That is to say, conventional service experience management or optimization is mainly achieved through the interaction between the control plane functional entity and AF. However, with the development and evolution of 5G new radio (NR), new service scenarios are faced. For example, URLLC services have high requirements for latency and reliability, which are different from the QoE indicators of conventional services. The process of network elements interacting with AF to obtain QoE indicators and then manage or optimize service experience should also be different.

Based on this, please refer to FIG. 3, which is a flow chart of a service quality management method provided in an embodiment of the present application. As shown in FIG. 3, the method includes the following steps:

201. A data analysis function entity receives first service experience information of a delay and/or reliability sensitive service from an application function entity or a terminal device, where the first service experience information is a quality parameter that affects a user's perception of the delay and/or reliability sensitive service.

In the embodiment of the present application, the data analysis function entity receives the first service experience information from the AF or UE, which may be actively sent by the AF or UE to the data analysis function entity, or sent by the AF or UE in response to a request message or subscription message from the data analysis function entity. Therefore, before step 201, step 204 may also be included, in which the data analysis function entity sends a first message to the application function entity or the terminal device, and the first message is used to request or subscribe to service experience information.

In an embodiment of the present application, the first service experience information of the delay and/or reliability sensitive service is received from the application function entity AF or the terminal device UE through the data analysis function entity. The delay and/or reliability sensitive service refers to a service with low delay and high reliability requirements, which may specifically refer to a URLLC service. The data analysis function entity is a functional entity capable of performing data analysis. Optionally, the data analysis function entity may refer to eMDAS, or it may refer to NWDAF. The eMDAS may be co-established with the NSMF. Or the eMDAS and the NSMF may be separately arranged. As an eMDAS consumer, NSMF may obtain the first service experience information from NSMF consumers (including AF, UE or other consumer entities) by NSMF, and then send it to eMDAS for subsequent analysis and processing.

The first service experience information of the delay and/or reliability sensitive service refers to the quality parameters that affect the user's perception of the delay and/or reliability sensitive service, and specifically refers to the QoE information (or QoE indicator information) described above. The first service experience information includes delay parameters and reliability parameters. Among them, the delay parameter is used to characterize whether the maximum transmission time of each data packet of the delay and/or reliability sensitive service is within the preset value. Within the time threshold, the reliability parameter is used to characterize whether the packet loss rate of the latency and/or reliability-sensitive service is within a preset range.

Optionally, the delay parameters in the first service experience information may include one or more of the following: delay distribution, escape delay, interaction delay, round-trip delay RTT jitter, packet interval distribution, or interruption rate.

For example, the QoE indicator information of the video backhaul service (URLLC service) includes the following:

Table 1

For example, the QoE indicator information of the remote control service (URLLC service) includes the following:

Table 2

Packet interval distribution refers to the distribution of the time intervals between data packet transmissions. As shown in Tables 1 and 2, RTT jitter and packet interval distribution are delay jitter QoE indicators unique to video backhaul services and remote control services. In addition, remote control services also include other unique QoE indicators. As shown in Table 2, they include delay distribution, escape delay, interaction delay, and interruption rate.

It should be noted that QoE information includes very systematic user experience information, but some of the user experience information is irrelevant to the parameters of the network transmission process, such as tariff satisfaction, after-sales satisfaction, etc., and such user experience information cannot be changed by modifying the service transmission information through the network quality management strategy. Therefore, the QoE information obtained by eMDAS can refer to part of the QoE information related to network transmission, rather than all the QoE information.

In the embodiment of the present application, the first user experience information can be obtained from the AF or UE through the data analysis function entity, and some QoE information in the table is also included in other types of services. Therefore, in some cases, the data analysis function entity can obtain this QoE information in the same way as other types of services obtain this type of QoE information. This is not specifically limited in the embodiment of the present application.

202. The data analysis function entity receives first service transmission information of a delay and/or reliability sensitive service from a first network entity, where the first service transmission information is measurement information characterizing service transmission performance during transmission of the delay and/or reliability sensitive service.

In the embodiment of the present application, the data analysis function entity receives the first service transmission information from the first network entity, which may be actively sent by the first network entity to the data analysis function entity, or sent by the first network entity in response to a request message or a subscription message of the data analysis function entity. Therefore, before step 202, step 205 may also be included, in which the data analysis function entity sends a second message to the first network entity, and the second message is used to request or subscribe to the first service transmission information.

In the embodiment of the present application, the first service transmission information of the delay and/or reliability sensitive service refers to the measurement information characterizing the service transmission performance during the delay and/or reliability sensitive service transmission process. In addition, there is a corresponding relationship between the first service transmission information and the first service experience information. When the first service transmission information changes, it usually causes the first service experience information to change.

Specifically, the first network entity refers to a functional entity that can obtain service transmission information. The first service transmission information may include service quality QoS measurement information of delay and/or reliability sensitive services.

In the embodiments of the present application, the QoS measurement information of delay and/or reliability sensitive services mainly refers to the 5G service quality identifier (5G QoS idtifier, 5QI), which represents a set of QoS attribute values of the 5G network. A set of QoS attribute values includes priority, packet delay budget, packet error rate, default maximum data burst, and/or default average window attribute, etc. There are three types of 5QI: standard 5QI, pre-configured 5QI, or dynamically allocated 5QI. In the standard 5QI, each value corresponds to a set of QoS specification parameters; the pre-configured 5QI is preset in the access network; the QoS specification of the dynamically allocated 5QI is part of the QoS template (QoS profile) or QoS rule (QoS rule).

When the data analysis function entities are different, the corresponding first network entities for obtaining the first service transmission information are also different. Please refer to Figure 4A for details. Figure 4A is a schematic diagram of a communication architecture provided in an embodiment of the present application. As shown in Figure 4A, the data analysis function entity is an enhanced management data analysis function entity eMDAS, which obtains the first service experience information from the AF. The first network entity may be a first network management entity, which may specifically include CN NSSMF and/or RAN NSSMF, or may also include NSMF (CN NSSMF and RAN NSSMF are managed by NSMF), and eMDAS obtains the first service transmission information from CN NSSMF and/or RAN NSSMF (or NSMF); wherein eMDAS may communicate directly with AF, or may communicate through an exposure governance management function (EGMF).

Or refer to Figure 4B, which is another communication architecture schematic diagram provided by an embodiment of the present application. As shown in Figure 4B, the data analysis function entity is eMDAS, and eMDAS and NSMF are jointly established. The first network entity includes CN NSSMF and/or RAN NSSMF. The first service transmission information is obtained directly from CN NSSMF and/or RAN NSSMF by eMDAS (or NSMF). In addition, the first service experience information can be obtained directly from AF or UE by eMDAS. NSMF can also obtain the first service experience information from AF or UE (or other NSMF consumers), and then send it to eMDAS, which will perform subsequent analysis and processing. When obtaining the first service experience information from the UE, the UE can communicate directly with the eMDAS or NSMF, or communicate with the UE through the base station gNB. UE can refer to all UEs within the management scope of NSMF.

Alternatively, refer to FIG. 4C , which is a schematic diagram of another communication architecture provided by an embodiment of the present application. As shown in FIG. 4C , the data analysis function entity in the communication architecture is NWDAF, and NWDAF can communicate directly with AF to obtain the first service experience information, or communicate through a network exposure function (NEF). The first network entity can be a network element, a network function or a network device, specifically a UPF.

Alternatively, the QoS measurement information can be obtained by the first network entity in the form of QoS analysis information. As described in the previous process, the data analysis function entity can be eMDAS, which is a management plane functional entity and can obtain QoS analysis information from other control plane data analysis function entities such as NWDAF. At this time, the first network entity is NWDAF (a network function). NWDAF obtains QoS measurement information from other network elements such as UPF, analyzes and processes the QoS measurement information, and sends it to eMDAS in the form of QoS analysis information. QoS analysis information is a statistical or predicted value of QoS measurement information. For example, statistical values of QoS compliance or non-compliance in different dimensions such as cells, tracking areas, network slices, etc.

The first service transmission information may also include network measurement information. The specific network measurement information may include the actual round-trip time (RTT), transmission delay, bandwidth utilization, packet loss rate, etc. in the network during service execution. The data analysis function entity in this case is the management plane data analysis function entity, which may be eMDAS. Correspondingly, the first network entity at this time may include CN NSSMF and/or RAN NSSMF as described above. In some cases, such as cross-domain management, the first network entity may also include NSMF. NSMF is used to manage CN NSSMF and RAN NSSMF.

203. The data analysis function entity generates a service quality management policy based on the first service experience information, the first service transmission information, and the service experience requirement information corresponding to the delay and/or reliability sensitive service, and sends the policy to the second network entity.

Among them, the service quality management policy is used to instruct the second network entity to modify or adjust the resource configuration policy or parameter configuration of the delay and/or reliability sensitive service, so that the difference between the second service experience information and the service experience requirement information of the delay and/or reliability sensitive service after the modification or adjustment operation is within a preset threshold range.

After obtaining the first service experience information, the data analysis function entity may compare it with the service experience requirement information of the delay and/or reliability sensitive service. The service experience requirement information is the standard service experience that should be achieved when executing the service. The quality of the service experience information is mainly determined by comparing the service experience information with the service experience requirement information. If the difference between the two is within a preset range, including the two being consistent, or the service experience information is within a preset boundary range, or the difference between the service experience information and the service experience requirement information is within a preset boundary range, it indicates that the service experience information is good, otherwise it indicates that the service experience information is poor.

The service experience requirement information can also be obtained by the management data analysis function entity from the AF or UE. Or when the management data analysis function entity is eMDAS, it is obtained by eMDAS from the eMDAS consumer. When the management function data analysis function entity is co-established with NSMF, it can also be obtained by NSMF from the NSMF consumer. Therefore, before step 203, the method may also include the step of: the data analysis function entity obtains the service experience requirement information of the delay and/or reliability sensitive service (not shown in the figure).

In order to compare the service experience requirement information and service experience information, the two should be parameters with the same content. When the experience information is a certain type of QoE indicator information, the service experience requirement information is also this type of QoE indicator information. For the description of the content of the specific service experience requirement information, please refer to the aforementioned description of the first service experience. Therefore, optionally, the delay parameters in the service experience requirement information of delay and/or reliability sensitive services include one or more of the following: delay distribution, escape delay, interaction delay, round-trip delay RTT jitter, packet interval distribution, or interruption rate. It should be noted that for delay and/or reliability sensitive services, both delay parameters and reliability parameters need to be met at the same time. Therefore, while meeting these delay parameter requirements, the corresponding reliability parameter requirements must also be met.

A service quality management strategy can be generated based on the comparison result between the service experience demand information and the first service experience information, as well as the service transmission information. When the difference between the first service experience information and the service experience demand information is not within the preset range, consider generating a service quality management strategy. As described above, there is a corresponding relationship between the service experience information and the service transmission information. The first service transmission information is used to provide a reference for the generated service quality management strategy. The service quality management strategy is specifically used to modify or adjust the resource configuration strategy or parameter configuration of the delay and/or reliability sensitive service, so that the second service transmission information of the measurement information characterizing the service transmission performance during the delay and/or reliability sensitive service transmission process is different from the first service transmission information, and correspondingly, the second service experience information also changes. Assuming that the difference between the second service experience information and the service experience demand information is within the preset range, it means that the service quality management strategy has achieved the quality management effect. If the difference between the two is still not within the preset range, the aforementioned process of generating and sending the service quality management strategy and comparing whether the service quality experience demand information is achieved can be continued until the service quality management effect is achieved.

For example, assuming that the packet loss rate in the service experience requirement information is 99%, and the packet loss rate in the first service experience information is 97%, the difference between the two is 99%-97%=2%. Assuming that the preset range is 0, the difference between the first service experience information and the service experience requirement information is not within the preset range, and a service quality management strategy needs to be formulated to change the service experience information related to the packet loss rate.

However, before generating a specific strategy, the first service transmission information also needs to be analyzed. For example, in the first service transmission information, the packet loss rate corresponding to the QoS measurement information is 97%, indicating that it is necessary to improve the packet loss rate in the corresponding service experience information by adjusting the QoS requirement information of the delay and reliability sensitive services. The service quality management strategy is related to improving the QoS requirement information. Assuming that the packet loss rate corresponding to the QoS measurement information is 99%, it may be due to other reasons, such as poor air interface quality, which leads to a low packet loss rate corresponding to the service experience information. A service quality management strategy related to improving air interface quality can be formulated.

Further, the service experience demand information is compared with the first service experience information, and the analysis results that can be obtained include one or more of the following information (taking delay and/or reliability sensitive services as URLLC services for example): statistical distribution or predicted distribution information of one or more indicators in the URLLC service data flow experience demand information of a specified user (statistics by time period or by specified time range, the statistical results are classified as good, normal, poor, or classified as 1 to 5 levels, or other classification methods), statistical distribution or predicted distribution information of one or more indicators in the URLLC service data flow experience demand information on a specified network slice or network slice subnet (user number information of one or more indicators or indicator combinations are counted by time period or by specified time range, the user number statistics are classified as good, normal, poor, or classified as 1 to 5 levels, for example, the number of users with poor PLC control accuracy in network slice 1 at 12:00 noon is 50, accounting for 5% of the number of online users). If one or more indicator differences or the proportion of poor quality time or the number of poor quality users in the analysis results exceed the preset threshold (multiple different thresholds can be set according to the severity of the poor quality situation, and the threshold can also change dynamically according to different dimensions such as business volume or number of users), the corresponding level of alarm or abnormal event information is reported. In other words, assuming that the first business experience information and the corresponding business experience demand information are not direct parameter values, parameter processing can be performed first to obtain the difference value. For example, good, normal, poor classification or classification according to levels 1 to 5, the corresponding parameterized values can be 5, 4, 3, 2, 1, etc.

The data analysis function entity also outputs a service quality management strategy, that is, a solution to improve the above-mentioned poor quality indicators or poor quality users, and executes the service quality management strategy through the second network entity. It should be noted that the service quality management strategy changes the service transmission information obtained from the first network entity by modifying or adjusting the resource configuration strategy or parameter configuration of the delay and/or reliability sensitive service. For example, NWDAF allocates more bandwidth resources to users according to the user distribution on the UPF under its jurisdiction, modifies the queuing waiting time of URLLC service scheduling, allocates different amounts of wireless resources or transmission bandwidth resources, etc.

It can be seen that in the embodiment of the present application, for delay and/or reliability sensitive services, the first service experience information is obtained from the application function or terminal device through the data analysis function entity, and the first service transmission information is obtained from the first network entity, and then a service quality management policy is generated according to the first service experience information, the service experience requirement information of the delay and/or reliability sensitive service and the first service transmission information, and the service quality management policy is sent to the second network entity, and the resource configuration policy or parameter configuration of the delay and/or reliability sensitive service is modified or adjusted through the service quality management policy, so that the re-acquired second service experience information can meet the requirements of the service experience requirement information as much as possible. This process provides method steps for service quality management of delay and/or reliability sensitive services, and ensures the effectiveness of service quality management of delay and/or reliability sensitive services.

In the embodiment of the present application, when the data analysis functional entities are different, the first network entity is different, and correspondingly, the second network entity that receives and executes the service quality management policy output by the data analysis functional entity is also different. In fact, the specific service quality management policies will also be different.

Please refer to FIG. 5A , which is a flow chart of another service quality management method provided by an embodiment of the present application. As shown in FIG. 5A , the data analysis function entity is eMDAS, and the first network entity and the second network entity are both RAN NSSMF and/or CN NSSMF. The method includes steps 201 to 203 (or may also include step 204 and/or step 205) in the corresponding method in FIG. 3 , and the first service transmission information obtained by eMDAS from RAN NSSMF and/or CN NSSMF includes QoS measurement information, or may also include network measurement information. The network quality management policy generated by eMDAS is sent to RAN NSSMF and/or CN NSSMF for execution. Consistent with the above description, CN NSSMF and RAN NSSMF may be managed by NSMF, so the first network entity and/or the second network entity may also include NSMF, and NSMF obtains the first service transmission information from RAN NSSMF and/or CN NSSMF and sends it to eMDAS, or NSMF obtains the service quality management policy from eMDAS and sends it to CN NSSMF and/or RAN NSSMF for execution.

Alternatively, the first network entity in Figure 5A may also be NWDAF (a network function), and the second network entity is still RAN NSSMF and/or CN NSSMF (a network management entity). The specific method execution process is the same as that in Figure 5B and will not be repeated here.

The resource modification strategy in this scenario may include at least one of the following: turning on or off a specific resource strategy switch, increasing or decreasing the number of redundant retransmission links or the number of retransmissions in the radio access network RAN or the core network CN.

Among them, turning on or off a specific resource policy switch, for example, turning on or off the local UPF configuration. The local UPF configuration refers to selecting a UPF that is closer to the network location of the cell where the user is connected to establish a service session. Turning on the local UPF configuration can reduce the data packet transmission delay. RAN redundant transmission links, for example, Packet Data Convergence Protocol (PDCP) multi-connection redundant transmission, means that the UE sends or receives the same PDCP data packet with multiple cells. CN redundant transmission links, for example, UPF multi-connection redundant transmission. Increasing the number of RAN or CN redundant transmission links or the number of retransmissions can reduce the packet loss rate, and reducing the number of RAN or CN redundant transmission links or the number of retransmissions can reduce the transmission delay.

The parameter configuration modification strategy in this scenario may include at least one of the following: modifying the number or location information of reserved resources, modifying the CN bandwidth resource configuration, modifying the wireless resource configuration, activating the resource pre-scheduling strategy, increasing the number and resources of pre-scheduled resources, or modifying the terminal device UE switching strategy.

Modifying the number or location information of reserved resources includes: on the basis of the existing network slice-level guaranteed resources, priority resources and shared resources, further configuring corresponding guaranteed resources, priority resources and shared resources for the service, or modifying the location information of these resources, such as modifying the route, selecting a new UPF, etc. Modifying the CN bandwidth resource configuration includes increasing or decreasing the CN bandwidth resources. Modifying the wireless resource configuration includes modifying the number of physical resource blocks, or modifying the transmission power, scheduling time, etc. Activating the resource pre-scheduling strategy, such as configuring wireless resources for different applications or wireless bearers, and activating wireless resources through radio resource control (RRC), medium access control (MAC) or physical downlink control channel (PDCCH). The UE switching strategy may refer to the switching strategy of the UE between UPFs, such as maintaining the source UPF connection until the target UPF is successfully accessed and then releasing the source UPF connection. The modification of these parameter configuration strategies is also to reduce the transmission delay of data packets and/or reduce the packet loss rate of data packets.

It can be seen that in the embodiment of the present application, the first service experience information, the first service transmission information, and the service experience requirement information of the delay and sensitive service are obtained through the data analysis function entity of the management plane, and the service quality management strategy of the delay and/or reliability sensitive service is analyzed and generated. This process optimizes from the service quality level and the network quality level, so that the user's service experience information reaches the service experience requirement information, and achieves the effect of managing service quality from a more comprehensive perspective.

Please refer to Figure 5B, which is a flow chart of another service quality management method provided in an embodiment of the present application. As shown in Figure 5B, the data analysis function entity is NWDAF, the first network entity is UPF (a network function), and the second network entity is PCF (also a network function). The method includes steps 201 to 203 in the corresponding method in Figure 3 (or may also include step 204 and/or step 205), and the first service transmission information obtained by NWDAF from UPF includes QoS measurement information. The network quality management policy generated by NWDAF is sent to PCF for execution.

In this scenario, modifying or adjusting the resource configuration policy of latency and/or reliability sensitive services may include modifying the routing selection policy; for example, changing from a static routing selection policy to a dynamic routing selection policy.

Modifying or adjusting the parameter configuration of delay and/or reliability sensitive services includes modifying the QoS requirement information of delay and/or reliability sensitive services, such as reducing the delay requirement in the QoS requirement information, or reducing the packet loss rate requirement in the QoS requirement information.

It can be seen that in the embodiment of the present application, the first service experience information, the first service transmission information, and the service experience requirement information of the delay and sensitive service are obtained through the data analysis function entity of the control plane, and the service quality management strategy of the delay and/or reliability sensitive service is analyzed and generated. This process optimizes from the service quality level so that the user's service experience information reaches the service experience requirement information, and achieves the effect of managing service quality from a more targeted perspective.

As shown in FIG. 6, a communication device 400 provided in an embodiment of the present application includes a communication device for implementing the above-mentioned FIG. 3, FIG. 5A or The method embodiment shown in FIG5B and any possible design method module or unit. The module or unit may be a hardware circuit, or software, or a hardware circuit combined with software. The device may include a transceiver unit 401 and a processing unit 402, wherein:

The transceiver unit 401 is configured to receive first service experience information of a delay and/or reliability sensitive service from an application function entity or a terminal device, and receive first service transmission information of a delay and/or reliability sensitive service from a first network entity, where the first service experience information is a quality parameter that affects the user's perception of the delay and/or reliability sensitive service, and the first service transmission information is measurement information that characterizes service transmission performance during the transmission of the delay and/or reliability sensitive service;

The processing unit 402 is used to send a service quality management policy to the second network entity based on the first service experience information, the first service transmission information and the service experience requirement information corresponding to the delay and/or reliability sensitive service; wherein the service quality management policy is used to instruct the second network entity to modify or adjust the resource configuration policy or parameter configuration of the delay and/or reliability sensitive service, so that the difference between the second service experience information and the service experience requirement information of the delay and/or reliability sensitive service after the modification or adjustment operation is within a preset threshold range.

For a more detailed description of the transceiver unit 401 and the processing unit 402, please refer to the relevant description in the above method embodiment, which will not be described again here.

As shown in FIG. 7 , FIG. 7 shows a schematic diagram of the hardware structure of a communication device in an embodiment of the present application. The structure of the communication device in FIG. 6 may refer to the structure shown in FIG. 7 . The communication device 900 includes: a processor 111 and a transceiver 112, wherein the processor 111 and the transceiver 112 are electrically coupled;

The processor 111 is configured to execute part or all of the computer program instructions in the memory. When the part or all of the computer program instructions are executed, the device executes the method described in any one of the above embodiments.

The transceiver 112 is used to communicate with other devices; for example, to receive first service experience information of a delay and/or reliability sensitive service from an application function entity or a terminal device.

Optionally, a memory 113 is also included for storing computer program instructions. Optionally, the memory 113 (memory #1) is located within the device, the memory 113 (memory #2) is integrated with the processor 111, or the memory 113 (memory #3) is located outside the device.

It should be understood that the communication device 900 shown in FIG. 7 may be a chip or a circuit. For example, a chip or a circuit may be provided in a terminal device or a communication device. The transceiver 112 may also be a communication interface. The transceiver includes a receiver and a transmitter. Further, the communication device 900 may also include a bus system.

Among them, the processor 111, the memory 113, and the transceiver 112 are connected through a bus system, and the processor 111 is used to execute the instructions stored in the memory 113 to control the transceiver to receive signals and send signals, and complete the steps of the first device or the second device in the implementation method involved in this application. The memory 113 can be integrated in the processor 111, or it can be set separately from the processor 111.

As an implementation method, the function of the transceiver 112 can be considered to be implemented by a transceiver circuit or a dedicated transceiver chip. The processor 111 can be considered to be implemented by a dedicated processing chip, a processing circuit, a processor or a general chip. The processor can be a central processing unit (CPU), a network processor (NP) or a combination of a CPU and a NP. The processor can further include a hardware chip or other general processors. The above-mentioned hardware chip can be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above-mentioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) and other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. or any combination thereof. The general processor can be a microprocessor or the processor can also be any conventional processor, etc.

It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus random access memory (DR RAM). It should be noted that the memory described in this application is intended to include, but is not limited to, these and any other suitable types of memory.

An embodiment of the present application provides a computer storage medium storing a computer program, wherein the computer program includes a method for executing the method corresponding to the management data analysis functional entity in the above embodiment.

An embodiment of the present application provides a computer storage medium storing a computer program, wherein the computer program includes a method for executing the method corresponding to the network data analysis function entity in the above embodiment.

An embodiment of the present application provides a computer program product including instructions, which, when executed on a computer, enables the computer to execute the method in the above embodiment corresponding to the management data analysis functional entity.

An embodiment of the present application provides a computer program product including instructions, which, when executed on a computer, enables the computer to execute the method in the above embodiment corresponding to the network data analysis functional entity.

It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, 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 through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (25)

1. A service quality management method, characterized in that it is applied to a data analysis function entity, and the method comprises:

   Receiving first service experience information of a delay and/or reliability sensitive service from an application function entity or a terminal device, and receiving first service transmission information of a delay and/or reliability sensitive service from a first network entity, wherein the first service experience information is a quality parameter that affects a user's perception of the delay and/or reliability sensitive service, and the first service transmission information is measurement information characterizing service transmission performance during transmission of the delay and/or reliability sensitive service;

   A service quality management policy is sent to a second network entity based on the first service experience information, the first service transmission information and the service experience requirement information corresponding to the delay and/or reliability sensitive service; wherein the service quality management policy is used to instruct the second network entity to modify or adjust the resource configuration policy or parameter configuration of the delay and/or reliability sensitive service, so that the difference between the second service experience information of the delay and/or reliability sensitive service after the modification or adjustment operation and the service experience requirement information is within a preset threshold range.
2. The method according to claim 1 is characterized in that the service experience information of the delay and/or reliability sensitive service includes a delay parameter and a reliability parameter.
3. The method according to claim 2 is characterized in that the delay parameters include one or more of the following: transmission delay, escape delay, interaction delay, round-trip time (RTT) jitter, packet interval, or interruption rate.
4. The method according to any one of claims 1-3 is characterized in that the first service transmission information includes service quality QoS measurement information of the delay and/or reliability sensitive service; or the first service transmission information also includes network performance measurement information corresponding to the delay and/or reliability sensitive service.
5. The method according to any one of claims 1 to 4 is characterized in that the data analysis function entity is an enhanced management data analysis service eMDAS.
6. The method according to claim 5 is characterized in that the first network entity includes a core network network slice subnet management function entity CN NSSMF, and/or an access network network slice subnet management function entity RAN NSSMF; and/or

   The first network entity includes a network slice management function entity NSMF; and/or

   The first network entity includes a network data analysis function entity NWDAF.
7. The method according to claim 5 or 6 is characterized in that the second network entity includes CN NSSMF and/or RAN NSSMF, or the second network entity also includes NSMF.
8. The method according to any one of claims 1 to 4 is characterized in that the data analysis function entity is a network data analysis function entity NWDAF.
9. The method according to claim 8 is characterized in that the first network entity is a user plane function entity UPF; and/or the second network entity is a policy control function entity PCF.
10. The method according to any one of claims 1 to 7 is characterized in that the modification or adjustment of the resource configuration strategy of the delay and/or reliability sensitive service includes at least one of the following: turning on or off a specific resource strategy switch, increasing or decreasing the number of redundant retransmission links or the number of retransmissions in the radio access network RAN or the core network CN; and/or

    The modification or adjustment of the parameter configuration of the delay and/or reliability sensitive service includes at least one of the following: modifying the number or location information of reserved resources, modifying the CN bandwidth resource configuration, modifying the wireless resource configuration, activating the resource pre-scheduling strategy, increasing the number and resources of pre-scheduled resources, or modifying the terminal device UE switching strategy.
11. The method according to any one of claims 1-4 or 8-9 is characterized in that the modification or adjustment of the resource allocation strategy of the delay and/or reliability sensitive service includes modifying the routing selection strategy; the modification or adjustment of the parameter configuration of the delay and/or reliability sensitive service includes modifying the QoS requirement information of the delay and/or reliability sensitive service.
12. A communication device, characterized in that the device comprises:

    A transceiver unit, configured to receive first service experience information of a delay and/or reliability sensitive service from an application function entity or a terminal device, and receive first service transmission information of a delay and/or reliability sensitive service from a first network entity, wherein the first service experience information is a quality parameter that affects a user's perception of the delay and/or reliability sensitive service, and the first service transmission information is measurement information characterizing service transmission performance during transmission of the delay and/or reliability sensitive service;

    A processing unit, used to send a service quality management policy to a second network entity based on the first service experience information, the first service transmission information and the service experience requirement information corresponding to the delay and/or reliability sensitive service; wherein the service quality management policy is used to instruct the second network entity to modify or adjust the resource configuration policy or parameter configuration of the delay and/or reliability sensitive service, so that the difference between the second service experience information of the delay and/or reliability sensitive service after the modification or adjustment operation and the service experience requirement information is within a preset threshold range.
13. The device according to claim 12 is characterized in that the service experience information of the delay and/or reliability sensitive service includes a delay parameter and a reliability parameter.
14. The device according to claim 13 is characterized in that the delay parameters include one or more of the following: transmission delay, escape delay, interaction delay, round-trip time (RTT) jitter, packet interval, or interruption rate.
15. The device according to any one of claims 12-14 is characterized in that the first service transmission information includes service quality QoS measurement information of the delay and/or reliability sensitive service; or the first service transmission information also includes network performance measurement information corresponding to the delay and/or reliability sensitive service.
16. The device according to any one of claims 12 to 15, characterized in that the data analysis functional entity is an enhanced management data analysis service eMDAS.
17. The device according to claim 16 is characterized in that the first network entity includes a core network network slice subnet management function entity CN NSSMF, and/or an access network network slice subnet management function entity RAN NSSMF; and/or

    The first network entity includes a network slice management function entity NSMF; and/or

    The first network entity includes a network data analysis function entity NWDAF.
18. The device according to claim 16 or 17 is characterized in that the second network entity includes CN NSSMF and/or RAN NSSMF, or the second network entity also includes NSMF.
19. The device according to any one of claims 12 to 16, characterized in that the data analysis function entity is a network data analysis function entity NWDAF.
20. The device according to claim 19 is characterized in that the first network entity is a user plane function entity UPF; and/or the second network entity is a policy control function entity PCF.
21. The device according to any one of claims 11 to 18 is characterized in that the modification or adjustment of the resource configuration strategy of the delay and/or reliability sensitive service includes at least one of the following: turning on or off a specific resource strategy switch, increasing or decreasing the number of redundant retransmission links or the number of retransmissions in the radio access network RAN or the core network CN; and/or

    The modification or adjustment of the parameter configuration of the delay and/or reliability sensitive service includes at least one of the following: modifying the number or location information of reserved resources, modifying the CN bandwidth resource configuration, modifying the wireless resource configuration, activating the resource pre-scheduling strategy, increasing the number and resources of pre-scheduled resources, or modifying the terminal device UE switching strategy.
22. The device according to any one of claims 11-15 or 19-20 is characterized in that the modification or adjustment of the resource allocation strategy of the delay and/or reliability sensitive service includes modifying the routing selection strategy; the modification or adjustment of the parameter configuration of the delay and/or reliability sensitive service includes modifying the QoS requirement information of the delay and/or reliability sensitive service.
23. A communication device, characterized in that it includes a processor coupled to a memory, wherein the processor is used to execute computer program instructions stored in the memory so that the device performs the method according to any one of claims 1 to 11.
24. A readable storage medium, characterized in that it is used to store instructions, and when the instructions are executed, the method according to any one of claims 1 to 11 is implemented.
25. A computer program product, characterized in that when a computer reads and executes the computer program product, the computer executes the method according to any one of claims 1 to 11.