Patent Description:
<FIG> shows positioning of a network data analytics function (network data analytics function, NWDAF) in the 3rd generation partnership project (3rd generation partnership project, 3GPP) <NUM>. Specifically, the NWDAF may subscribe to basic data from 5th generation core (5th generation core, 5GC) network functions (network functions, NFs), application functions (application functions, AFs), and an operation administration and maintenance (operation, administration, and maintenance, OAM) system of a carrier network, analyzes the subscribed basic data based on scenarios, and then feeds back an analysis result to the NFs and the AFs for subsequent processing.

For a service experience assurance scenario, how the NWDAF subscribes to the data from the NF and the AF and establishes a MOS model of a specified service is defined in the observed service experience related network data analytics (observed service experience related network data analytics) of the 3GPP <NUM><NUM>. Specifically, an NWDAF entity subscribes to a quality of service MOS level of the specified service from an AF entity, and the NWDAF entity subscribes to, from a 5GC NFs entity, a network performance indicator of a transmission network that carries the current service. Further, the NWDAF entity establishes the MOS model (namely, a mathematical relationship between the quality of service MOS level and the network performance indicator of the transmission network) of the specified service based on the quality of service MOS level subscribed from the AF entity and the network performance indicator of the transmission network subscribed from the 5GC NFs entity.

However, in the foregoing method for establishing a MOS model of a service, the network performance indicator of the transmission network and the quality of service MOS level need to be respectively subscribed from the 5GC NFs entity and the AF entity. Therefore, measurement synchronization needs to rely on capabilities and cooperation of the 5GC NFs entity and the AF entity. This is difficult to implement in a live network.

<NPL>, relates to optionality of data to be collected by NWDAF.

"<NPL>, relates to network automation for <NUM>.

Implementations of this application provide a training method for an application MOS model, a device, and a system, to resolve a problem that an existing training method for a MOS model of a service needs to rely on a capability and cooperation of an AF entity, and is difficult to implement in a live network.

According to a first aspect, a training method for an application mean opinion score MOS model is provided. The method includes: A central network data analytics function (central NWDAF, C-NWDAF) entity sends a first subscription request to an edge network data analytics function (edge NWDAF, E-NWDAF) entity, where the first subscription request is used to request to subscribe to a quality of service MOS level of a target service and a corresponding first network performance indicator, and the first network performance indicator is a network performance indicator of a transmission network that carries the target service; the C-NWDAF entity receives the quality of service MOS level and the first network performance indicator from the E-NWDAF entity; and the C-NWDAF entity establishes a MOS model of the target service based on the quality of service MOS level and the first network performance indicator. In this implementation of this application, the quality of service MOS level is a comprehensive score that is of a current service and that is obtained by analyzing a measurement result of a key quality of service indicator by using an experience model in a service process, where the key indicator in the service process is measured by using means such as an instrument or a tool. The quality of service MOS level may also be referred to as a service experience quality score. For example, a <NUM>-point scale may be used, and a quality of service evaluation score is <NUM>, <NUM>, <NUM>, <NUM>, or <NUM>. In addition, in this implementation of this application, establishing the MOS model of the target service is establishing a mathematical relationship between the quality of service MOS level of the target service and a network performance indicator. Unified descriptions are provided herein, and details are not described below again. Based on the training method for an application MOS model provided in this implementation of this application, in this implementation of this application, a carrier deploys distributed NWDAF entities including the C-NWDAF entity and the E-NWDAF entity, the C-NWDAF entity may subscribe to the quality of service MOS level of the target service and the corresponding first network performance indicator from the E-NWDAF entity, and the E-NWDAF entity obtains the quality of service MOS level of the target service and the corresponding first network performance indicator through synchronous measurement. In other words, the E-NWDAF entity obtains the quality of service MOS level of the target service and the corresponding first network performance indicator inside the carrier. Therefore, implementation is easier, and a measurement result is more accurate.

In a possible design, the quality of service MOS level is determined based on service experience data of the target service. For example, when the target service is a video service, the service experience data includes one or more of the following parameters: an initial buffering delay, playback buffer duration, a bit rate, a service rate, a frame rate, smoothness, and definition of the video service, and resolution of a terminal device. The bit rate of the video service in this implementation of this application is a quantity of data bits that are transferred per unit of time during data transmission, and a unit is generally kilobits per second (kbps). The frame rate of the video service is a measure used to measure a quantity of displayed frames, and a measurement unit is displayed frames per second (frames per second, FPS) or hertz (Hz). The resolution of the terminal device includes display resolution and image resolution. The display resolution may also be referred to as screen resolution, and is a quantity of pixels that can be displayed on a display. The image resolution is a quantity of pixels per inch. Unified descriptions are provided herein, and details are not described below again.

In a possible design, the first network performance indicator includes one or more of the following parameters: a quantity of lost uplink packets, an uplink packet loss rate, a quantity of lost downlink packets, a downlink packet loss rate, a round-trip time (round-trip time, RTT), a quantity of uplink packets with bit errors, an uplink bit error rate, a quantity of downlink packets with bit errors, a downlink error bit rate, a quantity of uplink out-of-order packets, an uplink out-of-order packet rate, a quantity of downlink out-of-order packets, a downlink out-of-order packet rate, a quantity of uplink retransmitted packets, an uplink retransmission rate, a quantity of downlink retransmitted packets, a downlink retransmission rate, an average uplink packet interval, an average uplink packet jitter, an average downlink packet interval, an average downlink packet jitter, an uplink rate, and a downlink rate on a path between the terminal device and an access network device; a quantity of lost uplink packets, an uplink packet loss rate, a quantity of lost downlink packets, a downlink packet loss rate, an RTT, a quantity of uplink packets with bit errors, an uplink bit error rate, a quantity of downlink packets with bit errors, a downlink error bit rate, a quantity of uplink out-of-order packets, an uplink out-of-order packet rate, a quantity of downlink out-of-order packets, a downlink out-of-order packet rate, a quantity of uplink retransmitted packets, an uplink retransmission rate, a quantity of downlink retransmitted packets, a downlink retransmission rate, an average uplink packet interval, an average uplink packet jitter, an average downlink packet interval, an average downlink packet jitter, an uplink rate, and a downlink rate on a path between the access network device and a user plane entity; and a quantity of lost uplink packets, an uplink packet loss rate, a quantity of lost downlink packets, a downlink packet loss rate, an RTT, a quantity of uplink packets with bit errors, an uplink bit error rate, a quantity of downlink packets with bit errors, a downlink error bit rate, a quantity of uplink out-of-order packets, an uplink out-of- order packet rate, a quantity of downlink out-of-order packets, a downlink out-of-order packet rate, a quantity of uplink retransmitted packets, an uplink retransmission rate, a quantity of downlink retransmitted packets, a downlink retransmission rate, an average uplink packet interval, an average uplink packet jitter, an average downlink packet interval, an average downlink packet jitter, an uplink rate, and a downlink rate on a path between the user plane entity and an application function entity. In this implementation of this application, a bit error means that an error occurs in some bits that have been received, judged, and regenerated in a digital data stream, and causes damage to quality of transmitted information. The bit error may be understood as that an error occurs in a data packet in a transmission process. Out-of-order means that when a data packet is too large, the data packet is split into a plurality of data packets that satisfy transmission requirements, where each data packet has a corresponding sequence number for a peer end to reassemble; however, due to different intermediate routes or poor network quality, a later sent data packet may first arrive at the peer end, thus generating out-of-order data packets. A high out-of-order packet rate also leads to poor communication quality. A jitter refers to a variation degree of a delay of a packet data packet. If a network is congested, a queuing delay affects an end-to-end delay and causes different delays of packets transmitted through a same connection. The jitter is used to describe the variation degree of the delay. In addition, the user plane entity in this implementation of this application is mainly configured to forward a user data packet. In a 5th generation <NUM> communication system, the user plane entity may be a user plane function (user plane function, UPF) network element. In future communication such as sixth generation <NUM> communication, the user plane entity may still be a UPF network element or have another name. This is not limited in this implementation of this application. The application function entity in this implementation of this application is mainly configured to provide an application layer service function for the terminal device. In the 5th generation <NUM> communication system, the application function entity may be an AF network element. In the future communication such as the 6th generation <NUM> communication, the application function entity may still be an AF network element or have another name. This is not limited in this implementation of this application.

According to the claimed invention, the method further includes: The C-NWDAF entity obtains a second network performance indicator corresponding to the MOS level, where the second network performance indicator is a performance indicator of a radio network that carries the target service. That the C-NWDAF entity establishes a MOS model of the target service based on the quality of service MOS level and the first network performance indicator includes: The C-NWDAF entity excludes a sample whose quality of service MOS is poor due to an exception of the terminal device and a sample whose quality of service MOS is poor due to an exception of the application function entity based on the second network performance indicator, the quality of service MOS level, and the first network performance indicator, and establishes the MOS model of the target service. In this implementation of this application, the samples whose quality of service MOS is poor are samples whose MOS score is relatively low due to the exception of the terminal device and the exception of the application function entity. Unified descriptions are provided herein, and details are not described below again. Because the first network performance indicator, the performance indicator of the radio network that carries the target service, the sample whose quality of service MOS is poor due to the exception of the terminal device, and the sample whose quality of service MOS is poor due to the exception of the application function entity are considered, the MOS model that is of the target service and that is established by using the training method for an application MOS model provided in this implementation of this application is more accurate and comprehensive.

In a possible design, the method further includes: The C-NWDAF entity obtains first load of a first network function entity corresponding to the MOS level, where the first network function entity is a network data provider function entity. That the C-NWDAF entity establishes a MOS model of the target service based on the quality of service MOS level and the first network performance indicator includes: The C-NWDAF entity excludes a sample whose quality of service MOS is poor due to an exception of the terminal device and a sample whose quality of service MOS is poor due to an exception of the application function entity based on the first load of the first network function entity, the quality of service MOS level, and the first network performance indicator, and establishes the MOS model of the target service. Because the first network performance indicator, the first load of the first network function entity corresponding to the MOS level, the sample whose quality of service MOS is poor due to the exception of the terminal device, and the sample whose quality of service MOS is poor due to the exception of the application function entity are considered, the MOS model that is of the target service and that is established by using the training method for an application MOS model provided in this implementation of this application is more accurate and comprehensive.

In a possible design, the method further includes: The C-NWDAF entity obtains a second network performance indicator corresponding to the MOS level and first load of a first network function entity corresponding to the MOS level, where the second network performance indicator is a performance indicator of a radio network that carries the target service, and the first network function entity is a network data provider function entity. That the C-NWDAF entity establishes a MOS model of the target service based on the quality of service MOS level and the first network performance indicator includes: The C-NWDAF entity excludes a sample whose quality of service MOS is poor due to an exception of the terminal device and a sample whose quality of service MOS is poor due to an exception of the application function entity based on the second network performance indicator, the first load of the first network function entity, the quality of service MOS level, and the first network performance indicator, and establishes the MOS model of the target service. Because the first network performance indicator, the performance indicator of the radio network that carries the target service, the first load of the first network function entity corresponding to the MOS level, the sample whose quality of service MOS is poor due to the exception of the terminal device, and the sample whose quality of service MOS is poor due to the exception of the application function entity are considered, the MOS model that is of the target service and that is established by using the training method for an application MOS model provided in this implementation of this application is more accurate and comprehensive.

In a possible design, that the C-NWDAF entity obtains first load of a first network function entity corresponding to the MOS level includes: The C-NWDAF entity sends a second subscription request to a network repository function entity, where the second subscription request is used to request to subscribe to the first load of the first network function entity; and the C-NWDAF entity receives the first load of the first network function entity from the network repository function entity. The network repository function entity in this implementation of this application is configured to: store description information of a network function entity (for example, the first network function entity) and a service provided by the network function entity, and support service discovery, network element or entity discovery, and the like. In the 5th generation <NUM> communication system, the network repository function entity may be a network repository function (network repository function, NRF) entity. In the future communication such as the 6th generation <NUM> communication, the network repository function entity may still be an NRF entity or have another name. This is not limited in this implementation of this application.

Based on this solution, the C-NWDAF entity may obtain the first load of the first network function entity corresponding to the MOS level.

In a possible design, that the C-NWDAF entity obtains a second network performance indicator corresponding to the MOS level includes: The C-NWDAF entity sends a third subscription request to an operation administration and maintenance OAM entity of a carrier network, where the third subscription request is used to request to subscribe to the second network performance indicator; and the C-NWDAF entity receives the second network performance indicator from the OAM entity. Based on this solution, the C-NWDAF entity obtains the second network performance indicator corresponding to the MOS level.

In a possible design, the first load of the first network function entity includes one or more of the following parameters: a quantity of sessions of the first network function entity, a quantity of users of the first network function entity, and resource usage of the first network function entity. In other words, the MOS model of the target service in this implementation of this application is further related to one or more of the quantity of sessions of the first network function entity, the quantity of users of the first network function entity, and the resource usage of the first network function entity. Therefore, the MOS model of the target service is more complete.

In a possible design, the second network performance indicator includes one or more of the following parameters: a quantity of sessions, a quantity of radio resource control (radio resource control, RRC) connected users, a congestion status, and resource usage of the access network device, a radio measurement indicator of the terminal device, and location information of the terminal device. In other words, the MOS model of the target service in this implementation of this application is further related to one or more of the quantity of sessions, the quantity of RRC connected users, the congestion status, and the resource usage of the access network device, the radio measurement indicator of the terminal device, and the location information of the terminal device. Therefore, the MOS model of the target service is more complete.

In a possible design, before the C-NWDAF entity sends the first subscription request to the E-NWDAF entity, the method further includes: The C-NWDAF entity receives a fourth subscription request from a second network function entity, where the fourth subscription request is used to request to subscribe to the MOS model of the target service, and the second network function entity is a consumer function entity. After the C-NWDAF entity establishes the MOS model of the target service, the method further includes: The C-NWDAF entity sends the MOS model of the target service to the second network function entity. In other words, in the training method for an application MOS model provided in this implementation of this application, the C-NWDAF entity may send the first subscription request message to the E-NWDAF entity based on triggering of the consumer function entity. The consumer function entity in this implementation of this application is a requester that initiates a data analysis request or subscription to the C-NWDAF entity or the NWDAF entity. Unified descriptions are provided herein, and details are not described below again.

In a possible design, the method further includes: The C-NWDAF entity receives a fifth subscription request from a policy control entity, where the fifth subscription request is used to request to provide service experience assurance for the target service of the target terminal device, and a quality of service MOS level requirement for the service experience assurance is a first quality of service MOS level; the C-NWDAF entity sends a sixth subscription request to the E-NWDAF entity, where the sixth subscription request is used to request to subscribe to a trigger event for using the target service by the target terminal device, a second quality of service MOS level of the target service, and a corresponding first network performance indicator; after the trigger event is triggered, the C-NWDAF entity receives the second quality of service MOS level and the corresponding first network performance indicator from the E-NWDAF entity; when the second quality of service MOS level is different from the first quality of service MOS level, the C-NWDAF entity matches the first network performance indicator corresponding to the second quality of service MOS level with a first network performance indicator corresponding to the first quality of service MOS level in the MOS model of the target service, to obtain a network analysis result; and the C-NWDAF entity sends the network analysis result to the policy control entity, where the network analysis result is used for network optimization. In other words, based on the MOS model of the target service provided in this implementation of this application and with reference to current service experience quality of the terminal device, real-time service experience assurance can be provided for a user, and service experience perception of the user can be further improved.

In a possible design, the method further includes: The C-NWDAF entity receives a fifth subscription request from a policy control entity, where the fifth subscription request is used to request to provide service experience assurance for the target service of the target terminal device, and a quality of service MOS level requirement for the service experience assurance is a first quality of service MOS level; the C-NWDAF entity determines, based on a movement track of the target terminal device, that the target terminal device is to move from a service range of a first access network device to a service range of a second access network device; the C-NWDAF entity sends a sixth subscription request to the E-NWDAF entity, where the sixth subscription request is used to request to subscribe to a trigger event for using the target service by a target terminal device and a first network performance indicator associated with the second access network device; after the trigger event is triggered, the C-NWDAF entity receives the first network performance indicator associated with the second access network device from the E-NWDAF entity; the C-NWDAF entity matches the first network performance indicator associated with the second access network device with the MOS model of the target service, to determine a third quality of service MOS level of the target service corresponding to the first network performance indicator associated with the second access network device; when the third quality of service MOS level is different from the first quality of service MOS level, the C-NWDAF entity matches the first network performance indicator corresponding to the third quality of service MOS level with a first network performance indicator corresponding to the first quality of service MOS level in the MOS model of the target service, to obtain a network prediction result; and the C-NWDAF entity sends the network prediction result to the policy control entity, where the network prediction result is used for network optimization. In other words, based on the MOS model of the target service provided in this implementation of this application and with reference to current service experience quality of the terminal device, real-time service experience assurance can be provided for a user, and service experience perception of the user can be further improved.

According to a second aspect, a communication apparatus is provided. The communication apparatus includes a processor and a memory. The memory is configured to store computer instructions. When the processor executes the instructions, the communication apparatus is enabled to perform the method according to any one of the foregoing aspects. The communication apparatus is the C-NWDAF entity in the first aspect, or an apparatus including the C-NWDAF entity.

According to a third aspect, a computer program product including instructions is provided. When the computer program product runs on a computer, the computer is enabled to perform the method according to the first aspect.

With the advent of a <NUM> network, architectures of mobile networks and services carried by the mobile networks have changed greatly. The emergence of new application scenarios such as an internet of vehicles, cloud augmented reality (augmented reality, AR)/virtual reality (virtual reality, VR), high-definition live broadcast, and industrial control imposes higher end-to-end quality of service (quality of service, QoS) requirements on the <NUM> network. For example, an enhanced mobile broadband (enhanced mobile broadband, eMBB) service requires a large capacity, a high speed, and dynamic bandwidth allocation, so that gigabyte videos can be uploaded or downloaded at a high speed, and bandwidth can be dynamically allocated to services such as an ultra high-definition video and VR/AR. An ultra-reliable low-latency (ultra-reliable low-latency communication) service requires high reliability, high availability, and a low latency, to support reliable running of mission-critical (mission-critical) services such as automatic manufacturing and remote surgery, and satisfy low-latency requirements of delay-critical (delay-critical) services such as autonomous driving and unmanned aerial vehicle remote control. A massive machine type communication (massive machine type communication, mMTC) service requires a large capacity, a high speed, and dynamic bandwidth allocation, so that a connection of one billion devices can be provided for internet of things (internet of things, IoT) services such as a smart city, and a connection density can reach millions of devices per square kilometer.

QoS is designed to support on-demand customization and provide network services with differentiated quality for a service when resources are limited. As shown in <FIG>, resources (for example, an air interface bearer resource between a terminal device and an access network device or a next generation network user plane (next generation network user plane, NG-U) tunnel (tunnel) between the access network device and a UPF entity) in a network are shared by all users and services. However, different QoS rules may be allocated to different services (such as camera, WeChat, Youku, or Taobao) on demand to implement differentiated quality of service at the lowest cost.

The QoS generally has two meanings. One is a level of quality of service, namely, a specific indicator (parameter) that represents the QoS. The other one is how to guarantee these indicators, namely, a QoS implementation mechanism. A standard <NUM> QoS specification (namely, the specific indicator (parameter) that represents the QoS) is defined in the section <NUM>. <NUM> of the 3GPP <NUM>. The specification includes a <NUM> QoS identifier (<NUM> QoS identifier, 5QI) value, a corresponding resource type (resource type), a default priority level (default priority level), a packet delay budget (packet delay budget, PDB), a packet error rate (packet error rate, PER), a default (default) maximum data burst volume (maximum data burst volume, MDBV), a default averaging window (default averaging window, DAV), and an example service, as shown in Table <NUM>:.

The 5QI in Table <NUM> is defined as an end-to-end network quality of service level. Each transmission node (for example, the access network device or a core network device) in the network provides assurance for data transmission based on a QoS profile (QoS profile), but whether end-to-end service experience quality can be ensured is unknown. Therefore, an NWDAF entity is introduced in the 3GPP <NUM> and <NUM>. The NWDAF entity subscribes to a network performance indicator (a packet loss rate, an RTT, and a bit error rate) of a transmission network from a 5GC NFs entity and subscribes to a quality of service MOS level from an AF entity, so that a MOS model of a specified service is obtained through inference. The MOS model is used to help a carrier to provide, based on the QoS configuration profile, differentiated quality of service assurance for a terminal user, a third-party application (over the top, OTT) vendor carried on a carrier network, and an industry.

The following describes technical solutions in the implementations of this application with reference to accompanying drawings in the implementations of this application. It should be noted that a network architecture and a service scenario described in the implementations of this application are intended to describe the technical solutions in the implementations of this application more clearly, and do not constitute a limitation on the technical solutions provided in the implementations of this application. A person of ordinary skill in the art may know that with evolution of the network architecture and emergence of a new service scenario, the technical solutions provided in the implementations of this application are also applicable to similar technical problems.

<FIG> shows a communication system <NUM> according to an implementation of this application. The communication system <NUM> includes a C-NWDAF entity <NUM> and an E-NWDAF entity <NUM>. The C-NWDAF entity <NUM> and the E-NWDAF entity <NUM> are distributed structures of an NWDAF entity.

The E-NWDAF entity <NUM> may be deployed on a 5GC NFs side, an access network device side, or inside a terminal device. For example, the E-NWDAF entity <NUM> may be embedded in the terminal device through a software development kit (software development kit, SDK), may be co-deployed with a UPF entity through network function virtualization (network function virtualization, NFV) by using a software plug-in, or may be deployed around an access network device, the UPF entity, or the like through universal server software. In this implementation of this application, the E-NWDAF entity <NUM> is mainly configured to: collect a quality of service MOS level of a target service and a corresponding first network performance indicator, and provide the quality of service MOS level of the target service and the corresponding first network performance indicator for the C-NWDAF entity <NUM>, where the first network performance indicator is a network performance indicator of a transmission network that carries the target service.

The C-NWDAF entity <NUM> is a central node, and is mainly configured to: obtain the quality of service MOS level of the target service and the corresponding first network performance indicator from the E-NWDAF entity <NUM>, and establish a MOS model of the target service based on the quality of service MOS level of the target service and the corresponding first network performance indicator. Optionally, as shown in <FIG>, the communication system may further include one or more of a network repository function entity <NUM>, an OAM entity <NUM>, or a terminal device <NUM>. The C-NWDAF entity <NUM> may further interact with one or more of the network repository function entity <NUM>, the terminal device <NUM>, or the OAM entity <NUM> to collect data, and complete final MOS inference and analysis based on the quality of service MOS level of the target service and the corresponding first network performance indicator.

It should be noted that the entity in this implementation of this application may also be referred to as a network element. Unified descriptions are provided herein, and details are not described below again.

For a training method for an application MOS model based on the communication system, refer to subsequent method implementations.

Optionally, the terminal device in this implementation of this application may be a device configured to implement a wireless communication function, for example, a terminal, or a chip that may be used in the terminal. The terminal may be user equipment (user equipment, UE), an access terminal, a terminal unit, a terminal station, a mobile station, a remote station, a remote terminal, a mobile device, a wireless communication device, a terminal agent, a terminal apparatus, or the like in a <NUM> network or a future evolved PLMN. The access terminal may be a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device having a wireless communication function, a computing device, another processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in telemedicine (telemedicine), a wireless terminal in a smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in a smart city (smart city), a wireless terminal in a smart home (smart home), or the like. The terminal may be mobile or fixed.

Optionally, the access network device in this implementation of this application is a device that accesses a core network. For example, the access network device may be a base station, a broadband network gateway (broadband network gateway, BNG), an aggregation switch, or a non-3GPP access device. There may be base stations in various forms, for example, a macro base station, a micro base station (also referred to as a small cell), a relay station, and an access point.

Optionally, a related function of the C-NWDAF entity or the E-NWDAF entity in this implementation of this application may be implemented by one device, may be jointly implemented by a plurality of devices, or may be implemented by one or more function modules in a device. This is not specifically limited in this implementation of this application. It may be understood that the foregoing function may be a network element in a hardware device, may be a software function running on dedicated hardware, a combination of hardware and software, or a virtualization function instantiated on a platform (for example, a cloud platform).

For example, a related function of the C-NWDAF entity or the E-NWDAF entity in this implementation of this application may be implemented by a communication device <NUM> in <FIG> is a schematic diagram of a structure of the communication device <NUM> according to an implementation of this application. The communication device <NUM> includes one or more processors <NUM>, a communication line <NUM>, and at least one communication interface (in <FIG>, an example in which a communication interface <NUM> and one processor <NUM> are included is merely used for description), and optionally, may further include a memory <NUM>.

The processor <NUM> may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (application-specific integrated circuit, ASIC), or one or more integrated circuits configured to control program execution of solutions of this application.

The communication line <NUM> may include a path for connecting different components.

The communication interface <NUM> may be a transceiver module, configured to communicate with another device or a communication network, such as the Ethernet, a RAN, or a wireless local area network (wireless local area network, WLAN). For example, the transceiver module may be an apparatus such as a transceiver or a receiver and transmitter. Optionally, the communication interface <NUM> may alternatively be a transceiver circuit located in the processor <NUM>, to implement signal input and signal output of the processor.

The memory <NUM> may be an apparatus having a storage function. For example, the memory <NUM> may be a read-only memory (read-only memory, ROM) or another type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM) or another type of dynamic storage device that can store information and instructions, or may be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc read-only memory (compact disc read-only memory, CD-ROM) or another compact disc storage, an optical disc storage (including a compressed optical disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc), a magnetic disk storage medium or another magnetic storage device, or any other medium that can be used to carry or store expected program code in a form of instructions or a data structure and that can be accessed by a computer, but is not limited thereto. The memory may exist independently, and is connected to the processor by using the communication line <NUM>. The memory may alternatively be integrated with the processor.

The memory <NUM> is configured to store computer-executable instructions for executing the solutions of this application, and the processor <NUM> controls execution. The processor <NUM> is configured to execute the computer-executable instructions stored in the memory <NUM>, to implement the training method for an application MOS model provided in this implementation of this application.

Alternatively, optionally, in this implementation of this application, the processor <NUM> may implement a processing-related function in the training method for an application MOS model provided in the following implementations of this application, and the communication interface <NUM> is responsible for communicating with another device or a communication network. This is not specifically limited in this implementation of this application.

Optionally, the computer-executable instructions in this implementation of this application may also be referred to as application program code. This is not specifically limited in this implementation of this application.

During specific implementation, in an implementation, the processor <NUM> may include one or more CPUs, for example, a CPU <NUM> and a CPU <NUM> in <FIG>.

During specific implementation, in an implementation, the communication device <NUM> may include a plurality of processors, for example, the processor <NUM> and a processor <NUM> in <FIG>. Each of the processors may be a single-core (single-core) processor, or may be a multi-core (multi-core) processor. The processor herein may refer to one or more devices, circuits, and/or processing cores configured to process data (for example, computer program instructions).

During specific implementation, in an implementation, the communication device <NUM> may further include an output device <NUM> and an input device <NUM>. The output device <NUM> communicates with the processor <NUM>, and may display information in a plurality of manners. For example, the output device <NUM> may be a liquid crystal display (liquid crystal display, LCD), a light emitting diode (light emitting diode, LED) display device, a cathode ray tube (cathode ray tube, CRT) display device, a projector (projector), or the like. The input device <NUM> communicates with the processor <NUM>, and may receive an input of a user in a plurality of manners. For example, the input device <NUM> may be a mouse, a keyboard, a touchscreen device, a sensing device, or the like.

The communication device <NUM> may also be referred to as a communication apparatus sometimes, and may be a general-purpose device or a dedicated device. For example, the communication device <NUM> may be an AP, for example, a server, a router, a switch, or a bridge. Alternatively, the communication device <NUM> may be a STA, for example, a mobile phone, a tablet computer, a computer notebook, a smart watch, or a smart TV A type of the communication device <NUM> is not limited in this implementation of this application.

The following specifically describes, with reference to <FIG>, the training method for an application MOS model provided in the implementations of this application.

It should be noted that, in the following implementations of this application, names of messages or names of parameters in messages between entities are merely examples, and the messages or the parameters may have other names in a specific implementation. This is not specifically limited in the implementations of this application.

With reference to the communication system shown in <FIG>, using an example in which the network repository function entity is an NRF entity in a <NUM> network, <FIG> shows a training method for an application MOS model according to an implementation of this application.

S501: Optionally, a consumer NF entity sends a subscription request <NUM> to a C-NWDAF entity. Correspondingly, the C-NWDAF entity receives the subscription request <NUM> from the consumer NF entity, where the subscription request <NUM> is used to request to subscribe to a MOS model of a specified service.

It should be noted that step S501 is an optional step. In other words, step S501 may not be performed in the training method for an application MOS model provided in this implementation of this application. Unified descriptions are provided herein, and details are not described below again.

S502: The C-NWDAF entity sends a subscription request <NUM> to an E-NWDAF entity. Correspondingly, the E-NWDAF entity receives the subscription request <NUM> from the C-NWDAF entity, where the subscription request <NUM> is used to request to subscribe to a quality of service MOS level of a target service and a corresponding first network performance indicator, and the first network performance indicator is a network performance indicator of a transmission network that carries the target service.

Optionally, in this implementation of this application, the first network performance indicator includes one or more of the following parameters:.

It should be noted that the RTT in this implementation of this application includes an uplink RTT and a downlink RTT. The uplink RTT may be understood as a time interval between a time point at which the terminal device sends an uplink data packet and a time point at which the terminal device receives a response frame of the uplink data packet. The downlink RTT may be understood as a time interval between a time point at which the AF entity sends a downlink data packet and a time point at which the AF entity receives a response frame of the downlink data packet. Unified descriptions are provided herein, and details are not described below again.

For example, the access network device is a next generation NodeB (next generation NodeB, gNB) in the <NUM> network, and the user plane entity is a UPF entity in the <NUM> network. <FIG> is a schematic diagram of a first network performance indicator according to an implementation of this application. The first network performance indicator includes one or more of a network performance indicator between the terminal device and the gNB, a network performance indicator between the gNB and the UPF entity, or a network performance indicator between the UPF entity and the AF entity.

S503: The E-NWDAF entity obtains the quality of service MOS level of the target service and the corresponding first network performance indicator.

Optionally, in this implementation of this application, the E-NWDAF entity may collect original service data of a user through traffic mirroring, implantation of an NF proxy, or the like, and complete the following processing:.

S504: The E-NWDAF entity sends a notification message <NUM> to the C-NWDAF entity. The C-NWDAF entity receives the notification message <NUM> from the E-NWDAF entity, where the notification message <NUM> includes the quality of service MOS level of the target service and the corresponding first network performance indicator.

Optionally, the training method for an application MOS model provided in this implementation of this application may further include the following steps S505 to S507.

S505: The C-NWDAF entity sends a subscription request <NUM> to the NRF entity/a 5GC NFs entity. Correspondingly, the NRF entity/the 5GC NFs entity receives the subscription request <NUM> from the C-NWDAF entity, where the subscription request <NUM> is used to request to subscribe to first load of the 5GC NFs entity.

Optionally, in this implementation of this application, the first load of the 5GC NFs entity includes one or more of the following parameters:
a quantity of sessions of the 5GC NFs entity, a quantity of users of the 5GC NFs entity, and resource usage of the 5GC NFs entity.

For example, the resource usage of the 5GC NFs entity may include, for example, CPU, memory, or network I/O usage.

S506: The NRF entity/the 5GC NFs entity obtains the first load of the 5GC NFs entity.

S507: The NRF entity/the 5GC NFs entity sends a notification message <NUM> to the C-NWDAF entity. Correspondingly, the C-NWDAF entity receives the notification message <NUM> from the NRF entity/the 5GC NFs entity, where the notification message <NUM> includes the first load of the 5GC NFs entity.

Optionally, the training method for an application MOS model provided in this implementation of this application may further include the following steps S508 to S510.

S508: The C-NWDAF entity sends a subscription request <NUM> to an OAM. Correspondingly, the OAM entity receives the subscription request <NUM> from the C-NWDAF entity, where the subscription request <NUM> is used to request to subscribe to a second network performance indicator, and the second network performance indicator is a performance indicator of a radio network that carries the target service.

Optionally, in this implementation of this application, the second network performance indicator includes one or more of the following parameters:
a quantity of sessions, a quantity of RRC connected users, a congestion status, and resource usage of the access network device, a radio measurement indicator of the terminal device, and location information of the terminal device.

For example, the quantity of RRC connected users may include, for example, a quantity of users in an RRC_inactive (inactive) state and a quantity of users in an RRC_active (active) state.

For example, the resource usage of the access network device may include, for example, uplink or downlink physical resource block (physical resource block, PRB) usage, or CPU or memory usage.

For example, the radio measurement indicator of the terminal device may include, for example, reference signal received power (reference signal received power, RSRP), reference signal received quality (reference signal receiving quality, RSRQ), or a signal-to-interference plus noise ratio (signal to interference plus noise ratio, SINR).

S509: The OAM entity obtains the second network performance indicator.

S510: The OAM entity sends a notification message <NUM> to the C-NWDAF entity. Correspondingly, the C-NWDAF entity receives the notification message <NUM> from the OAM, where the notification message <NUM> includes the second network performance indicator.

Optionally, the training method for an application MOS model provided in this implementation of this application may further include the following step S511.

S511: The terminal device sends a measurement report to the C-NWDAF entity. Correspondingly, the C-NWDAF entity receives the measurement report from the terminal device. The measurement report includes information about the terminal device and one or more of the following information: the quality of service MOS level of the target service, the quantity of lost uplink packets, the uplink packet loss rate, the quantity of lost downlink packets, the downlink packet loss rate, the RTT, the average uplink packet interval, the average uplink packet jitter, the average downlink packet interval, the average downlink packet jitter, the uplink rate, and the downlink rate on the corresponding path between the terminal device and the access network device, or the radio measurement indicator of the terminal device.

For example, the information about the terminal device may include, for example, a model, a CPU, or a memory capacity of the terminal device.

After the C-NWDAF entity obtains the required information, the training method for an application MOS model provided in this implementation of this application may further include the following step S512.

S512: The C-NWDAF entity establishes the MOS model of the target service based on the quality of service MOS level and the first network performance indicator. The MOS model of the target service includes a model relationship between the quality of service MOS level and the first network performance indicator.

According to the claimed invention, when steps S505 to S507, steps S508 to S510, or step S511 are/is performed, that the C-NWDAF entity establishes the MOS model of the target service based on the quality of service MOS level and the first network performance indicator includes: The C-NWDAF entity excludes a sample whose quality of service MOS is poor due to an exception of the terminal device and a sample whose quality of service MOS is poor due to an exception of the AF entity based on the quality of service MOS level, the first network performance indicator, the measurement report of the terminal device, and the second network performance indicator and/or the first load of the 5GC NFs entity, and establishes the MOS model of the target service. In this case, the MOS model of the target service includes a model relationship between the quality of service MOS level and the second network performance indicator and/or the first load of the 5GC NFs entity, and the model relationship between the quality of service MOS level and the first network performance indicator.

Optionally, in this implementation of this application, if step S501 is performed, the training method for an application MOS model provided in this implementation of this application may further include the following step S513.

S513: The C-NWDAF entity sends a notification message <NUM> to the consumer NF entity. Correspondingly, the consumer NF entity receives the notification message <NUM> from the C-NWDAF entity, where the notification message <NUM> includes the MOS model of the target service.

Optionally, in this implementation of this application, the consumer NF entity in an area managed by the E-NWDAF entity may alternatively directly subscribe to the MOS model of the specified service from the E-NWDAF entity. Further, after obtaining the quality of service MOS level of the target service and the corresponding first network performance indicator, the E-NWDAF entity establishes the MOS model of the target service based on the quality of service MOS level and the first network performance indicator, and sends the MOS model of the target service to the consumer NF entity in the area managed by the E-NWDAF entity. This is not specifically limited in this implementation of this application. Certainly, the terminal device may alternatively send the measurement report to the E-NWDAF entity, and the E-NWDAF entity may subscribe to the quality of service MOS level and the second network performance indicator and/or the first load of the 5GC NFs entity. Further, the E-NWDAF entity may exclude a sample whose quality of service MOS is poor due to an exception of the terminal device and a sample whose quality of service MOS is poor due to an exception of the AF entity based on the quality of service MOS level, the first network performance indicator, the measurement report of the terminal device, and the second network performance indicator and/or the first load of the 5GC NFs entity, and establishes the MOS model of the target service. This is not specifically limited in this implementation of this application.

Optionally, in this implementation of this application, after obtaining the MOS model of the target service, the C-NWDAF entity or the E-NWDAF entity may generate a recommended QoS file based on the MOS model of the target service, to help a carrier to provide differentiated quality of service assurance for a terminal user, an OTT vendor, and an industry. If the consumer NF entity receives the recommended QoS file sent by the C-NWDAF entity or the E-NWDAF entity, the consumer NF entity may select, based on a preconfigured priority rule or a corresponding determining algorithm, a corresponding QoS file to be used. Unified descriptions are provided herein, and details are not described below again.

Based on the training method for an application MOS model provided in this implementation of this application, in this implementation of this application, the carrier deploys distributed NWDAF entities including the C-NWDAF entity and the E-NWDAF entity, the C-NWDAF entity may subscribe to the quality of service MOS level of the target service and the corresponding first network performance indicator from the E-NWDAF entity, and the E-NWDAF entity obtains the quality of service MOS level of the target service and the corresponding first network performance indicator through synchronous measurement, that is, the E-NWDAF entity obtains the quality of service MOS level of the target service and the corresponding first network performance indicator inside the carrier. Therefore, implementation is easier, and a measurement result is more accurate. In another aspect, because the first network performance indicator, the sample whose quality of service MOS is poor due to the exception of the terminal device, the sample whose quality of service MOS is poor due to the exception of the AF entity, and the performance indicator of the radio network that carries the target service and/or the first load of the 5GC NFs entity corresponding to the MOS level are considered, the MOS model that is of the target service and that is established by using the training method for an application MOS model provided in this implementation of this application is more accurate and comprehensive.

An action of the C-NWDAF entity or the E-NWDAF entity in steps S501 to S513 may be performed by the processor <NUM> in the communication device <NUM> shown in <FIG> by invoking the application program code stored in the memory <NUM>. This is not limited in this implementation of this application.

The following provides a related example of providing real-time service experience assurance for the user based on the MOS model of the target service provided in this implementation of this application and with reference to current service experience quality of the terminal device.

Example <NUM>: Service experience assurance in the <NUM> network is used as an example. As shown in <FIG>, a service experience assurance method according to an implementation of this application includes the following steps.

S701: An AF entity applies to a policy control function (policy control function, PCF) entity through a network exposure function (network exposure function, NEF) entity to provide service experience assurance for a target service of a target terminal device.

Optionally, in this implementation of this application, for a trusted application, the AF entity may alternatively directly apply to the PCF entity to provide the service experience assurance for the target service. This is not specifically limited in this implementation of this application.

Optionally, the service experience assurance in this implementation of this application may alternatively be replaced with QoS optimization. Unified descriptions are provided herein, and details are not described below again.

S702: The PCF entity sends a subscription request <NUM> to a C-NWDAF entity. Correspondingly, the C-NWDAF entity receives the subscription request <NUM> from the PCF entity, where the subscription request <NUM> is used to request to provide the service experience assurance for the target service of the target terminal device, and a quality of service MOS level requirement for the service experience assurance is a first quality of service MOS level.

S703: The C-NWDAF entity sends a subscription request <NUM> to an E-NWDAF entity. Correspondingly, the E-NWDAF entity receives the subscription request <NUM> from the C-NWDAF entity, where the subscription request <NUM> is used to request to subscribe to a trigger event for using the target service by the target terminal device, a second quality of service MOS level of the target service, and a corresponding first network performance indicator.

For related descriptions of the first network performance indicator, refer to the implementation shown in <FIG>.

S704: After the trigger event is triggered, the E-NWDAF entity obtains the second quality of service MOS level of the target service and the corresponding first network performance indicator, and sends a notification message <NUM> to the C-NWDAF entity, where the notification message <NUM> includes the second quality of service MOS level of the current target service and the corresponding first network performance indicator.

S705: The C-NWDAF entity sends a subscription request <NUM> to an OAM. Correspondingly, the OAM entity receives the subscription request <NUM> from the C-NWDAF entity, where the subscription request <NUM> is used to request to subscribe to a second network performance indicator.

For related descriptions of the second network performance indicator, refer to the implementation shown in <FIG>.

S706: After obtaining the second network performance indicator, the OAM entity sends a notification message <NUM> to the C-NWDAF entity. Correspondingly, the C-NWDAF entity receives the notification message <NUM> from the OAM, where the notification message <NUM> includes the current second network performance indicator.

S707: When the second quality of service MOS level is different from the first quality of service MOS level, the C-NWDAF entity matches the first network performance indicator corresponding to the second quality of service MOS level with a first network performance indicator corresponding to the first quality of service MOS level in a MOS model of the target service, and the C-NWDAF entity matches a second network performance indicator corresponding to the second quality of service MOS level with a second network performance indicator corresponding to the first quality of service MOS level in the MOS model of the target service, to obtain a network analysis result.

Optionally, the network analysis result in this implementation of this application is used to represent a reason why the second quality of service MOS level is different from the first quality of service MOS level. For example, a network performance indicator between the terminal device and a current access network device is poor, a network performance indicator between the current access network device and a UPF entity is poor, or a network performance indicator between the UPF entity and the AF entity is poor. This is not specifically limited herein.

It should be noted that steps S705 and S706 are optional steps. If steps S705 and S706 are not performed, in step S707, the C-NWDAF entity does not need to match the second network performance indicator corresponding to the second quality of service MOS level with the second network performance indicator corresponding to the first quality of service MOS level in the MOS model of the target service. Unified descriptions are provided herein, and details are not described below again.

S708: The C-NWDAF entity sends a notification message <NUM> to the PCF entity. Correspondingly, the PCF entity receives the notification message <NUM> from the C-NWDAF entity, where the notification message <NUM> includes the network analysis result.

Optionally, in this implementation of this application, the PCF entity may notify, based on the network analysis result, a session management function (session management function, SMF) entity or the UPF entity to update a QoS policy and network parameter optimization of the terminal device, for example, a radio scheduling priority or a transport layer differentiated services code point (differentiated services code point, DSCP) level. This is not specifically limited in this implementation of this application.

<FIG> is a schematic diagram of an architecture corresponding to the service experience assurance method shown in <FIG>. Based on the service experience assurance method provided in this implementation of this application, real-time service experience assurance can be provided for a user.

Example <NUM>: Service experience assurance in the <NUM> network is used as an example. As shown in <FIG>, another service experience assurance method according to an implementation of this application includes the following steps.

S901: An AF entity applies to a PCF entity through an NEF entity to provide service experience assurance for a target service of a target terminal device.

Optionally, in this implementation of this application, for a trusted application, the AF entity may directly apply to the PCF entity to provide the service experience assurance for the target service. This is not specifically limited in this implementation of this application.

S902: The PCF entity sends a subscription request <NUM> to a C-NWDAF entity. Correspondingly, the C-NWDAF entity receives the subscription request <NUM> from the PCF entity, where the subscription request <NUM> is used to request to provide the service experience assurance for the target service of the target terminal device, and a quality of service MOS level requirement for the service experience assurance is a first quality of service MOS level.

S903: The C-NWDAF entity determines, based on a movement track of the target terminal device, that the target terminal device is to move from a service range of a first access network device to a service range of a second access network device.

Optionally, in this implementation of this application, the movement track of the target terminal device may be obtained by an E-NWDAF entity and then sent to the C-NWDAF entity, or may be obtained by the C-NWDAF entity in another manner. This is not specifically limited in this implementation of this application.

S904: The C-NWDAF entity sends a subscription request <NUM> to the E-NWDAF entity. Correspondingly, the E-NWDAF entity receives the subscription request <NUM> from the C-NWDAF entity, where the subscription request <NUM> is used to request to subscribe to a trigger event for using the target service by the target terminal device and a first network performance indicator associated with the second access network device.

For example, in this implementation of this application, the first network performance indicator associated with the second access network device may include, for example, one or more of the following parameters:.

S905: After the trigger event is triggered, the E-NWDAF entity obtains the first network performance indicator associated with the second access network device, and sends a notification message <NUM> to the C-NWDAF entity, where the notification message <NUM> includes the first network performance indicator associated with the second access network device.

S906: The C-NWDAF entity sends a subscription request <NUM> to an OAM. Correspondingly, the OAM entity receives the subscription request <NUM> from the C-NWDAF entity, where the subscription request <NUM> is used to request to subscribe to a second network performance indicator associated with the second access network device.

Optionally, in this implementation of this application, the second network performance indicator associated with the second access network device includes one or more of the following parameters:
a quantity of sessions, a quantity of RRC connected users, a congestion status, and resource usage of the second access network device, a radio measurement indicator of the terminal device, and location information of the terminal device. For related descriptions of the quantity of RRC connected users, the resource usage, and the radio measurement indicator of the terminal device, refer to descriptions in the implementation shown in <FIG>.

S907: After obtaining the second network performance indicator associated with the second access network device, the OAM entity sends a notification message <NUM> to the C-NWDAF entity. Correspondingly, the C-NWDAF entity receives the notification message <NUM> from the OAM, where the notification message <NUM> includes the second network performance indicator associated with the second access network device.

S908: The C-NWDAF entity matches the first network performance indicator and the second network performance indicator that are associated with the second access network device with a MOS model of the target service, to determine a third quality of service MOS level of the target service corresponding to the first network performance indicator and the second network performance indicator that are associated with the second access network device.

S909: When the third quality of service MOS level is different from the first quality of service MOS level, the C-NWDAF entity matches the first network performance indicator corresponding to the third quality of service MOS level with a first network performance indicator corresponding to the first quality of service MOS level in the MOS model of the target service, and the C-NWDAF entity matches the second network performance indicator corresponding to the third quality of service MOS level with a second network performance indicator corresponding to the first quality of service MOS level in the MOS model of the target service, to obtain a network prediction result.

Optionally, the network prediction result in this implementation of this application is used to represent a reason why the third quality of service MOS level is different from the first quality of service MOS level. For example, a network performance indicator between the terminal device and a current access network device is poor, a network performance indicator between the current access network device and a UPF entity is poor, or a network performance indicator between the UPF entity and the AF entity is poor. This is not specifically limited herein.

It should be noted that steps S906 and S907 are optional steps. If steps S906 and S907 are not performed, in step S908, the C-NWDAF entity does not need to match the second network performance indicator associated with the second access network device with the MOS model of the target service, and only needs to determine the third quality of service MOS level of the target service corresponding to the first network performance indicator associated with the second access network device. In addition, if steps S906 and S907 are not performed, in step S909, the C-NWDAF entity does not need to match the second network performance indicator corresponding to the third quality of service MOS level with the second network performance indicator corresponding to the first quality of service MOS level in the MOS model of the target service. Unified descriptions are provided herein, and details are not described below again.

S910: The C-NWDAF entity sends a notification message <NUM> to the PCF entity. Correspondingly, the PCF entity receives the notification message <NUM> from the C-NWDAF entity, where the notification message <NUM> includes the network prediction result.

Optionally, in this implementation of this application, the PCF entity may recommend, based on the network prediction result, the UPF entity to update a QoS policy of the user after entering the service range of the second access network device. This is not specifically limited in this implementation of this application.

It may be understood that, in the foregoing implementations, the methods and/or steps implemented by the C-NWDAF entity may also be implemented by a component used in the C-NWDAF entity, and the methods and/or steps implemented by the E-NWDAF entity may also be implemented by a component used in the E-NWDAF entity.

The foregoing mainly describes the solutions provided in the implementations of this application from the perspective of interaction between entities. Correspondingly, an implementation of this application further provides a communication apparatus. The communication apparatus may be the C-NWDAF entity in the foregoing method implementations, an apparatus including the C-NWDAF entity, or a component that may be used in the C-NWDAF entity. Alternatively, the communication apparatus may be the E-NWDAF entity in the foregoing method implementations, an apparatus including the E-NWDAF entity, or a component that can be used in the E-NWDAF entity. It can be understood that, to implement the foregoing functions, the communication apparatus includes a corresponding hardware structure and/or software module for implementing the functions. A person skilled in the art should be easily aware that, in combination with the units and algorithm steps in the examples described in the implementations disclosed in this specification, this application may be implemented by hardware or a combination of hardware and computer software. Whether a function is performed by hardware or hardware driven by computer software depends on particular applications and design constraints of the technical solutions.

For example, the communication apparatus is the C-NWDAF entity in the foregoing method implementations. <FIG> is a schematic diagram of a structure of a C-NWDAF entity <NUM>. The C-NWDAF entity <NUM> includes a transceiver module <NUM> and a processing module <NUM>. The transceiver module <NUM> may also be referred to as a transceiver unit, and is configured to implement a transceiver function. For example, the transceiver module <NUM> may be a transceiver circuit, a transceiver, or a communication interface.

The transceiver module <NUM> is configured to send a first subscription request to an E-NWDAF entity, where the first subscription request is used to request to subscribe to a quality of service MOS level of a target service and a corresponding first network performance indicator, and the first network performance indicator is a network performance indicator of a transmission network that carries the target service. The transceiver module <NUM> is further configured to receive the quality of service MOS level and the first network performance indicator from the E-NWDAF entity. The processing module <NUM> is configured to establish a MOS model of the target service based on the quality of service MOS level and the first network performance indicator.

According to the claimed invention, the processing module <NUM> is further configured to obtain a second network performance indicator corresponding to the MOS level and/or first load of a first network function entity corresponding to the MOS level, where the second network performance indicator is a performance indicator of a radio network that carries the target service, and the first network function entity is a network data provider function entity. That the processing module <NUM> is configured to establish a MOS model of the target service based on the quality of service MOS level and the first network performance indicator includes: The processing module <NUM> is configured to: exclude a sample whose quality of service MOS is poor due to an exception of a terminal device and a sample whose quality of service MOS is poor due to an exception of an application function entity based on the second network performance indicator, the first load of the first network function entity, the quality of service MOS level, and the first network performance indicator, and establish the MOS model of the target service.

Optionally, that the processing module <NUM> is configured to obtain first load of a first network function entity corresponding to the MOS level includes: The processing module <NUM> is configured to: send a second subscription request to a network repository function entity through the transceiver module <NUM>, where the second subscription request is used to request to subscribe to the first load of the first network function entity; and receive the first load of the first network function entity from the network repository function entity through the transceiver module <NUM>.

Optionally, that the processing module <NUM> is configured to obtain a second network performance indicator corresponding to the MOS level includes: The processing module <NUM> is configured to: send a third subscription request to an operation administration and maintenance OAM entity of a carrier network through the transceiver module <NUM>, where the third subscription request is used to request to subscribe to the second network performance indicator; and receive the second network performance indicator from the OAM entity through the transceiver module <NUM>.

Optionally, the transceiver module <NUM> is further configured to receive a fourth subscription request from a second network function entity, where the fourth subscription request is used to request to subscribe to the MOS model of the target service, and the second network function entity is a consumer function entity. The transceiver module <NUM> is further configured to send the MOS model of the target service to the second network function entity.

Optionally, the transceiver module <NUM> is further configured to receive a fifth subscription request from a policy control entity, where the fifth subscription request is used to request to provide service experience assurance for the target service of the target terminal device, and a quality of service MOS level requirement for the service experience assurance is a first quality of service MOS level. The transceiver module <NUM> is further configured to send a sixth subscription request to the E-NWDAF entity, where the sixth subscription request is used to request to subscribe to a trigger event for using the target service by the target terminal device, a second quality of service MOS level of the target service, and a corresponding first network performance indicator. The transceiver module <NUM> is further configured to: after the trigger event is triggered, receive the second quality of service MOS level and the corresponding first network performance indicator from the E-NWDAF entity. The processing module <NUM> is further configured to: when the second quality of service MOS level is different from the first quality of service MOS level, match the first network performance indicator corresponding to the second quality of service MOS level with a first network performance indicator corresponding to the first quality of service MOS level in the MOS model of the target service, to obtain a network analysis result. The transceiver module <NUM> is further configured to send the network analysis result to the policy control entity, where the network analysis result is used for network optimization.

Optionally, the transceiver module <NUM> is further configured to receive a fifth subscription request from a policy control entity, where the fifth subscription request is used to request to provide service experience assurance for the target service of the target terminal device, and a quality of service MOS level requirement for the service experience assurance is a first quality of service MOS level. The processing module <NUM> is further configured to determine, based on a movement track of the target terminal device, that the target terminal device is to move from a service range of a first access network device to a service range of a second access network device. The transceiver module <NUM> is further configured to send a sixth subscription request to the E-NWDAF entity, where the sixth subscription request is used to request to subscribe to a trigger event for using the target service by a target terminal device and a first network performance indicator associated with the second access network device. The transceiver module <NUM> is further configured to: after the trigger event is triggered, receive the first network performance indicator associated with the second access network device from the E-NWDAF entity. The processing module <NUM> is further configured to match the first network performance indicator associated with the second access network device with the MOS model of the target service, to determine a third quality of service MOS level of the target service corresponding to the first network performance indicator associated with the second access network device. The processing module <NUM> is further configured to: when the third quality of service MOS level is different from the first quality of service MOS level, match the first network performance indicator corresponding to the third quality of service MOS level with a first network performance indicator corresponding to the first quality of service MOS level in the MOS model of the target service, to obtain a network prediction result. The transceiver module <NUM> is further configured to send the network prediction result to the policy control entity, where the network prediction result is used for network optimization.

All related content of the steps in the foregoing method implementations may be cited in function descriptions of a corresponding function module.

In this implementation, the C-NWDAF entity <NUM> is presented in a form of function modules obtained through division in an integrated manner. The "module" herein may be an application-specific integrated circuit ASIC, a circuit, a processor executing one or more software or firmware programs, a memory, an integrated logic circuit, and/or another device that can provide the foregoing function. In a simple implementation, a person skilled in the art may figure out that the C-NWDAF entity <NUM> may be in a form of the communication device <NUM> shown in <FIG>.

For example, the processor <NUM> in the communication device <NUM> shown in <FIG> may invoke the computer-executable instructions stored in the memory <NUM>, to enable the communication device <NUM> to perform the training method for an application MOS model in the foregoing method implementations.

Specifically, functions/implementation processes of the transceiver module <NUM> and the processing module <NUM> in <FIG> may be implemented by the processor <NUM> in the communication device <NUM> in <FIG> by invoking the computer-executable instructions stored in the memory <NUM>. Alternatively, functions/implementation processes of the processing module <NUM> in <FIG> may be implemented by the processor <NUM> in the communication device <NUM> shown in <FIG> by invoking the computer-executable instructions stored in the memory <NUM>. Functions/implementation processes of the transceiver module <NUM> in <FIG> may be implemented by the communication interface <NUM> in the communication device <NUM> shown in <FIG>.

The C-NWDAF entity <NUM> provided in this implementation can perform the foregoing training method for an application MOS model. Therefore, for a technical effect that can be achieved by the C-NWDAF entity <NUM>, refer to the foregoing method implementations.

For example, the communication apparatus is the E-NWDAF entity in the foregoing method implementations. <FIG> is a schematic diagram of a structure of an E-NWDAF entity <NUM>. The E-NWDAF entity <NUM> includes a transceiver module <NUM> and a processing module <NUM>. The transceiver module <NUM> may also be referred to as a transceiver unit, and is configured to implement a transceiver function. For example, the transceiver module <NUM> may be a transceiver circuit, a transceiver, or a communication interface.

The transceiver module <NUM> is configured to receive a first subscription request from a C-NWDAF entity, where the first subscription request is used to request to subscribe to a quality of service mean opinion score MOS level of a target service and a corresponding first network performance indicator, and the first network performance indicator is a network performance indicator of a transmission network that carries the target service. The processing module <NUM> is configured to obtain the quality of service MOS level and the first network performance indicator. The transceiver module <NUM> is further configured to send the quality of service MOS level and the first network performance indicator to the C-NWDAF entity.

Optionally, that the processing module <NUM> is configured to obtain the quality of service MOS level includes: The processing module <NUM> is configured to: obtain service experience data of the target service, and determine the quality of service MOS level based on the service experience data of the target service.

In this implementation, the E-NWDAF entity <NUM> is presented in a form of function modules obtained through division in an integrated manner. The "module" herein may be an application-specific integrated circuit ASIC, a circuit, a processor executing one or more software or firmware programs, a memory, an integrated logic circuit, and/or another device that can provide the foregoing function. In a simple implementation, a person skilled in the art may figure out that the E-NWDAF entity <NUM> may be in a form of the communication device <NUM> shown in <FIG>.

The E-NWDAF entity <NUM> provided in this implementation can perform the foregoing training method for an application MOS model. Therefore, for a technical effect that can be achieved by the E-NWDAF entity <NUM>, refer to the foregoing method implementations.

It should be noted that one or more of the foregoing modules or units may be implemented by using software, hardware, or a combination thereof. When any one of the foregoing modules or units is implemented by using software, the software exists in a manner of computer program instructions and is stored in a memory. A processor may be configured to: execute the program instructions and implement the foregoing method procedure. The processor may be built into a SoC (system-on-a-chip) or an ASIC, or may be an independent semiconductor chip. In addition to a core configured to execute software instructions to perform an operation or processing, the processor may further include a necessary hardware accelerator, such as a field programmable gate array (field programmable gate array, FPGA), a PLD (programmable logic device), or a logic circuit that implements a dedicated logic operation.

When the foregoing modules or units are implemented by using hardware, the hardware may be any one or any combination of a CPU, a microprocessor, a digital signal processing (digital signal processing, DSP) chip, a microcontroller unit (microcontroller unit, MCU), an artificial intelligence processor, an ASIC, a SoC, an FPGA, a PLD, a dedicated digital circuit, a hardware accelerator, or a non-integrated discrete device, and the hardware may run necessary software or be independent of software to perform the foregoing method procedure.

Optionally, the implementations of this application further provide a communication apparatus (for example, the communication apparatus may be a chip or a chip system). The communication apparatus includes a processor, configured to implement the method in any one of the foregoing method implementations. In a possible design, the communication apparatus further includes a memory. The memory is configured to store necessary program instructions and data. The processor may invoke program code stored in the memory, to indicate the communication apparatus to perform the method in any one of the foregoing method implementations. Certainly, the memory may not be in the communication apparatus. When the communication apparatus is a chip system, the chip system may include a chip, or include a chip and other discrete devices. This is not specifically limited in this implementation of this application.

In the descriptions of this application, "/" indicates that associated objects are in an "or" relationship unless otherwise specified. For example, A/B may represent A or B. In this application, "and/or" describes only an association relationship for describing associated objects and represents that three relationships may exist. In the three cases, A. B may be singular or plural. In addition, in the descriptions of this application, "a plurality of" means two or more than two unless otherwise specified. "At least one of the following items (pieces)" or a similar expression thereof means any combination of these items, including any combination of singular items (pieces) or plural items (pieces). For example, at least one of a, b, or c may indicate: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be singular or plural. In addition, to clearly describe the technical solutions in the implementations of this application, terms such as "first" and "second" are used in the implementations of this application to distinguish between same items or similar items that provide basically same functions or purposes. A person skilled in the art may understand that the terms such as "first" and "second" do not limit a quantity and an execution sequence, and the terms such as "first" and "second" do not indicate a definite difference. In addition, in the implementations of this application, a word such as "example" or "for example" is used to represent giving an example, an illustration, or a description. Any implementation or design scheme described as an "example" or with "for example" in the implementations of this application should not be explained as being more preferred or having more advantages than another implementation or design scheme. Exactly, use of the word "example", "for example", or the like is intended to present a relative concept in a specific manner for ease of understanding.

All or some of the foregoing implementations may be implemented by using software, hardware, firmware, or any combination thereof. When a software program is used to implement the implementations, all or some of the implementations may be implemented in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, all or some of the procedures or functions are generated according to the implementations of this application. The computer may be a general-purpose computer, a dedicated computer, a computer network, or another programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (digital subscriber line, DSL)) or wireless (for example, infrared, radio, or microwave) manner. The computer-readable storage medium may be any usable medium accessible by the computer, or a data storage device, such as a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a solid-state drive (solid-state drive, SSD)), or the like.

Although this application is described with reference to the implementations, in a process of implementing this application that claims protection, a person skilled in the art may understand and implement another variation of the disclosed implementations by viewing the accompanying drawings, disclosed content, and the accompanying claims. In the claims, "comprising" (comprising) does not exclude another component or another step, and "a" or "one" does not exclude a case of "a plurality of". A single processor or another unit may implement several functions enumerated in the claims. Some measures are recorded in dependent claims that are different from each other, but this does not mean that these measures cannot be combined to produce a great effect.

Claim 1:
A training method for an application mean opinion score, MOS, model, wherein the method comprises:
sending (S502), by a central network data analytics function, C-NWDAF, entity, a first subscription request to an edge network data analytics function, E-NWDAF, entity, wherein the first subscription request is used to request to subscribe to a quality of service MOS level of a target service and a corresponding first network performance indicator, and the first network performance indicator is a network performance indicator of a transmission network that carries the target service;
receiving (S504), by the C-NWDAF entity, the quality of service MOS level and the first network performance indicator from the E-NWDAF entity; and
establishing (S512), by the C-NWDAF entity, a MOS model of the target service based on the quality of service MOS level and the first network performance indicator;
wherein the method further comprises:
obtaining (S505-S507, S508-S510), by the C-NWDAF entity, a second network performance indicator corresponding to the MOS level and/or first load of a first network function entity corresponding to the MOS level, wherein the second network performance indicator is a performance indicator of a radio network that carries the target service, and the first network function entity is a network data provider function entity; and
the establishing, by the C-NWDAF entity, a MOS model of the target service based on the quality of service MOS level and the first network performance indicator comprises:
excluding, by the C-NWDAF entity, a sample whose quality of service MOS is poor due to an exception of the terminal device and a sample whose quality of service MOS is poor due to an exception of the application function entity based on the quality of service MOS level, the first network performance indicator, and the second network performance indicator and/or the first load of the first network function entity; and establishing the MOS model of the target service.