A communication method and apparatus

CN122373017APending Publication Date: 2026-07-10HUAWEI TECH CO LTD

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
HUAWEI TECH CO LTD
Filing Date
2025-01-08
Publication Date
2026-07-10

AI Technical Summary

Technical Problem

In existing technologies, the QoE information configuration latency for audio and video communication is relatively long, and it relies on DCAF and OAM technologies, making it difficult to transmit and configure efficiently, which affects the user experience.

Method used

QoE and configuration information are transmitted directly through the control plane. NAS signaling and PDU sessions are used to reduce signaling overhead and latency. Container transmission is adopted to improve efficiency, and configuration information is matched according to the QoE reporting capability of the terminal device.

Benefits of technology

It enables rapid transmission and configuration of QoE information, reduces latency and signaling overhead, improves the efficiency of reporting user experience quality, and is easy to commercially deploy.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122373017A_ABST
    Figure CN122373017A_ABST
Patent Text Reader

Abstract

A communication method and device are used to guarantee reporting of QoE information. The method comprises the following steps: a network data analysis function network element sends first configuration information through a control plane or a user plane. A terminal device collects QoE information according to the first configuration information and sends the QoE information through the control plane or the user plane. Based on this, the network data analysis function network element and the terminal device can directly transmit the first configuration information and the QoE information through the CP or the UP, without needing to pass through OAM and AF to acquire, so that the reporting delay of the QoE information can be reduced, and the network data analysis function network element does not need to rely on DCAF technology and OAM technology to acquire the QoE information from the terminal device, and is more likely to be commercially landed.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] Audio and video communication has become an essential part of users' daily lives and work. However, due to the complexity and variability of the network environment, the quality of audio and video communication is often severely affected. Quality of Service (QoS) and Quality of Experience (QoE) are two important indicators for measuring the quality of audio and video communication.

[0003] QoE can accurately assess user experience, thereby improving user experience. Therefore, QoE reporting is crucial for improving user experience. Summary of the Invention

[0004] This application provides a communication method and apparatus to ensure the reporting of QoE information.

[0005] Firstly, this application provides a communication method that can be applied to a communication device, which can be a terminal device, or a processor, chip, chip system, circuit, or functional module within the terminal device. The method may include: receiving first configuration information via a first non-access stratum (NAS) signaling, the first configuration information being used to instruct the terminal device to collect or report QoE information; and collecting or reporting QoE information according to the first configuration information.

[0006] Using the above method, the network data analysis function network element and the terminal device can directly transmit the first configuration information through the control plane without going through OAM and AF to trigger the configuration. This can reduce the latency of QoE information configuration, and the network data analysis function network element does not need to rely on DCAF technology or OAM technology to obtain QoE information from the terminal device, making it easier to commercially deploy.

[0007] In one possible design, the first NAS signaling may include a first container, which contains the first configuration information. Transmitting the first configuration information through a container reduces transmission latency and improves transmission efficiency.

[0008] In one possible design, the first NAS signaling is a registration accept message, a downlink transmission message, or a session accept message. This allows existing messages to be reused to transmit the first configuration information, saving signaling overhead.

[0009] In one possible design, the QoE information is sent via a second NAS signaling. Terminal devices directly report QoE information through the control plane, which reduces QoE information transmission latency. Furthermore, network data analysis elements do not need to rely on DCAF or OAM technologies to obtain QoE information from terminal devices, making it easier for commercial deployment.

[0010] In one possible design, the second NAS signaling is a registration request message, an uplink transmission message, or a session request message. This allows existing messages to be reused to transmit QoE information, saving signaling overhead.

[0011] In one possible design, the second NAS signaling includes a second container, which contains the QoE information. Transmitting QoE information through a container reduces QoE information transmission latency and improves QoE information transmission efficiency.

[0012] In one possible design, the QoE information is sent via the user plane. Transmitting QoE information directly via the user plane can reduce QoE information transmission latency and improve QoE information transmission efficiency.

[0013] In one possible design, the QoE information can be sent via the user plane by: establishing a Protocol Data Unit (PDU) session for transmitting QoE information; and sending the QoE information through the PDU session. Directly transmitting QoE information through the PDU session can reduce QoE information transmission latency and improve QoE information transmission efficiency.

[0014] In one possible design, a first message is received, the first message including first indication information, which instructs the establishment of a PDU session for transmitting QoE information. This allows the terminal device to establish a PDU session for transmitting QoE information, enabling direct transmission of QoE information through the PDU session, thereby reducing QoE information transmission latency and improving QoE information transmission efficiency.

[0015] In one possible design, the first message includes a routing policy rule, which in turn includes the first indication information. This allows the first indication information to be carried within an existing routing policy rule, saving signaling overhead.

[0016] In one possible design, the routing policy rule includes a traffic descriptor, which includes the first indication information. This allows the first indication information to be carried within existing routing policy rules, saving signaling overhead.

[0017] In one possible design, a third message is sent to request the establishment of a secure connection. This ensures the secure transmission of QoE information.

[0018] In one possible design, the first configuration information is determined based on the QoE reporting capabilities supported by the terminal device. Based on this, the network data analysis function network element can configure configuration information that matches the QoE reporting capabilities of the terminal device, so that the terminal device reports QoE information matching its own capabilities.

[0019] In one possible design, a second message is sent, which contains information about the QoE reporting capabilities supported by the terminal device. This allows the network data analysis function element to obtain the QoE reporting capabilities supported by the terminal device and configure configuration information that matches the QoE reporting capabilities of the terminal device.

[0020] In one possible design, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity. This allows terminal devices to flexibly report relevant QoE information.

[0021] In one possible design, the second message is a registration request message or a session request message. This allows for the reuse of existing messages, saving signaling overhead.

[0022] Secondly, this application provides a communication method that can be applied to a communication device. The communication device can be a network data analysis function network element, or a processor, chip, chip system, circuit, or functional module within the network data analysis function network element. The method may include: sending first configuration information via a first transmission message, the first configuration information being used to instruct a terminal device to collect or report Quality of Experience (QoE) information; and receiving QoE information.

[0023] Using the above method, the network data analysis function network element and the terminal device can directly transmit the first configuration information through the control plane without going through OAM and AF to trigger the configuration. This can reduce the latency of QoE information configuration, and the network data analysis function network element does not need to rely on DCAF technology or OAM technology to obtain QoE information from the terminal device, making it easier to commercially deploy.

[0024] In one possible design, QoE information can be received via a second transmission message. This allows network data analysis elements to directly obtain QoE information through the control plane, reducing QoE information transmission latency. It eliminates the need to rely on DCAF (Distributed Control Alarm) or OAM (Operational Access Mode) technologies to obtain QoE information from terminal devices, making it easier for commercial deployment.

[0025] In one possible design, receiving QoE information can be achieved by receiving the QoE information from an Access and Mobility Management (AMI) network element or a Session Management (SEM) network element via a second transmission message. This allows the network data analysis (BMI) network element to directly obtain QoE information from the AMI or SEM network element, reducing QoE information transmission latency. This approach, which relies on DCAF (Distributed Control Allocation) and OAM (Operational Access Management) technologies to obtain QoE information from terminal devices, is easier for commercial deployment.

[0026] In one possible design, the QoE information is received via the user plane. Transmitting QoE information directly via the user plane can reduce QoE information transmission latency and improve QoE information transmission efficiency.

[0027] In one possible design, receiving the QoE information via the user plane can be achieved by receiving the QoE information through a Protocol Data Unit (PDU) session used for transmitting QoE information. Directly transmitting QoE information via a PDU session can reduce QoE information transmission latency and improve QoE information transmission efficiency.

[0028] In one possible design, a third message is received, which requests the establishment of a secure connection. This ensures the secure transmission of QoE information.

[0029] In one possible design, the first configuration information is determined based on the QoE reporting capabilities supported by the terminal device. Based on this, the network data analysis function network element can configure configuration information that matches the QoE reporting capabilities of the terminal device, so that the terminal device reports QoE information matching its own capabilities.

[0030] In one possible design, a fourth message is received, which contains information about the QoE reporting capabilities supported by the terminal device. This allows the network data analysis function element to obtain the QoE reporting capabilities supported by the terminal device and configure configuration information that matches the terminal device's QoE reporting capabilities.

[0031] In one possible design, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity. This allows terminal devices to flexibly report relevant QoE information.

[0032] In one possible design, the fourth message is a subscription notification message or a QoE service message. This allows for the reuse of existing messages, saving signaling overhead.

[0033] Thirdly, this application provides a communication method that can be applied to a communication device, which can be an access and mobility management function (AMU) network element, or a processor, chip, chip system, circuit, or functional module within the AMU. The method may include: receiving first configuration information via a first transmission message, the first configuration information being used to instruct a terminal device to collect or report Quality of Experience (QoE) information; and sending the first configuration information via a first NAS signaling.

[0034] The above method enables the network data analysis function network element and the terminal device to directly transmit the first configuration information through the control plane without going through OAM and AF to trigger the configuration. This can reduce the latency of QoE information configuration, and the network data analysis function network element does not need to rely on DCAF technology or OAM technology to obtain QoE information from the terminal device, making it easier to commercially deploy.

[0035] In one possible design, the first NAS signaling includes a first container, and the first container includes the first configuration information. Transmitting the first configuration information through the container reduces transmission latency and improves transmission efficiency.

[0036] In one possible design, the first NAS signaling is either a registration acceptance message or a downlink transmission message. This allows existing messages to be reused to transmit the first configuration information, saving signaling overhead.

[0037] In one possible design, the QoE information is received via a second NAS signaling; the QoE information is then sent via a second transmission message. This allows the terminal device to directly report QoE information through the control plane, reducing QoE information transmission latency. Furthermore, network data analysis elements do not need to rely on DCAF or OAM technologies to obtain QoE information from the terminal device, making it easier for commercial deployment.

[0038] In one possible design, the second NAS signaling is a registration request message or an uplink transmission message. This allows existing messages to be reused to transmit QoE information, saving signaling overhead.

[0039] In one possible design, the second NAS signaling includes a second container, which contains the QoE information. Transmitting QoE information through a container reduces QoE information transmission latency and improves QoE information transmission efficiency.

[0040] In one possible design, the first configuration information is determined based on the QoE reporting capabilities supported by the terminal device. Based on this, the network data analysis function network element can configure configuration information that matches the QoE reporting capabilities of the terminal device, so that the terminal device reports QoE information matching its own capabilities.

[0041] In one possible design, a second message is received, which contains information about the QoE reporting capabilities supported by the terminal device. This allows the network data analysis function element to obtain the QoE reporting capabilities supported by the terminal device and configure configuration information that matches the QoE reporting capabilities of the terminal device.

[0042] In one possible design, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity. This allows terminal devices to flexibly report relevant QoE information.

[0043] In one possible design, the second message is a registration request message. This allows for the reuse of existing messages, saving signaling overhead.

[0044] In one possible design, a fourth message is sent, which includes the QoE reporting capabilities supported by the terminal device. This allows the network data analysis function element to obtain the QoE reporting capabilities supported by the terminal device and configure configuration information that matches the QoE reporting capabilities of the terminal device.

[0045] In one possible design, the fourth message is a subscription notification message or a QoE service message. This allows for the reuse of existing messages, saving signaling overhead.

[0046] Fourthly, this application provides a communication method that can be applied to a communication device. The communication device can be a session management function network element, or it can be a processor, chip, chip system, circuit, or functional module in the session management function network element. The method may include: receiving first configuration information through a first transmission message, the first configuration information being used to instruct a terminal device to collect or report Quality of Experience (QoE) information; and sending the first configuration information through a first NAS signaling.

[0047] The above method enables the network data analysis function network element and the terminal device to directly transmit the first configuration information through the control plane without going through OAM and AF to trigger the configuration. This can reduce the latency of QoE information configuration, and the network data analysis function network element does not need to rely on DCAF technology or OAM technology to obtain QoE information from the terminal device, making it easier to commercially deploy.

[0048] In one possible design, the first NAS signaling is a session accept message. This allows existing messages to be reused to transmit the first configuration information, saving signaling overhead.

[0049] In one possible design, the QoE information is received via a second NAS signaling; the QoE information is then sent via a second transmission message. This allows the terminal device to directly report QoE information through the control plane, reducing QoE information transmission latency. Furthermore, network data analysis elements do not need to rely on DCAF or OAM technologies to obtain QoE information from the terminal device, making it easier for commercial deployment.

[0050] In one possible design, the second NAS signaling is a session request message. This allows existing message transmissions of QoE information to be reused, saving signaling overhead.

[0051] In one possible design, a first PDU session establishment request is received. This request is used to establish a PDU session for transmitting QoS information. This allows the terminal device to directly transmit QoE information through the PDU session, reducing QoE information transmission latency and improving QoE information transmission efficiency.

[0052] In one possible design, the first configuration information is determined based on the QoE reporting capabilities supported by the terminal device. Based on this, the network data analysis function network element can configure configuration information that matches the QoE reporting capabilities of the terminal device, so that the terminal device reports QoE information matching its own capabilities.

[0053] In one possible design, a second message is received, which contains information about the QoE reporting capabilities supported by the terminal device. This allows the network data analysis function element to obtain the QoE reporting capabilities supported by the terminal device and configure configuration information that matches the QoE reporting capabilities of the terminal device.

[0054] In one possible design, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity. This allows terminal devices to flexibly report relevant QoE information.

[0055] In one possible design, the second message is a session request message. This allows for the reuse of existing messages, saving signaling overhead.

[0056] In one possible design, a fourth message is sent, which includes the QoE reporting capabilities supported by the terminal device. This allows the network data analysis function element to obtain the QoE reporting capabilities supported by the terminal device and configure configuration information that matches the QoE reporting capabilities of the terminal device.

[0057] In one possible design, the fourth message is a subscription notification message or a QoE service message. This allows for the reuse of existing messages, saving signaling overhead.

[0058] Fifthly, this application provides a communication method that can be applied to a communication device, which can be a terminal device, or a processor, chip, chip system, circuit, or functional module within the terminal device. The method may include: receiving first configuration information, the first configuration information being used to instruct the terminal device to collect or report QoE information; and sending the QoE information via a second NAS signaling.

[0059] Using the above method, terminal devices can directly transmit QoE information through the control plane. Network data analysis function network elements do not need to obtain it through OAM and AF, which can reduce the transmission latency of QoE information. Furthermore, network data analysis function network elements do not need to rely on DCAF technology or OAM technology to obtain QoE information from terminal devices, making it easier to commercially deploy.

[0060] In one possible design, the second NAS signaling includes a second container, which contains the QoE information. Transmitting QoE information through a container reduces QoE information transmission latency and improves QoE information transmission efficiency.

[0061] In one possible design, the second NAS signaling is a registration request message or an uplink transmission message. This allows existing messages to be reused to transmit QoE information, saving signaling overhead.

[0062] In one possible design, the first configuration information is received via first NAS signaling. The network data analysis function network element and the terminal device can directly transmit the first configuration information through the control plane, without needing to go through OAM and AF to trigger configuration, which can reduce QoE information configuration latency.

[0063] In one possible design, the first NAS signaling includes a first container, and the first container includes the first configuration information. Transmitting the first configuration information through the container reduces transmission latency and improves transmission efficiency.

[0064] In one possible design, the first configuration information is received via the user plane. Transmitting the first configuration information directly via the user plane can reduce transmission latency and improve transmission efficiency.

[0065] In one possible design, a Protocol Data Unit (PDU) session is established for transmitting first configuration information; the first configuration information is received through the PDU session. Transmitting the first configuration information directly through the PDU session can reduce transmission latency and improve transmission efficiency.

[0066] In one possible design, a fifth message is received, which includes second indication information. This second indication information instructs the establishment of a PDU session for transmitting first configuration information. This allows the terminal device to establish a PDU session for transmitting the first configuration information, enabling direct transmission of the first configuration information through the PDU session. This reduces transmission latency and improves transmission efficiency.

[0067] In one possible design, the first configuration information is determined based on the QoE reporting capabilities supported by the terminal device. Based on this, the network data analysis function network element can configure configuration information that matches the QoE reporting capabilities of the terminal device, so that the terminal device reports QoE information matching its own capabilities.

[0068] In one possible design, a second message is sent, which contains information about the QoE reporting capabilities supported by the terminal device. This allows the network data analysis function element to obtain the QoE reporting capabilities supported by the terminal device and configure configuration information that matches the QoE reporting capabilities of the terminal device.

[0069] In one possible design, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity. This allows terminal devices to flexibly report relevant QoE information.

[0070] Sixthly, this application provides a communication method that can be applied to a communication device. The communication device can be a network data analysis function network element, or a processor, chip, chip system, circuit, or functional module within the network data analysis function network element. The method may include: sending first configuration information, which instructs a terminal device to collect or report QoE information; and receiving QoE information via a second transmission message.

[0071] Using the above method, terminal devices can directly transmit QoE information through the control plane. Network data analysis function network elements do not need to obtain it through OAM and AF, which can reduce the transmission latency of QoE information. Furthermore, network data analysis function network elements do not need to rely on DCAF technology or OAM technology to obtain QoE information from terminal devices, making it easier to commercially deploy.

[0072] In one possible design, receiving QoE information via a second transmission message can be achieved by receiving the QoE information from an access and mobility management function (AMAC) network element or a session management function (SMU) network element via the second transmission message. This allows the network data analysis function network element to directly obtain QoE information from the AMAC or SMU network element, reducing QoE information transmission latency. This approach, which relies on DCAF and OAM technologies to obtain QoE information from terminal devices, is easier for commercial deployment.

[0073] In one possible design, the first configuration information can be sent via a first transmission message. The network data analysis function network element and the terminal device can directly transmit the first configuration information through the control plane, without needing to go through OAM and AF to trigger configuration, which can reduce QoE information configuration latency.

[0074] In one possible design, the first configuration information is sent via the user plane. Transmitting the first configuration information directly via the user plane can reduce transmission latency and improve transmission efficiency.

[0075] In one possible design, sending the first configuration information via the user plane includes: sending the first configuration information through a PDU session used for transmitting the first configuration information. Directly transmitting the first configuration information through the PDU session can reduce transmission latency and improve transmission efficiency.

[0076] In one possible design, the first configuration information is determined based on the QoE reporting capabilities supported by the terminal device. Based on this, the network data analysis function network element can configure configuration information that matches the QoE reporting capabilities of the terminal device, so that the terminal device reports QoE information matching its own capabilities.

[0077] In one possible design, a fourth message is received, which contains information about the QoE reporting capabilities supported by the terminal device. This allows the network data analysis function element to obtain the QoE reporting capabilities supported by the terminal device and configure configuration information that matches the QoE reporting capabilities of the terminal device.

[0078] In one possible design, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity. This allows terminal devices to flexibly report relevant QoE information.

[0079] Seventhly, this application provides a communication method that can be applied to a communication device. The communication device can be an Access and Mobility Management Function (AMS) network element, or a Session Management Function (SMS) network element, or a processor, chip, chip system, circuit, or functional module within an AMS network element. The method may include: receiving QoE information via a second NAS signaling, wherein the QoE information is collected or reported according to first configuration information; and sending the QoE information via a second transmission message.

[0080] Using the above method, terminal devices can directly transmit QoE information through the control plane. Network data analysis function network elements do not need to obtain it through OAM and AF, which can reduce the transmission latency of QoE information. Furthermore, network data analysis function network elements do not need to rely on DCAF technology or OAM technology to obtain QoE information from terminal devices, making it easier to commercially deploy.

[0081] In one possible design, the second NAS signaling includes a second container, which contains the QoE information. Transmitting QoE information through a container reduces QoE information transmission latency and improves QoE information transmission efficiency.

[0082] In one possible design, the first configuration information is received via a first transmission message; the first configuration information is then sent via a first NAS signaling. The network data analysis function network element and the terminal device can directly transmit the first configuration information through the control plane, without needing to go through OAM and AF-triggered configuration, which can reduce QoE information configuration latency.

[0083] In one possible design, the first NAS signaling shown includes a first container, which contains the first configuration information. Transmitting the first configuration information through the container reduces transmission latency and improves transmission efficiency.

[0084] In one possible design, the first configuration information is determined based on the QoE reporting capabilities supported by the terminal device. Based on this, the network data analysis function network element can configure configuration information that matches the QoE reporting capabilities of the terminal device, so that the terminal device reports QoE information matching its own capabilities.

[0085] In one possible design, a second message is received, which contains information about the QoE reporting capabilities supported by the terminal device. This allows the network data analysis function element to obtain the QoE reporting capabilities supported by the terminal device and configure configuration information that matches the QoE reporting capabilities of the terminal device.

[0086] In one possible design, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity. This allows terminal devices to flexibly report relevant QoE information.

[0087] In one possible design, the second message is a registration request message. This allows for the reuse of existing messages, saving signaling overhead.

[0088] In one possible design, a fourth message is sent, which includes the QoE reporting capabilities supported by the terminal device. This allows the network data analysis function element to obtain the QoE reporting capabilities supported by the terminal device and configure configuration information that matches the QoE reporting capabilities of the terminal device.

[0089] In one possible design, the fourth message is a subscription notification message or a QoE service message. This allows for the reuse of existing messages, saving signaling overhead.

[0090] Eighthly, this application provides a communication method that can be applied to a communication device, which can be a session management function network element, or a processor, chip, chip system, circuit, or functional module within the session management function network element. The method may include: receiving QoE information via a second NAS signaling, wherein the QoE information is collected or reported according to first configuration information; and sending the QoE information via a second transmission message.

[0091] Using the above method, terminal devices can directly transmit QoE information through the control plane. Network data analysis function network elements do not need to obtain it through OAM and AF, which can reduce the transmission latency of QoE information. Furthermore, network data analysis function network elements do not need to rely on DCAF technology or OAM technology to obtain QoE information from terminal devices, making it easier to commercially deploy.

[0092] In one possible design, the first configuration information is received via a first transmission message; the first configuration information is then sent via a first NAS signaling. The network data analysis function network element and the terminal device can directly transmit the first configuration information through the control plane, without needing to go through OAM and AF-triggered configuration, which can reduce QoE information configuration latency.

[0093] In one possible design, a second PDU session establishment request is received. This second PDU session request is used to request the establishment of a PDU session for transmitting the first configuration information. This allows network data analysis function elements to directly transmit the first configuration information through the PDU session, reducing the transmission latency of the first configuration information and improving its transmission efficiency.

[0094] In one possible design, the first configuration information is determined based on the QoE reporting capabilities supported by the terminal device. Based on this, the network data analysis function network element can configure configuration information that matches the QoE reporting capabilities of the terminal device, so that the terminal device reports QoE information matching its own capabilities.

[0095] In one possible design, a second message is received, which contains information about the QoE reporting capabilities supported by the terminal device. This allows the network data analysis function element to obtain the QoE reporting capabilities supported by the terminal device and configure configuration information that matches the QoE reporting capabilities of the terminal device.

[0096] In one possible design, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity. This allows terminal devices to flexibly report relevant QoE information.

[0097] In one possible design, the second message is a session request message. This allows for the reuse of existing messages, saving signaling overhead.

[0098] In one possible design, a fourth message is sent, which includes the QoE reporting capabilities supported by the terminal device. This allows the network data analysis function element to obtain the QoE reporting capabilities supported by the terminal device and configure configuration information that matches the QoE reporting capabilities of the terminal device.

[0099] In one possible design, the fourth message is a subscription notification message or a QoE service message. This allows for the reuse of existing messages, saving signaling overhead.

[0100] Ninthly, this application provides a communication method that can be applied to a communication device, which can be a terminal device, or a processor, chip, chip system, circuit, or functional module in the terminal device. The method may include: receiving first configuration information, the first configuration information being used to indicate the collection or reporting of QoE information; establishing a Protocol Data Unit (PDU) session for transmitting QoE information; and sending the QoE information through the PDU session.

[0101] Using the above method, terminal devices can directly transmit QoE information through the user plane. Network data analysis function network elements do not need to obtain it through OAM and AF, which can reduce the transmission latency of QoE information. Furthermore, network data analysis function network elements do not need to rely on DCAF technology or OAM technology to obtain QoE information from terminal devices, making it easier to commercially deploy.

[0102] In one possible design, a first message is received, the first message including first indication information, which is used to instruct the establishment of a Protocol Data Unit (PDU) session for transmitting QoE information. This allows the terminal device to establish a PDU session for transmitting QoE information, enabling direct transmission of QoE information through the PDU session, thereby reducing QoE information transmission latency and improving QoE information transmission efficiency.

[0103] In one possible design, the first message includes a routing policy rule, which in turn includes the first indication information. This allows the first indication information to be carried within an existing routing policy rule, saving signaling overhead.

[0104] In one possible design, the routing policy rule includes a traffic descriptor, which includes the first indication information. This allows the first indication information to be carried within existing routing policy rules, saving signaling overhead.

[0105] In one possible design, the routing policy rule also includes a routing descriptor, which includes attributes for establishing the PDU session. This clarifies the attributes of the PDU session to be established.

[0106] In one possible design, the first configuration information can be received via first NAS signaling. The network data analysis function network element and the terminal device can directly transmit the first configuration information through the control plane, without needing to go through OAM and AF to trigger configuration, which can reduce QoE information configuration latency.

[0107] In one possible design, the first NAS signaling includes a first container, and the first container includes the first configuration information. Transmitting the first configuration information through the container reduces transmission latency and improves transmission efficiency.

[0108] In one possible design, the first NAS signaling is a registration accept message, a downlink transmission message, or a session accept message. This allows existing message transmissions of QoE information to be reused, saving signaling overhead.

[0109] In one possible design, the first configuration information can be received via the user plane. Directly transmitting the first configuration information via the user plane can reduce transmission latency and improve transmission efficiency.

[0110] In one possible design, a Protocol Data Unit (PDU) session is established for transmitting first configuration information; the first configuration information is received through the PDU session. Transmitting the first configuration information directly through the PDU session can reduce transmission latency and improve transmission efficiency.

[0111] In one possible design, a fifth message is received, which includes second indication information. This second indication information instructs the establishment of a PDU session for transmitting first configuration information. This allows the terminal device to establish a PDU session for transmitting the first configuration information, enabling direct transmission of the first configuration information through the PDU session. This reduces transmission latency and improves transmission efficiency.

[0112] In one possible design, the first configuration information is determined based on the QoE reporting capabilities supported by the terminal device. Based on this, the network data analysis function network element can configure configuration information that matches the QoE reporting capabilities of the terminal device, so that the terminal device reports QoE information matching its own capabilities.

[0113] In one possible design, a second message is sent, which contains information about the QoE reporting capabilities supported by the terminal device. This allows the network data analysis function element to obtain the QoE reporting capabilities supported by the terminal device and configure configuration information that matches the QoE reporting capabilities of the terminal device.

[0114] In one possible design, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity. This allows terminal devices to flexibly report relevant QoE information.

[0115] In one possible design, the first configuration information is received via subscription.

[0116] Tenthly, this application provides a communication method that can be applied to a communication device. The communication device can be a network data analysis function network element, or a processor, chip, chip system, circuit, or functional module within the network data analysis function network element. The method may include: sending first configuration information, the first configuration information being used to instruct the collection or reporting of QoE information; and receiving QoE information through a Protocol Data Unit (PDU) session used for transmitting QoE information.

[0117] Using the above method, terminal devices can directly transmit QoE information through the user plane. Network data analysis function network elements do not need to obtain it through OAM and AF, which can reduce the transmission latency of QoE information. Furthermore, network data analysis function network elements do not need to rely on DCAF technology or OAM technology to obtain QoE information from terminal devices, making it easier to commercially deploy.

[0118] In one possible design, the first configuration information can be sent via a first transmission message. The network data analysis function network element and the terminal device can directly transmit the first configuration information through the control plane, without needing to go through OAM and AF-triggered configuration, which can reduce QoE information configuration latency.

[0119] In one possible design, sending the first configuration information includes: sending the first configuration information through the user plane. Directly transmitting the first configuration information through the user plane can reduce transmission latency and improve transmission efficiency.

[0120] In one possible design, sending the first configuration information via the user plane includes: sending the first configuration information through a PDU session used for transmitting the first configuration information. Directly transmitting the first configuration information through the PDU session can reduce transmission latency and improve transmission efficiency.

[0121] In one possible design, the first configuration information is determined based on the QoE reporting capabilities supported by the terminal device. Based on this, the network data analysis function network element can configure configuration information that matches the QoE reporting capabilities of the terminal device, so that the terminal device reports QoE information matching its own capabilities.

[0122] In one possible design, a fourth message is received, which contains information about the QoE reporting capabilities supported by the terminal device. This allows the network data analysis function element to obtain the QoE reporting capabilities supported by the terminal device and configure configuration information that matches the QoE reporting capabilities of the terminal device.

[0123] In one possible design, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity. This allows terminal devices to flexibly report relevant QoE information.

[0124] Eleventhly, this application provides a communication method that can be applied to a communication device. The communication device can be a policy control function network element, or a processor, chip, chip system, circuit, or functional module in a network data analysis function network element. The method may include: sending a first message, the first message including first indication information, the first indication information being used to indicate the establishment of a Protocol Data Unit (PDU) session for transmitting QoE information.

[0125] Based on this method, terminal devices can establish PDU sessions for transmitting QoE information, thereby directly transmitting QoE information through the PDU session, reducing QoE information transmission latency and improving QoE information transmission efficiency.

[0126] In one possible design, the first message includes a routing policy rule, which in turn includes the first indication information. This allows the first indication information to be carried within an existing routing policy rule, saving signaling overhead.

[0127] In one possible design, the routing policy rule includes a traffic descriptor, which includes the first indication information. This allows the first indication information to be carried within existing routing policy rules, saving signaling overhead.

[0128] In one possible design, a fifth message is sent, which includes second indication information. This second indication information instructs the establishment of a Protocol Data Unit (PDU) session for transmitting first configuration information. This allows the terminal device to establish a PDU session for transmitting the first configuration information, enabling direct transmission of the first configuration information through the PDU session. This reduces transmission latency and improves transmission efficiency.

[0129] In a twelfth aspect, this application provides a communication method that can be applied to a communication device. The communication device can be a policy control function network element, or a processor, chip, chip system, circuit, or functional module in a network data analysis function network element. The method may include: sending a fifth message, the fifth message including second indication information, the second indication information being used to indicate the establishment of a Protocol Data Unit (PDU) session for transmitting first configuration information.

[0130] Based on this method, the terminal device can establish a PDU session for transmitting the first configuration information, so that the first configuration information can be directly transmitted through the PDU session, which can reduce the transmission latency of the first configuration information and improve the transmission efficiency of the first configuration information.

[0131] In one possible design, the fifth message includes a routing policy rule, which in turn includes the second indication information. This allows the second indication information to be carried over from existing routing policy rules, saving signaling overhead.

[0132] In one possible design, the routing policy rule includes a traffic descriptor, which includes the second indication information. This allows the second indication information to be carried within existing routing policy rules, saving signaling overhead.

[0133] In one possible design, a first message is sent, which includes first indication information. This first indication information instructs the establishment of a Protocol Data Unit (PDU) session for transmitting QoE information. This allows the terminal device to establish a PDU session for transmitting QoE information, enabling direct transmission of QoE information through the PDU session, thereby reducing QoE information transmission latency and improving QoE information transmission efficiency.

[0134] In a thirteenth aspect, this application provides a communication method that can be applied to a communication device, which may be a terminal device, or a processor, chip, chip system, circuit, or functional module within the terminal device. The method may include: receiving first configuration information, the first configuration information being determined based on the Quality of Experience (QoE) reporting capability supported by the terminal device; and sending QoE information according to the first configuration information.

[0135] Based on this, network data analysis function network elements can be configured with configuration information that matches the QoE reporting capability of terminal devices, so that terminal devices can report QoE information that matches their own capabilities.

[0136] In a fourteenth aspect, this application provides a communication method that can be applied to a communication device. The communication device can be a network data analysis function network element, or a processor, chip, chip system, circuit, or functional module within the network data analysis function network element. The method may include: sending first configuration information, the first configuration information being determined based on the Quality of Experience (QoE) reporting capability supported by the terminal device; and receiving QoE information.

[0137] In a fifteenth aspect, this application provides a communication method that can be applied to a communication device. The communication device can be a session management function network element or an access and mobility management function network element, or it can be a processor, chip, chip system, circuit, or functional module within a session management function network element or an access and mobility management function network element. The method may include: receiving a second message, the second message containing QoE reporting capabilities supported by the terminal device; and sending a fourth message, the fourth message including the QoE reporting capabilities supported by the terminal device.

[0138] Based on this, network data analysis function elements can obtain the QoE reporting capabilities supported by terminal devices, and can configure configuration information that matches the QoE reporting capabilities of terminal devices, so that terminal devices can report QoE information that matches their own capabilities.

[0139] In a sixteenth aspect, this application also provides a communication device, which may be a terminal device or a component within a terminal device (e.g., a processor, chip, chip system, circuit, component, module, or functional module, etc.). This communication device has the functionality to implement the methods described in the first aspect or various possible design examples of the first aspect, or the fifth aspect or various possible design examples of the fifth aspect, or the ninth aspect or various possible design examples of the ninth aspect, or the thirteenth aspect or various possible design examples of the thirteenth aspect. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the described functionality.

[0140] In one possible design, the communication device may include a processing unit, and optionally a transceiver unit. These units may perform the functions of the methods described in the first aspect or various possible design examples of the first aspect, or in the fifth aspect or various possible design examples of the fifth aspect, or in the ninth aspect or various possible design examples of the ninth aspect, or in the thirteenth aspect or various possible design examples of the thirteenth aspect, which will not be elaborated here.

[0141] In one possible design, the communication device includes one or more processors, and optionally also includes a memory and / or a transceiver. The transceiver is used to send and receive data, messages, or information, and to communicate and interact with other devices in the system. The processor is configured to support the communication device in performing the corresponding functions described in the first aspect or various possible design examples of the first aspect, or the fifth aspect or various possible design examples of the fifth aspect, or the ninth aspect or various possible design examples of the ninth aspect, or the thirteenth aspect or various possible design examples of the thirteenth aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device.

[0142] In a seventeenth aspect, this application also provides a communication device, which can be a network data analysis function network element, or a component (e.g., a processor, chip, chip system, circuit, component, module, or functional module, etc.) within a network data analysis function network element. This communication device has the functionality to implement the methods described in the second aspect or various possible design examples of the second aspect, or the sixth aspect or various possible design examples of the sixth aspect, or the tenth aspect or various possible design examples of the tenth aspect, or the fourteenth aspect or various possible design examples of the fourteenth aspect. The functionality can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functionality.

[0143] In one possible design, the communication device may include a processing unit, and optionally a transceiver unit. These units may perform the functions of the methods described in the second aspect or various possible design examples of the second aspect, or the sixth aspect or various possible design examples of the sixth aspect, or the tenth aspect or various possible design examples of the tenth aspect, or the fourteenth aspect or various possible design examples of the fourteenth aspect, which will not be elaborated here.

[0144] In one possible design, the communication device includes one or more processors, and optionally also includes a memory and / or a transceiver. The transceiver is used to send and receive data, messages, or information, and to communicate and interact with other devices in the system. The processor is configured to support the communication device in performing corresponding functions in the second aspect or various possible design examples of the second aspect, or the sixth aspect or various possible design examples of the sixth aspect, or the tenth aspect or various possible design examples of the tenth aspect, or the fourteenth aspect or various possible design examples of the fourteenth aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device.

[0145] In an eighteenth aspect, this application also provides a communication device, which may be an access and mobility management function (AMU) network element, or a component within an AMU network element (e.g., a processor, chip, chip system, circuit, component, module, or functional module, etc.). This communication device has the functionality to implement the methods described in the third aspect or various possible design examples of the third aspect, or in the seventh aspect or various possible design examples of the seventh aspect, or in the fifteenth aspect or various possible design examples of the fifteenth aspect. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the described functionality.

[0146] In one possible design, the communication device may include a processing unit, and optionally a transceiver unit. These units may perform the functions of the methods described in the third aspect or various possible design examples of the third aspect, or in the seventh aspect or various possible design examples of the seventh aspect, or in the fifteenth aspect or various possible design examples of the fifteenth aspect, which will not be elaborated here.

[0147] In one possible design, the communication device includes one or more processors, and optionally also includes a memory and / or a transceiver. The transceiver is used to send and receive data, messages, or information, and to communicate and interact with other devices in the system. The processor is configured to support the communication device in performing the corresponding functions in the third aspect or various possible design examples of the third aspect, or the seventh aspect or various possible design examples of the seventh aspect, or the fifteenth aspect or various possible design examples of the fifteenth aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device.

[0148] In a nineteenth aspect, this application also provides a communication device, which may be a session management function network element, or a component within a session management function network element (e.g., a processor, chip, chip system, circuit, component, module, or functional module, etc.). This communication device has the functionality to implement the methods described in the fourth aspect or various possible design examples of the fourth aspect, or the eighth aspect or various possible design examples of the eighth aspect, or the fifteenth aspect or various possible design examples of the fifteenth aspect. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the described functionality.

[0149] In one possible design, the communication device may include a processing unit, and optionally a transceiver unit. These units may perform the functions of the methods described in the fourth aspect or various possible design examples of the fourth aspect, or the eighth aspect or various possible design examples of the eighth aspect, or the fifteenth aspect or various possible design examples of the fifteenth aspect, which will not be elaborated here.

[0150] In one possible design, the communication device includes one or more processors, and optionally also includes a memory and / or a transceiver. The transceiver is used to send and receive data, messages, or information, and to communicate and interact with other devices in the system. The processor is configured to support the communication device in performing the corresponding functions in the fourth aspect or various possible design examples of the fourth aspect, or the eighth aspect or various possible design examples of the eighth aspect, or the fifteenth aspect or various possible design examples of the fifteenth aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device.

[0151] In a twentieth aspect, this application also provides a communication device, which may be a policy control function network element, or a component of a policy control function network element (e.g., a processor, chip, chip system, circuit, component, module, or functional module, etc.). This communication device has the functionality to implement the methods described in the eleventh aspect or various possible design examples of the eleventh aspect, or the twelfth aspect or various possible design examples of the twelfth aspect. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functionality.

[0152] In one possible design, the communication device may include a processing unit, and optionally a transceiver unit. These units may perform the functions of the methods described in the eleventh aspect or various possible design examples of the eleventh aspect, or the twelfth aspect or various possible design examples of the twelfth aspect, which will not be elaborated here.

[0153] In one possible design, the communication device includes one or more processors, and optionally also includes a memory and / or a transceiver. The transceiver is used to send and receive data, messages, or information, and to communicate with other devices in the system. The processor is configured to support the communication device in performing the corresponding functions in the eleventh aspect or various possible design examples of the eleventh aspect, or in the twelfth aspect or various possible design examples of the twelfth aspect. The memory is coupled to the processor and stores the necessary program instructions and data for the communication device.

[0154] In a twentieth aspect, embodiments of this application provide a communication system that may include a terminal device and a network data analysis function network element. The terminal device may be used to implement the methods described in the first aspect or various possible design examples of the first aspect; the network data analysis function network element may be used to implement the methods described in the second aspect or various possible design examples of the second aspect. Alternatively, the terminal device may be used to implement the methods described in the fifth aspect or various possible design examples of the fifth aspect; the network data analysis function network element may be used to implement the methods described in the sixth aspect or various possible design examples of the sixth aspect. Alternatively, the terminal device may be used to implement the methods described in the ninth aspect or various possible design examples of the ninth aspect; the network data analysis function network element may be used to implement the methods described in the tenth aspect or various possible design examples of the tenth aspect. Alternatively, the terminal device may be used to implement the methods described in the thirteenth aspect or various possible design examples of the thirteenth aspect; the network data analysis function network element may be used to implement the methods described in the fourteenth aspect or various possible design examples of the fourteenth aspect.

[0155] In one possible design, the communication system may further include an access and mobility management function network element, which is used to implement the methods in the third aspect or various possible design examples of the third aspect, or to implement the methods in the seventh aspect or various possible design examples of the seventh aspect, or to implement the methods in the fifteenth aspect or various possible design examples of the fifteenth aspect.

[0156] In one possible design, the communication system may further include a session management function network element, which is used to implement the methods in the fourth aspect or various possible design examples of the fourth aspect, or to implement the methods in the eighth aspect or various possible design examples of the eighth aspect, or to implement the methods in the fifteenth aspect or various possible design examples of the fifteenth aspect.

[0157] In one possible design, the communication system may also include a policy control function network element, which is used to implement the methods in the eleventh aspect or various possible design examples of the eleventh aspect, or to implement the methods in the twelfth aspect or various possible design examples of the twelfth aspect.

[0158] In a twentieth aspect, embodiments of this application provide a computer-readable storage medium storing program instructions that, when executed on a computer, cause the computer to perform the methods described in the first aspect and any possible design of the embodiments of this application, or in the second aspect and any possible design of the second aspect, or in the third aspect and any possible design of the third aspect, or in the fourth aspect and any possible design of the fourth aspect, or in the fifth aspect and any possible design of the fifth aspect, or in the sixth aspect and any possible design of the seventh aspect and any possible design of the seventh aspect, or in the eighth aspect and any possible design of the ninth aspect and any possible design of the ninth aspect, or in the tenth aspect and any possible design of the tenth aspect, or in the eleventh aspect and any possible design of the eleventh aspect and any possible design of the twelfth aspect and any possible design of the thirteenth aspect and any possible design of the fourteenth aspect and any possible design of the fifteenth aspect and any possible design. Exemplarily, the computer-readable storage medium can be any available medium accessible to a computer. For example, but not limited to: computer-readable media may include non-transient computer-readable media, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disc storage, magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer.

[0159] In a twentieth aspect, embodiments of this application provide a computer program product, including a computer program or instructions, which, when executed on a computer, cause the method described in the first aspect or any possible design of the first aspect, or in the second aspect or any possible design of the second aspect, or in the third aspect and any possible design of the third aspect, or in the fourth aspect and any possible design of the fourth aspect, or in the fifth aspect and any possible design of the fifth aspect, or in the sixth aspect and any possible design of the seventh aspect, or in the eighth aspect and any possible design of the eighth aspect, or in the ninth aspect and any possible design of the ninth aspect, or in the tenth aspect and any possible design of the tenth aspect, or in the eleventh aspect and any possible design of the eleventh aspect, or in the twelfth aspect and any possible design of the thirteenth aspect, or in the fourteenth aspect and any possible design of the fourteenth aspect, or in the fifteenth aspect and any possible design of the fifteenth aspect to be executed.

[0160] In a twentieth aspect, this application also provides a chip or chip system, including one or more processors, said processors being coupled to at least one memory for reading and executing program instructions stored in said memory to enable the chip or chip system to implement the methods described in the first aspect or any possible design of the first aspect, or in the second aspect or any possible design of the second aspect, or in the third aspect and any possible design of the third aspect, or in the fourth aspect and any possible design of the fourth aspect, or in the fifth aspect and any possible design of the fifth aspect, or in the sixth aspect and any possible design of the seventh aspect, or in the eighth aspect and any possible design of the eighth aspect, or in the ninth aspect and any possible design of the ninth aspect, or in the tenth aspect and any possible design of the tenth aspect, or in the eleventh aspect and any possible design of the eleventh aspect, or in the twelfth aspect and any possible design of the thirteenth aspect, or in the fourteenth aspect and any possible design of the fifteenth aspect.

[0161] For each of the above-mentioned aspects sixteen to twenty-four and the technical effects that each aspect may achieve, please refer to the above description of the technical effects that can be achieved for the first aspect or the various possible solutions in the first aspect, or the second aspect or the various possible solutions in the second aspect, or the third aspect or the various possible solutions in the third aspect, or the fourth aspect or the various possible solutions in the fourth aspect, or the fifth aspect or the various possible solutions in the fifth aspect, or the sixth aspect or the various possible solutions in the sixth aspect, or the seventh aspect or the various possible solutions in the seventh aspect, or the eighth aspect or the various possible solutions in the eighth aspect, or the ninth aspect or the various possible solutions in the ninth aspect, or the tenth aspect or the tenth aspect, or the eleventh aspect or the eleventh aspect, or the twelfth aspect or the twelfth aspect, or the thirteenth aspect or the thirteenth aspect, or the fourteenth aspect or the fourteenth aspect, or the fifteenth aspect or the fifteenth aspect. It will not be repeated here. Attached Figure Description

[0162] Figure 1 A schematic diagram of the architecture of a communication system provided in this application;

[0163] Figure 2 This application provides a schematic diagram of the structure of a communication chip for a terminal device.

[0164] Figure 3 A schematic diagram of the network architecture of another communication system provided in this application;

[0165] Figure 4 A flowchart illustrating a communication method provided in this application;

[0166] Figure 5 A flowchart illustrating an example of a communication method provided in this application;

[0167] Figure 6 A flowchart illustrating an example of another communication method provided in this application;

[0168] Figure 7 A flowchart illustrating an example of another communication method provided in this application;

[0169] Figure 8 A flowchart illustrating an example of another communication method provided in this application;

[0170] Figure 9 A flowchart illustrating an example of another communication method provided in this application;

[0171] Figure 10 A flowchart illustrating an example of another communication method provided in this application;

[0172] Figure 11 A flowchart illustrating an example of another communication method provided in this application;

[0173] Figure 12 A flowchart illustrating an example of another communication method provided in this application;

[0174] Figure 13 A schematic diagram of the structure of a communication device provided in this application;

[0175] Figure 14 A structural diagram of a communication device provided in this application. Detailed Implementation

[0176] This application provides a communication method and apparatus to ensure the reporting of QoE information. The method and apparatus described in this application are based on the same technical concept. Since the principles by which the method and apparatus solve the problem are similar, their implementations can be mutually referred to, and repeated details will not be elaborated further.

[0177] In the description of this application, the terms "first," "second," etc., are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance or order.

[0178] In the description of this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0179] In the description of this application, "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 simultaneously, or B exists alone, where A and B can be singular or plural. " / " means "or", for example, a / b means a or b.

[0180] To more clearly describe the technical solutions of the embodiments of this application, the communication methods and devices provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0181] The technical solutions in this application embodiment can be applied to various communication systems, such as Universal Mobile Telecommunications System (UMTS), Wireless Local Area Network (WLAN), Wireless Fidelity (Wi-Fi) system, 4th generation (4G) mobile communication system (such as Long Term Evolution (LTE) system), 5th generation (5G) mobile communication system (such as New Radio (NR) system), and future communication networks, etc.

[0182] The 3rd Generation Partnership Project (3GPP) standards group defined the 5G network architecture. This architecture supports radio access technologies defined by the 3GPP standards group (such as Long Term Evolution (LTE) and the Sixth Generation (5G) radio access network ((R)AN)) to access the 5G core network (CN). (R)AN and RAN are interchangeable; for ease of description, RAN will be used as an example below.

[0183] For example, Figure 1A schematic diagram of the architecture of a possible communication system applicable to embodiments of this application is shown. Figure 1 The architecture shown is a 5G network architecture based on a service-oriented architecture. Figure 1 The document illustrates the interaction relationships between network functions and entities, as well as their corresponding interfaces. For example, terminal devices (such as user equipment (UE)) and the AMF can interact through the N1 interface, and the interaction messages are called N1 messages. Figure 1 Some interfaces in the system are implemented using service-oriented interfaces. The architecture of this communication system may include terminal equipment, a radio access network, a data network (DN), and a core network. For example, in the architecture of this communication system, the radio access network may include (radio)access network ((R)AN) devices; for ease of explanation, (R)AN will be referred to as RAN in the following description. The core network may include: Network Slice Selection Function (NSSF) network elements, Network Exposure Function (NEF) network elements, Network Function Repository Function (NRF) network elements, Policy Control Function (PCF) network elements, Unified Data Management (UDM) network elements, Application Function (AF) network elements, Authentication Server Function (AUSF) network elements, Access and Mobility Management Function (AMF) network elements, Session Management Function (SMF) network elements, User Plane Function (UPF) network elements, Network Data Analytics Function (NWDAF) network elements, Network Slice Admission Control Function (NSACF) network elements, and Network Slice-Specific Authentication and Suspension Function (NSSAAF) network elements, etc. Among them:

[0184] Terminal equipment refers to any device capable of data communication with RAN equipment. It can also be called a terminal, terminal device, user equipment (UE), mobile station (MS), or mobile terminal (MT). Terminal equipment can be widely used in various scenarios, including: mobile phones, computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, stations (STA), robotic arms, cameras, robots, vehicles, drones, helicopters, airplanes, ships, or smart home devices (such as televisions, air conditioners, robot vacuums, speakers, set-top boxes), relays, and customer premises equipment (CPE).

[0185] Furthermore, in this embodiment, the terminal device can also be a terminal device in an Internet of Things (IoT) system.

[0186] Examples include water meters and electricity meters. The Internet of Things (IoT) is an important component of future information technology development. Its main technical characteristic is connecting objects to networks through communication technologies, thereby realizing an intelligent network that enables human-machine interconnection and the interconnection of things.

[0187] When the terminal device is applied to V2X, it can also be called a V2X device, such as a smart car, an unmanned car, a driverless car, a pilotless car, or an automobile, or a roadside unit (RSU). All the terminal devices described above, if located on a vehicle (e.g., placed / installed inside the vehicle), can be considered in-vehicle terminal devices. In-vehicle terminal devices can be built into a vehicle's on-board module, on-board unit, on-board component, on-board chip, or on-board unit as one or more components or units. The vehicle can implement the methods of this application through the built-in on-board module, on-board unit, on-board component, on-board chip, or on-board unit. In-vehicle terminal devices can be vehicle equipment, on-board modules, vehicles, on-board units (OBU), RSUs, in-vehicle infotainment systems (or on-board transmitting units) (telematics boxes, T-boxes), chips, or SoCs, etc., and the aforementioned chips or SoCs can be installed in the vehicle, OBU, RSU, or T-box.

[0188] Terminal devices can establish connections with the operator's network through interfaces provided by the operator's network (such as N1) and use the data, voice, and video services provided by the operator's network. Terminal devices can also access the DN (Network Provider) through the operator's network and use operator services deployed on the DN, and / or services provided by third parties. These third parties can be service providers outside of the operator's network and terminal devices, and can provide data, voice, and video / voice services to the terminal devices. The specific form of these third parties can be determined based on the actual application scenario and is not limited here.

[0189] For example, Figure 2 The diagram shows the structure of the communication chip in a terminal device. The communication chip mainly consists of a baseband subsystem, a radio frequency subsystem, a power management subsystem, and peripherals (such as storage and external interfaces). The functions of each part are as follows:

[0190] Baseband subsystem: responsible for application layer processing, external interfaces, and L3 / L2 / L1 communication protocol processing;

[0191] Radio frequency (RF) subsystem: The RF front-end and antenna realize the conversion of spatial electromagnetic waves into electrical signals, as well as the required amplification, filtering and other functions to achieve excellent coverage; it connects with the baseband to complete the frequency conversion and nonlinear distortion correction of analog signals;

[0192] Power Management Subsystem: Provides power management functions for communication baseband chips.

[0193] RAN is a sub-network of an operator's network, serving as the implementation system between service nodes and terminal devices within the operator's network. For a terminal device to access the operator's network, it first passes through the RAN, and then connects to service nodes in the operator's network via the RAN. In this application's embodiments, the RAN can be a 3GPP-related cellular system, such as a 5G / new radio (NR) mobile communication system, or a future-oriented evolution system. The RAN can also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), a virtualized radio access network (vRAN), a non-terrestrial network (NTN), etc. The RAN can also be a communication system that integrates two or more of the above systems. In this application's embodiments, the RAN device can also be referred to as a RAN node, RAN entity, or access node, etc.

[0194] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), or a base station in a future mobile communication system. RAN nodes can also be macro base stations, micro base stations, indoor stations, relay nodes, donor / host nodes, or radio controllers. RAN nodes can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in V2X technology, the RAN node can be a roadside unit (RSU).

[0195] In another possible scenario, the RAN node can be a module or unit that performs some of the functions of the base station; or multiple RAN nodes can cooperate to assist terminal equipment in achieving wireless access, with different RAN nodes performing some of the functions of the base station. For example, the RAN node can be a CU, DU, or RU. The function of the CU can be implemented by a single entity or by different entities. For example, the function of the CU can be further divided, that is, the control plane and the user plane can be separated and implemented by different entities, namely the control plane CU entity (i.e., CU-control plane (CP) entity) and the user plane CU entity (i.e., CU-user plane (UP) entity). The CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the function of the RAN node. The CU and DU can be set up separately or included in the same network element, such as in the baseband unit (BBU). Any of the units among the CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented by software modules, hardware modules, or a combination of software modules and hardware modules.

[0196] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples.

[0197] The CU and DU can be configured according to the protocol layer functions of the wireless network they implement: for example, the CU can be configured to implement the functions of the Packet Data Convergence Protocol (PDCP) layer and above (such as the Radio Resource Control (RRC) layer and / or the Service Data Adaptation Protocol (SDAP) layer); the DU can be configured to implement the functions of the protocol layers below the PDCP layer (such as the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and / or the Physical (PHY) layer). For specific descriptions of the above protocol layers, please refer to the relevant 3GPP technical specifications or the technical specifications of other applicable communication protocols.

[0198] The above division of the processing functions of CU and DU according to protocol layers is merely an example; other division methods are also possible, and this application does not limit this. For example, in one design, CU or DU can be further divided into processing functions with protocol layers. In one design, some functions of the RLC layer and the functions of the protocol layer above the RLC layer are located in the CU, while the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer are located in the DU.

[0199] In another possible design, the DU and RU collaborate to implement the PHY layer functionality, or, more specifically, a portion of the PHY layer functionality of the DU can be moved to the RU. A DU can be connected to one or more RUs. The functions of the DU and RU can be configured in various ways depending on the design. For example, the DU may be configured to implement baseband functions, and the RU may be configured to implement mid-RF functions. Alternatively, the DU may be configured to implement higher-level functions in the PHY layer, and the RU may be configured to implement lower-level functions in the PHY layer, or both lower-level and RF functions. Higher-level functions in the physical layer may include a portion of the physical layer's functionality closer to the MAC layer, and lower-level functions may include another portion of the physical layer's functionality closer to the mid-RF side. This application does not limit the specific functions of the DU and RU. The interface between the DU and RU can be called a fronthaul interface. In one design, the CU may not have a PDCP layer; for example, the CU may only include an RRC layer. The CU-CP may not have PDCP-C. The CU-UP may not have PDCP-U, or may not have a CU-UP. In one design, the DU may not have an RLC layer; for example, the DU may only have a MAC and a higher PHY layer.

[0200] When the RAN is O-RAN, it can also have artificial intelligence (AI) capabilities. For example, O-RAN includes an intelligent controller. The intelligent controller can be a non-real-time RAN intelligent controller (RIC / non-RT RIC / NRTRIC) or a near-real-time RAN intelligent controller (RIC / nRT RIC / nRT RIC). A non-real-time RIC can be used to implement non-real-time intelligent management of RAN functions, enabling workflows including model training and updates, and guiding applications / functions in the nRT RIC based on policies. A near-real-time RIC can be used to implement near-real-time intelligent management of the RAN. Through data collection and related operations on the E2 interface, near-real-time control and optimization of O-RAN modules and resources are achieved.

[0201] NSSF network elements are used to select target network elements. NSSF network elements select target network elements based on acquired information, such as parameters provided by the consumer or subscription information obtained from the subscription data management network element. It is understood that in future communication systems, the network element responsible for the above functions may still be an NSSF network element, or may have other names; this application does not impose any limitations.

[0202] AMF (Automatic Facilitation Function) network elements can be used to manage the access control and mobility of terminal devices. Specifically, they can be responsible for terminal device registration, mobility management, tracking area update procedures, reachability detection, selection of session management function network elements, and mobility state transition management. It is understood that in future communication systems, the network elements responsible for the above functions may still be AMF network elements, or may have other names; this application does not impose any limitations.

[0203] SMF network elements can be used to manage terminal devices' sessions (including session establishment, modification, and release), select and reselect user plane function network elements, allocate Internet Protocol (IP) addresses for terminal devices, control quality of service (QoS), collect billing data, and manage roaming. It is understood that in future communication systems, the network elements responsible for the above functions may still be SMF network elements, or may have other names; this application does not impose any limitations.

[0204] The UPF network element is responsible for forwarding and receiving user data in the terminal device. It can receive user data from the data network and transmit it to the terminal device through the access network equipment; the UPF network element can also receive user data from the terminal device through the access network equipment and forward it to the data network. The transmission resources and scheduling functions providing services to the terminal device in the UPF network element are managed and controlled by the SMF network element. It is understood that in future communication systems, the network element responsible for the above functions may still be a UPF network element, or may have other names; this application does not limit this.

[0205] PCF network elements primarily support providing a unified policy framework to control network behavior, providing policy rules to control layer network functions, and acquiring user subscription information related to policy decisions. For example, they can provide rules based on service data flow and application detection, gating, QoS, and flow-based charging control. It is understood that in future communication systems, the network element responsible for the above functions may still be a PCF network element, or may have other names; this application does not impose any limitations.

[0206] UDM network elements are used to generate authentication credentials, process user identifiers (such as storing and managing permanent user identities), control access authorization, and manage subscription data. It is understood that in future communication systems, the network elements responsible for these functions may still be UDM network elements, or may have other names; this application does not impose any limitations.

[0207] AF (AF-based) network elements are used for data routing affected by applications, accessing network open functions, or interacting with policy frameworks for policy control. It is understood that in future communication systems, the network elements responsible for these functions may still be AF network elements, or may have other names; this application does not limit this.

[0208] NEF network elements are used to securely expose services and capabilities provided by 3GPP network functions to the outside world. It is understood that in future communication systems, the network element responsible for the above functions may still be an NEF network element, or may have other names; this application does not limit this.

[0209] NRF network elements are used to store network functional entities and their descriptions of the services they provide, as well as to support functions such as service discovery and network element entity discovery. It is understood that in future communication systems, the network elements responsible for the above functions may still be NRF network elements, or may have other names; this application does not impose any limitations.

[0210] NWDAF network elements can be used for big data analysis. It is understood that in future communication systems, the network elements responsible for the above functions may still be NWDAF network elements, or may have other names; this application does not limit this.

[0211] The NSACF network element is responsible for controlling the number of terminal devices registered in each network slice and the number of sessions corresponding to each network slice. It is understood that in future communication systems, the network element responsible for the above functions may still be an NSACF network element, or may have other names; this application does not limit this.

[0212] The NSSAAF network element is responsible for the authentication and authorization of network slices. In future communication systems, the network element responsible for the above functions may still be an NSSAAF network element, or may have other names; this application does not impose any restrictions.

[0213] DN, also known as Packet Data Network (PDN), is a data network that provides services to users. Typically, clients reside on terminal devices, while servers reside on the data network. Data networks can be private networks, such as local area networks (LANs), external networks not controlled by operators, such as the Internet, or dedicated networks jointly deployed by operators, such as networks providing Internet Protocol (IP) Multimedia Core Network Subsystem (IMS) services.

[0214] It is understood that in practical applications, the above network architecture may also include other network elements, and this application does not limit this.

[0215] It should be noted that the names of the network elements in this application are merely examples, and this application does not preclude the possibility of using other names for the network elements in the future, or the merging of functions between the network elements. With the evolution of technology, any device or network element capable of implementing the functions of the aforementioned network elements is within the scope of protection of this application. Figure 1 The interface names between the various network elements are merely examples; in actual implementations, the interface names may differ, and this application does not impose any specific limitations on them. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0216] For ease of description, each network element will be referred to by its corresponding English abbreviation in the following text, such as "SMF" for the session management function network element, etc.

[0217] See Figure 3 The diagram illustrates a network architecture diagram of another communication system to which embodiments of this application are applicable, which is a RAN-based service architecture. Figure 3Only some network function (NF) elements are listed, such as short message service function (SMSF), PCF, SMF, AMF, UPF, etc. Figure 3 The dashed line in the middle indicates that the connection is not yet complete.

[0218] from Figure 3 As can be seen, in a RAN-based service-oriented architecture, UEs can communicate directly with NFs via the RAN without using the AMF as an anchor point. This reduces AMF congestion. Furthermore, since the AMF doesn't need to be an anchor point, data from the UE to other NFs doesn't pass through the AMF, achieving data isolation and simplifying the process. For the RAN, the N2 interface can also be based on a service-oriented interface protocol, eliminating the need for the AMF as an anchor point. Therefore, the RAN only needs to maintain one set of protocols for each NF. Compared to using the AMF as an anchor point, where operators need to maintain one set of protocols between the access network equipment and the AMF, and another set between the AMF and other NFs, the operator only needs to maintain one set of protocols between the access network equipment and the NFs, resulting in fewer protocols and lower complexity.

[0219] Furthermore, during the process of establishing an AMF connection by sending messages (such as SR) to the terminal device, the security of the access stratum (AS) can be activated to ensure connection security. Additionally, RRC connections and N2 interface connections can be established to ensure reliable message transmission after the connection is established.

[0220] For ease of description, the embodiments of this application are used in... Figure 1 or Figure 3 The network architecture shown is an example. The system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems. It should be noted that the above... Figure 1 , Figure 3 The network elements, functions, or services mentioned can be network components in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). Optionally, the aforementioned network elements, functions, or services can be implemented by a single device, multiple devices working together, or a functional module within a single device; this application does not specifically limit this. Furthermore, some English abbreviations used in this document to describe embodiments of this application using the current 5G network as an example may change as the network evolves; specific evolution can be found in the descriptions in the relevant standards.

[0221] Currently, the standard defines two QoE reporting methods: RAN-based QoE reporting and AF-based QoE reporting. RAN-based QoE reporting is triggered by Operations Administration and Maintenance (OAM) configuration, and the QoE information collected by OAM is mainly used for operation and maintenance management. AF-based QoE reporting is triggered by AF configuration and collected by the AF, which can be a Data Collection Application Function (DCAF). QoE information reported through these two methods can be provided to the NWDAF to assist in service experience analysis. However, the above two methods involve many network elements, resulting in a long data collection chain and significant latency. Furthermore, the OAM method involves RAN modifications, which have a significant impact on the standard. In addition, relying on DCAF technology to obtain QoE information from the UE and relying on OAM technology to obtain QoE information from the UE make commercial deployment difficult. Based on this, this application provides a communication method that enables NWDAF to collect QoE information, reduces latency, and is easier to deploy commercially.

[0222] In the following embodiments, the communication method provided in this application is described in detail using a certain device (or network element) as an example. It should be understood that the operation performed by the certain device (or network element) can also be implemented by the processor, chip or chip system, or functional module in the certain device (or network element).

[0223] Based on the above description, an embodiment of this application provides a communication method, which can be referred to as... Figure 4 As shown, the process of this method may include:

[0224] Step 401: The network data analysis function element sends the first configuration information through the control plane (CP) or user plane (UP). Correspondingly, the terminal device receives the first configuration information through the CP or UP. The first configuration information is used to instruct the terminal device to collect or report QoE information.

[0225] The first configuration information can be described as QoE configuration information or other descriptions, and this application does not limit it in this way.

[0226] For example, the first configuration information may include one or more of the following: the reporting period of QoE information, the event that triggers the reporting of QoE information, business information, application (APP) information, data network name (DNN), slice information, etc.

[0227] Optionally, the business information may include business type and / or business identification (ID). For example, the business type may include one or more of the following: streaming, multimedia telephony service for IMS (MTSI), or virtual reality (VR).

[0228] App information may include the App ID, etc.

[0229] Slice information may include single network slice selection assistance information (S-NSSAI), etc.

[0230] Step 402: The terminal device collects QoE information based on the first configuration information and sends the QoE information through the CP or UP. Correspondingly, the network data analysis function network element receives the QoE information through the CP or UP.

[0231] For example, the QoE information corresponding to different services can contain different content. For instance, the QoE information for dynamic adaptive streaming (DASH), the QoE information for 5G multimedia subsystem (MS), and the QoE information for VR can include one or more of the following: representation switch events, average throughput, initial playout delay, buffer level, playlist, MPD information, playout delay for media start-up, or device information.

[0232] In one optional implementation, the transmission method based on the first configuration information and QoE information may include the following four embodiments:

[0233] Example 1: The network data analysis function network element sends the first configuration information to the terminal device through the CP, and the terminal device sends QoE information to the network data analysis function network element through the CP;

[0234] Example 2: The network data analysis function network element sends the first configuration information to the terminal device through the CP, and the terminal device sends QoE information to the network data analysis function network element through the UP;

[0235] Example 3: The network data analysis function network element sends the first configuration information to the terminal device through the UP, and the terminal device sends QoE information to the network data analysis function network element through the CP;

[0236] Example 4: The network data analysis function network element sends the first configuration information to the terminal device through the UP, and the terminal device sends QoE information to the network data analysis function network element through the UP.

[0237] The four embodiments described above will be described in detail below.

[0238] Example 1

[0239] The network data analysis function network element sends the first configuration information through transmission messages, and correspondingly, the terminal device receives the first configuration information through NAS signaling.

[0240] For example, a network data analysis function network element sends first configuration information to a first device via a first transmission message, and the first device sends the first configuration information to a terminal device via a first NAS signaling. The first device can be an access and mobility management function network element, or it can be a session management function network element.

[0241] Optionally, when the first device is an access and mobility management function network element, the first NAS signaling includes a first container, and the first container includes first configuration information.

[0242] The first container can also be described as a QoE configuration container or other descriptions, which are not limited in this application.

[0243] In some possible scenarios, when the first device is an access and mobility management function network element, the first NAS signaling can be a registration acceptance message or a downlink (DL) transport message. When the first device is a session management function network element, the first NAS signaling can be a session message, such as a session establishment acceptance message or a session modification command message.

[0244] The first transfer message can be a newly defined message or a message transmitted through a newly defined interface. When the first device is an access and mobility management function network element, the first transfer message can also reuse an existing message, and this application does not limit this.

[0245] Optionally, the first transfer message may also carry the SUPI of the terminal device.

[0246] For QoE information, the terminal device collects QoE information based on the first configuration information and sends QoE information through NAS signaling. Correspondingly, the network data analysis function network element receives QoE information through transmission messages.

[0247] For example, the terminal device sends QoE information to the first device through the second NAS signaling. After receiving the second NAS signaling, the first device sends QoE information to the network data analysis function network element through the second transmission message.

[0248] Optionally, when the first device is an access and mobility management function network element, the second NAS signaling includes a second container, and the second container includes the QoE information.

[0249] In some possible scenarios, when the first device is an access and mobility management function network element, the second NAS signaling can be a registration request message or an uplink (UL) transport message. When the first device is a session management function network element, the second NAS signaling can be a session request message.

[0250] The second transmitted message can be an N1 notification message. Alternatively, the second transmitted message can be a newly defined message, or a message transmitted through a newly defined interface.

[0251] Optionally, in the downlink transmission where the network data analysis function network element sends the first configuration information to the terminal device, and in the uplink transmission where the terminal device sends QoE information to the network device, the first device can be different devices or the same device. For example, the network data analysis function network element can send the first configuration information to the terminal device through the session management function network element, and the terminal device can send QoE information through the access and mobility management function network element. Alternatively, the network data analysis function network element can send the first configuration information to the terminal device through the access and mobility management function network element, and the terminal device can send QoE information through the access and mobility management function network element. Other situations are also possible, and this application does not limit them.

[0252] Example 2

[0253] The specific method by which the network data analysis function network element sends the first configuration information to the terminal device through the CP can be found in the aforementioned Embodiment 1, and will not be described again here.

[0254] For QoE information, the terminal device can establish a PDU session (referred to as the first PDU session in this application) for transmitting QoE information, and send the QoE information through the first PDU session. Correspondingly, the network data analysis function network element receives the QoE information through the first PDU session.

[0255] In one optional implementation, the terminal device may receive a first message from a policy control function network element. The first message includes first indication information, which is used to indicate the establishment of a PDU session for transmitting QoE information.

[0256] Optionally, the first message may include routing policy rules, which include first indication information.

[0257] For example, the routing policy rule includes a traffic descriptor, which includes the first indication information.

[0258] Optionally, the routing policy rule may also include a routing descriptor, which includes attributes used to establish the first PDU session.

[0259] For example, the first message (e.g., downlink transport message) may contain a policy container, which contains extended UE route selection policy (URSP) rules. The current URSP rule contains a traffic descriptor and a route selection descriptor. The traffic descriptor contains flow identifiers, such as APP ID, Internet protocol (IP) triples, and connection capabilities. The route selection descriptor contains various attributes used to establish a PDU session, such as PDU session type, session and service continuity (SSC) mode, DNN, and S-NSSAI. In this application, a QoE indication (i.e., the first indication information) can be defined in the traffic descriptor. Optionally, this application can implement this by defining a type in the connection capabilities.

[0260] For example, the QoE indicator can be used in conjunction with other flow indicators. For instance, if the QoE indicator is used with the APP ID, it can be understood that the APP's QoE information establishes a dedicated PDU session.

[0261] Furthermore, the terminal device can send a first PDU session establishment request to the session management function network element according to the first instruction information to request the establishment of a first PDU session. The session management function network element establishes a PDU session (i.e., the first PDU session) for transmitting QoE information according to the first PDU session establishment request.

[0262] Optionally, when the terminal device has data for its current service or when a service is in progress, the terminal device collects QoE information based on the first configuration information and triggers the sending of a first PDU session establishment request to the session management function network element.

[0263] Example 3

[0264] The network data analysis function network element can send the first configuration information through a PDU session (which may be referred to as the second PDU in this application) used for transmitting the first configuration information. Correspondingly, the terminal device receives the first configuration information through the second PDU session.

[0265] In some embodiments, the terminal device establishes a PDU session for transmitting first configuration information.

[0266] Optionally, the terminal device may receive a fifth message from a policy control function network element, the fifth message including second indication information, the second indication information being used to indicate the establishment of a PDU session for transmitting first configuration information.

[0267] Optionally, the fifth message may include routing policy rules, which include second instruction information.

[0268] For example, the routing policy rule includes a traffic descriptor, which includes the second indication information.

[0269] Optionally, the routing policy rule may also include a routing descriptor, which includes attributes for establishing a second PDU session.

[0270] For example, the content format of the fifth message is similar to that of the first message, as can be seen in the aforementioned first message, and will not be described in detail here.

[0271] Furthermore, the terminal device can send a second PDU session establishment request to the session management function network element according to the second instruction information to request the establishment of a second PDU session. The session management function network element establishes a PDU session (i.e., the second PDU session) for transmitting the first configuration information according to the second PDU session establishment request.

[0272] In some implementations, the specific method by which the terminal device sends QoE information to the network data analysis function network element through the CP can be found in the aforementioned Embodiment 1, and will not be described again here.

[0273] Example 4

[0274] The specific method for the network data analysis function network element to send the first configuration information to the terminal device through the UP can be found in the aforementioned Embodiment 3. The specific method for the terminal device to send QoE information to the network data analysis function network element through the UP can be found in the aforementioned Embodiment 2. It will not be described again here.

[0275] Optionally, in this fourth embodiment, the first message and the fifth message can be the same message, the first indication information and the second indication information can be the same indication information, and the first PDU session and the second PDU can be the same PDU session. That is, a PDU session for transmitting QoE-related data can be established, and the PDU session can be used to transmit the first configuration information and QoE information.

[0276] In some embodiments, the first configuration information is determined based on the QoE reporting capability supported by the terminal device.

[0277] In one optional implementation, the QoE reporting capability supported by the terminal device may include one or more of the following: service granularity, application (APP) granularity, data network name (DNN) granularity, or slice granularity.

[0278] For example, the granularity of a service can include one or more of the following: streaming, multimedia telephony service for IMS (MTSI), or virtual reality (VR). The granularity of an app can be represented by an app identifier (ID). The granularity of a slice can be represented by single network slice selection assistance information (S-NSSAI).

[0279] In one possible approach, when the terminal device supports multiple of the above-mentioned QoE reporting capabilities, it can include both DNN granularity and slice granularity. Of course, this is merely an example, and this application does not limit its scope.

[0280] Optionally, before sending the first configuration information, the network data analysis function network element obtains the QoE reporting capabilities supported by the terminal device and determines the first configuration information based on the QoE reporting capabilities supported by the terminal device. This can be understood as the first configuration information being matched with the QoE reporting capabilities of the terminal device.

[0281] In some embodiments, the terminal device sends a second message to the first device, and the first device receives the second message, which includes the QoE reporting capability supported by the terminal device. Further, the first device sends a fourth message to the network data analysis function network element, the fourth message including the QoE reporting capability supported by the terminal device. Based on this, the network data analysis function network element can obtain the QoE reporting capability supported by the terminal device.

[0282] Optionally, when the first device is an access and mobility management function network element, the second message can be a registration request message sent by the terminal device. When the first device is a session management function network element, the second message can be a session request message (such as a PDU session establishment request).

[0283] Of course, the second message can also be other messages, and this application does not limit this.

[0284] In one example, the terminal device may send the second message based on the first trigger information.

[0285] Optionally, the upper layer or application layer of the terminal device may, based on the first triggering information, instruct the modem via an AT command to trigger the modem to send the second message.

[0286] The first triggering information is triggered by the user, who can trigger it according to their needs.

[0287] For example, a terminal device might have a switch. When the switch is turned on (by the user), this is interpreted as triggering the first trigger message, which is sent to the modem via an AT command. This triggers the modem to send a second message reporting the QoE reporting capabilities supported by the terminal device. This approach can be understood as a coarse-grained capability reporting method, meaning it doesn't limit reporting to any particular capability.

[0288] For example, the terminal device has multiple options (such as streaming, MTSI and VR) for the user to choose from. When the user selects a certain option, the first trigger message is triggered, which is sent to the modem via AT command. The modem then reports fine-grained capabilities, that is, the second message contains the QoE reporting capability that supports streaming, MTSI or VR.

[0289] For example, the user interface of a terminal device allows the user to select the granularity of a certain APP. The user can choose to report QoE for a specific APP. After the user makes the selection, the first trigger message is triggered. Then, the upper layer or application layer of the terminal device sends the application information (such as APP ID) to the modem through ATcommand. Then, the modem sends the QoE reporting capability that supports the APP (that is, sends the second message, which contains the QoE reporting capability that supports the APP).

[0290] For example, the user interface of the terminal device can indicate the information of DNN and NSSAI for the user to choose from. After the user makes a selection, the QoE reporting capability supporting DNN, NSSAI, and DNN+NSSAI can be sent through a second message.

[0291] In one example, when the first device is an access and mobility management function network element, after receiving the second message and obtaining the QoE reporting capability supported by the terminal device, the access and mobility management function network element can send a fourth message to the network data analysis function network element in the following way to notify the network data analysis function network element of the QoE reporting capability supported by the terminal device.

[0292] In method a1, the access and mobility management function (AM) network element sends the fourth message to the network data analysis function (QoE) network element through a first interface. Correspondingly, the network data analysis function network element receives the fourth message from the AM AM network element through the first interface.

[0293] The first interface can be understood as a service interface between predefined access and mobility management function network elements and network data analysis function network elements. This first interface is used to transmit information or signaling related to QoE.

[0294] In this mode a1, once the access and mobility management function network element receives a supported QoE reporting capability sent by any terminal device, it instructs the network data analysis function network element on the supported QoE reporting capability of that terminal device.

[0295] In method a1, the fourth message can be QoE service information.

[0296] Method a2: The network data analysis function network element sends first subscription information to the access and mobility management function network element, and the access and mobility management function network element sends the fourth message to the network data analysis function network element based on the first subscription information. The first subscription information is used to subscribe to events indicating that the terminal device supports QoE reporting capability, or to subscribe to events indicating that the terminal device supports QoE reporting capability and other terminal devices support QoE reporting capability.

[0297] Optionally, the network device analysis function network element may send the first subscription information to the access and mobility management function network element before the terminal device sends the second message.

[0298] The first subscription information is used to subscribe to events indicating that the terminal device supports QoE reporting capabilities. This can be understood as the network device analysis function element subscribing to the reporting of QoE reporting capabilities supported by a specific terminal device. In this case, the first subscription information may include the identifier of the terminal device (such as a subscription permanent identifier (SUPI)). Further, after receiving information about the terminal device's supported QoE reporting capabilities, the access and mobility management function element can send a fourth message to the network device analysis function element to notify it of the terminal device's supported QoE reporting capabilities.

[0299] The first subscription information is used to subscribe to events indicating that the terminal device supports QoE reporting capabilities and other terminal devices support QoE reporting capabilities. This can be understood as subscribing to events indicating that any terminal device supports QoE reporting capabilities. In this case, after receiving information indicating that any terminal device supports QoE reporting capabilities, the access and mobility management function network element can send this information to the network device analysis function network element.

[0300] In method a2, the fourth message can be a subscription notification message.

[0301] Optionally, in methods a1 and a2 above, the fourth message may also include the identifier of the terminal device, such as the SUPI of the terminal device.

[0302] When different terminal devices support different QoE reporting capabilities through the two methods described above, the access and mobility management function network element indicates to the network data analysis function network element that different terminal devices support different QoE reporting capabilities.

[0303] In another example, when the first device is a session management function network element, after receiving the second message and obtaining the QoE reporting capability supported by the terminal device, the session management function network element can send a fourth message to the network data analysis function network element in the following way to notify the network data analysis function network element of the QoE reporting capability supported by the terminal device.

[0304] Method b1: The session management function network element sends a fourth message to the network data analysis function network element. The fourth message indicates that the PDU session for transmitting QoE information has been established. The fourth message includes the QoE reporting capability supported by the terminal device.

[0305] This method b1 can be understood as follows: when the session management function network element establishes a PDU session specifically for transmitting QoE information, it can notify the network data analysis function network element and simultaneously indicate the QoE reporting capability supported by the terminal device to the network data analysis function network element.

[0306] Method b2: The network data analysis function network element sends a second subscription information to the session management function network element. The second subscription information is used to indicate that the network data analysis function network element should be notified after the PDU session is established. The network data analysis function network element receives a fourth message from the session management function network element. The fourth message indicates that the PDU session has been established. The fourth message includes the QoE reporting capability supported by the terminal device.

[0307] This method, b2, can be understood as follows: the network data analysis function element subscribes in advance to the event of establishing a new PDU session, and the session management function element notifies the network data analysis function element when a new PDU session is established. Simultaneously, the session management function element indicates the QoE reporting capability supported by the terminal device to the network data analysis function element.

[0308] Optionally, the fourth message may also include the identifier of the terminal device (such as SUPI).

[0309] In one alternative implementation, the terminal device can receive the first configuration information by subscription, and correspondingly, the network data analysis function network element can send the first configuration information by subscription.

[0310] For example, a network data analysis function network element sends third subscription information to the terminal device. This third subscription information is used to subscribe to the QoE information from the terminal device, and the third subscription message includes the first configuration information. Correspondingly, the terminal device receives the third subscription information from the network data analysis function network element, and the third subscription message includes the first configuration information. Alternatively, it can be understood that when the network data analysis function network element subscribes to QoE information via subscription, it simultaneously sends the first configuration information.

[0311] Based on the first configuration information, in some embodiments, the terminal device can send the QoE information according to a first period based on the first configuration information. The first period is included in the first configuration information.

[0312] Based on the first configuration information, in some other embodiments, the terminal device can determine, according to the first configuration information, that a first event must be met before sending the QoE information. The first event is included in the first configuration information.

[0313] It should be understood that when the terminal device sends QoE information based on the first cycle or the first event, it can still send it in any of the methods in Embodiments 1 to 4.

[0314] In some embodiments, the terminal device may send a third message for establishing a secure connection. Correspondingly, the network data analysis function network element may receive this third message. This ensures the security of QoE information and other data transmitted between the network data analysis function network element and the terminal device.

[0315] In some implementations, the signaling or messages of this application may reuse existing messages, or may be newly defined messages, or may be transmitted through a newly defined interface. This application does not limit this.

[0316] Using the above method, the network data analysis function network element and the terminal device can directly transmit the first configuration information and QoE information through CP or UP without obtaining them through OAM and AF. This can reduce the latency of QoE information reporting, and the network data analysis function network element does not need to rely on DCAF technology or OAM technology to obtain QoE information from the terminal device, making it easier to commercially deploy.

[0317] based on Figure 4 The embodiments shown below are explained through... Figures 5 to 12 The example shown is for Figure 4 The communication method provided in the illustrated embodiments is given by way of example. In the following examples, the terminal device is UE, the network data analysis function network element is NWDAF, the access and mobility management function network element is AMF, and the session management function network element is SMF, etc., are used as examples for illustrative purposes.

[0318] Figure 5 An example of a communication method is shown, in which both QoE configuration information (i.e., the first configuration information in this application) and QoE information transmission are implemented based on CP, serving as a container for transmission between the UE and AMF. Exemplarily, the process of this example may include:

[0319] Step 501: NWDAF sends the first subscription information to AMF. The first subscription information is used to subscribe to events that a specific UE supports QoE reporting capability, or to subscribe to events that all UEs (or any UE) support QoE reporting capability.

[0320] Specifically, when the first subscription information is used to subscribe to events of the QoE reporting capability supported by a specific UE, the first subscription information may include the SUPI of that specific UE.

[0321] Step 501 is optional.

[0322] Step 502: The UE sends a second message to the AMF, which contains the QoE reporting capabilities supported by the UE.

[0323] The second message can be a registration request message sent by the UE.

[0324] The specific implementation process of the UE sending the second message can be found in the aforementioned document. Figure 4 The relevant descriptions involved in the illustrated embodiments will not be repeated here.

[0325] It should be understood that messages or information sent by the UE to the AMF can be transmitted through the RAN, which will not be described in detail in this application.

[0326] Step 503: The AMF sends a fourth message to the NWDAF, which includes the QoE reporting capability supported by the UE.

[0327] The specific method by which the AMF sends the fourth message to the NWDAF can be found in the relevant descriptions of the aforementioned methods a1 and a2, and will not be repeated here.

[0328] It should be understood that when the AMF sends the fourth message to the NWDAF in accordance with method a2, the aforementioned step 501 exists.

[0329] Step 504: NWDAF determines the first configuration information based on the QoE reporting capability supported by the UE.

[0330] The first configuration information can be found in the aforementioned document. Figure 4 The relevant descriptions involved in the illustrated embodiments will not be repeated here.

[0331] Step 505: NWDAF sends a first transmission message to AMF, the first transmission message including first configuration information.

[0332] For details, please refer to the relevant descriptions mentioned above, which will not be repeated here.

[0333] Step 506: The AMF sends a first NAS signaling message to the UE. The first NAS signaling message includes a first container, and the first container includes first configuration information.

[0334] The first NAS signaling can be a registration acceptance message or a downlink transmission message, etc.

[0335] For details, please refer to the relevant descriptions mentioned above, which will not be repeated here.

[0336] Step 507: The UE collects QoE information according to the first configuration information and sends a second NAS signaling to the AMF. The second NAS signaling includes a second container, and the second container includes QoE information.

[0337] When there is data in the current PDU session, the terminal device collects QoE information.

[0338] Step 508: AMF sends a second transmission message to NWDAF, the second transmission message including QoE information.

[0339] Specifically, the UE can send QoE information to the NWDAF via the AMF either periodically or through an event. For details, please refer to the aforementioned descriptions, which will not be repeated here.

[0340] Based on the above example, the first configuration information and QoE information can be carried in a container, which can reduce the latency of QoE information transmission, improve the efficiency of QoE information transmission, and ensure the transmission of QoE information.

[0341] Figure 6 An example of another communication method is shown, in which QoE configuration information (i.e., the first configuration information in this application) and QoE information transmission are both implemented based on CP. Figure 5 The difference in the example shown is that the SMF receives the QoE reporting capability supported by the UE, and the NWDAF sends the first configuration information through the AMF. For example, the process in this example may include:

[0342] Step 601: NWDAF sends a second subscription message to SMF, which is used to indicate that NWDAF should be notified after a PDU session is established.

[0343] Step 601 is optional.

[0344] Step 602: The UE sends a second message to the SMF, which contains the QoE reporting capabilities supported by the UE.

[0345] The second message may be a PDU session establishment request sent by the UE.

[0346] The specific implementation process of the UE sending the second message can be found in the aforementioned document. Figure 4 The relevant descriptions involved in the illustrated embodiments will not be repeated here.

[0347] It should be understood that messages or information sent by the UE to the SMF can be transmitted through the RAN, which will not be described in detail in this application.

[0348] Step 603: The SMF sends a fourth message to the NWDAF, which includes the QoE reporting capability supported by the UE.

[0349] The specific method by which SMF sends the fourth message to NWDAF can be found in the relevant descriptions of methods b1 and b2 mentioned above, and will not be repeated here.

[0350] It should be understood that when the SMF sends the fourth message to the NWDAF in accordance with method b2, the aforementioned step 601 exists.

[0351] Step 604: NWDAF determines the first configuration information based on the QoE reporting capability supported by the UE.

[0352] The first configuration information can be found in the aforementioned document. Figure 4 The relevant descriptions involved in the illustrated embodiments will not be repeated here.

[0353] Step 605: NWDAF sends a first transmission message to AMF, the first transmission message including first configuration information.

[0354] For details, please refer to the relevant descriptions mentioned above, which will not be repeated here.

[0355] Step 606: The AMF sends a first NAS signaling message to the UE. The first NAS signaling message includes a first container, and the first container includes first configuration information.

[0356] For details, please refer to the relevant descriptions mentioned above, which will not be repeated here.

[0357] Step 607: The UE collects QoE information according to the first configuration information and sends a second NAS signaling to the AMF. The second NAS signaling includes a second container, and the second container includes QoE information.

[0358] When there is data in the current PDU session, the terminal device collects QoE information.

[0359] Step 608: AMF sends a second transmission message to NWDAF, the second transmission message including QoE information.

[0360] Specifically, the UE can send QoE information to the NWDAF via the AMF either periodically or through an event. For details, please refer to the aforementioned descriptions, which will not be repeated here.

[0361] Based on the above example, the first configuration information and QoE information can be carried in a container, which can reduce the latency of QoE information transmission, improve the efficiency of QoE information transmission, and ensure the transmission of QoE information.

[0362] Figure 7 An example of another communication method is shown, in which QoE configuration information (i.e., the first configuration information in this application) and QoE information transmission are both implemented based on CP. Figure 5 The difference in the example shown is that the SMF receives the QoE reporting capability supported by the UE, and the NWDAF sends the first configuration information through the SMF. For example, the process in this example may include:

[0363] Step 701: NWDAF sends a second subscription message to SMF, which is used to indicate that NWDAF should be notified after a PDU session is established.

[0364] Step 701 is optional.

[0365] Step 702: The UE sends a second message to the SMF, which contains the QoE reporting capabilities supported by the UE.

[0366] The second message can be a PDU session establishment request message sent by the UE.

[0367] The specific implementation process of the UE sending the second message can be found in the aforementioned document. Figure 4 The relevant descriptions involved in the illustrated embodiments will not be repeated here.

[0368] It should be understood that messages or information sent by the UE to the SMF can be transmitted through the RAN, which will not be described in detail in this application.

[0369] Step 703: The SMF sends a fourth message to the NWDAF, which includes the QoE reporting capability supported by the UE.

[0370] The specific method by which SMF sends the fourth message to NWDAF can be found in the relevant descriptions of methods b1 and b2 mentioned above, and will not be repeated here.

[0371] It should be understood that when the SMF sends the fourth message to the NWDAF in accordance with method b2, the aforementioned step 701 exists.

[0372] Step 704: NWDAF determines the first configuration information based on the QoE reporting capability supported by the UE.

[0373] The first configuration information can be found in the aforementioned document. Figure 4 The relevant descriptions involved in the illustrated embodiments will not be repeated here.

[0374] Step 705: NWDAF sends a first transmission message to SMF, the first transmission message including first configuration information.

[0375] For details, please refer to the relevant descriptions mentioned above, which will not be repeated here.

[0376] Step 706: The SMF sends the first NAS signaling to the UE. The first NAS signaling includes the first configuration information.

[0377] The first NAS signaling can be a session accept message or a session modify message.

[0378] For details, please refer to the relevant descriptions mentioned above, which will not be repeated here.

[0379] Step 707: The UE collects QoE information according to the first configuration information and sends a second NAS signaling to the AMF. The second NAS signaling includes a second container, and the second container includes QoE information.

[0380] When there is data in the current PDU session, the terminal device collects QoE information.

[0381] Step 708: AMF sends a second transmission message to NWDAF, the second transmission message including QoE information.

[0382] Specifically, the UE can send QoE information to the NWDAF via SMF either periodically or through an event. For details, please refer to the aforementioned descriptions, which will not be repeated here.

[0383] It should be noted that the UE reporting QoE information here is only illustrated using steps 707 and 708 as examples. Optionally, the UE can also report QoE information to the NWDAF through the SMF. For example, step 707 can be replaced by step 707a: the UE collects QoE information according to the first configuration information and sends a second NAS signaling to the SMF, the second NAS signaling including QoE information; step 708 can be replaced by step 708a: the SMF sends a second transmission message to the NWDAF, the second transmission message including QoE information, which is not shown in the illustration here.

[0384] Based on the above example, the first configuration information and QoE information can be carried in a container, which can reduce the latency of QoE information transmission, improve the efficiency of QoE information transmission, and ensure the transmission of QoE information.

[0385] Figure 8 An example of another communication method is shown, in which the transmission of QoE configuration information (i.e., the first configuration information in this application) is implemented based on CP, and QoE information transmission is implemented based on UP. Exemplarily, the process of this example may include:

[0386] Step 801: The PCF sends a first message to the UE. The first message includes first indication information, which is used to indicate the establishment of a PDU session for transmitting QoE information.

[0387] For details, please refer to the aforementioned descriptions, which will not be repeated here.

[0388] Step 801 is an optional step.

[0389] Step 802: The UE sends a second message to the AMF, which contains the QoE reporting capabilities supported by the UE.

[0390] The second message can be a registration request message sent by the UE.

[0391] The specific implementation process of the UE sending the second message can be found in the aforementioned document. Figure 4 The relevant descriptions involved in the illustrated embodiments will not be repeated here.

[0392] It should be understood that messages or information sent by the UE to the AMF can be transmitted through the RAN, which will not be described in detail in this application.

[0393] Step 803: The AMF sends a fourth message to the NWDAF, which includes the QoE reporting capability supported by the UE.

[0394] The specific method by which the AMF sends the fourth message to the NWDAF can be found in the relevant descriptions of the aforementioned methods a1 and a2, and will not be repeated here.

[0395] Step 804: NWDAF determines the first configuration information based on the QoE reporting capability supported by the UE.

[0396] The first configuration information can be found in the aforementioned document. Figure 4 The relevant descriptions involved in the illustrated embodiments will not be repeated here.

[0397] Step 805: NWDAF sends a first transmission message to AMF, the first transmission message including first configuration information.

[0398] For details, please refer to the relevant descriptions mentioned above, which will not be repeated here.

[0399] Step 806: The AMF sends a first NAS signaling message to the UE. The first NAS signaling message includes a first container, and the first container includes first configuration information.

[0400] For details, please refer to the relevant descriptions mentioned above, which will not be repeated here.

[0401] Optionally, the UE may send a message responding to the first NAS signaling to the AMF, such as an acknowledgment character (ACK) message; furthermore, the AMF may send a message responding to the first transmission message to the NWDAF, such as an ACK message.

[0402] Step 807: The UE sends a first PDU session establishment request to the SMF. The first PDU session establishment request is used to request the establishment of a PDU session for transmitting QoE information (i.e., the first PDU session).

[0403] Optionally, when a service is in progress, the UE collects QoE information based on the first configuration information and triggers the establishment of the first PDU session, i.e., executes step 807.

[0404] Step 808: SMF establishes the first PDU session.

[0405] Step 809: The UE sends a third message to the NWDAF, which is used to establish a secure connection.

[0406] Step 809 is an optional step.

[0407] Step 810: The UE sends QoE information to the NWDAF through the first PDU session.

[0408] Based on the above example, the first configuration information can be carried by a container, and QoE information can be transmitted through a PDU session, which can reduce the latency of QoE information transmission, improve the efficiency of QoE information transmission, and ensure the transmission of QoE information.

[0409] Figure 9 An example of another communication method is shown, in which the transmission of QoE configuration information (i.e., the first configuration information in this application) is implemented based on CP, and all QoE information transmission is implemented based on UP. Figure 8 The difference is that in this example, the SMF receives the QoE reporting capability supported by the UE. For example, the process in this example may include:

[0410] Step 901: The PCF sends a first message to the UE. The first message includes first indication information, which is used to indicate the establishment of a PDU session for transmitting QoE information.

[0411] For details, please refer to the aforementioned descriptions, which will not be repeated here.

[0412] Step 901 is an optional step.

[0413] Step 902: The UE sends a second message to the SMF, which contains the QoE reporting capabilities supported by the UE.

[0414] The second message may be a PDU session establishment request sent by the UE.

[0415] The specific implementation process of the UE sending the second message can be found in the aforementioned document. Figure 4 The relevant descriptions involved in the illustrated embodiments will not be repeated here.

[0416] It should be understood that messages or information sent by the UE to the SMF can be transmitted through the RAN, which will not be described in detail in this application.

[0417] Optionally, the SMF can send a PDU session establishment accept message to the UE in response to the PDU session establishment request.

[0418] Step 903: The SMF sends a fourth message to the NWDAF, which includes the QoE reporting capability supported by the UE.

[0419] The specific method by which SMF sends the fourth message to NWDAF can be found in the relevant descriptions of methods a1 and a2 mentioned above, and will not be repeated here.

[0420] Step 904: NWDAF determines the first configuration information based on the QoE reporting capability supported by the UE.

[0421] The first configuration information can be found in the aforementioned document. Figure 4 The relevant descriptions involved in the illustrated embodiments will not be repeated here.

[0422] Step 905: NWDAF sends a first transmission message to AMF, the first transmission message including first configuration information.

[0423] For details, please refer to the relevant descriptions mentioned above, which will not be repeated here.

[0424] Optionally, the first transmission message can be used to request the UE to report QoE information, and the first transmission message may also include the NWDAF address.

[0425] Step 906: The AMF sends a first NAS signaling message to the UE. The first NAS signaling message includes a first container, and the first container includes first configuration information.

[0426] The first NAS signaling can be a DL transmission message.

[0427] For details, please refer to the relevant descriptions mentioned above, which will not be repeated here.

[0428] Optionally, the UE may send a message responding to the first NAS signaling to the AMF, such as an acknowledgment character (ACK) message; furthermore, the AMF may send a message responding to the first transmission message to the NWDAF, such as an ACK message.

[0429] Step 907: The UE sends a first PDU session request to the SMF. The first PDU session request is used to request the establishment of a PDU session for transmitting QoE information (i.e., the first PDU session).

[0430] Optionally, when a service is in progress, the UE collects QoE information based on the first configuration information and triggers the establishment of the first PDU session, i.e., executes step 907.

[0431] Optionally, the UE sends a first PDU session request to the SMF based on the first indication information.

[0432] Step 908: SMF establishes the first PDU session.

[0433] Step 909: The UE sends QoE information to the NWDAF through the first PDU session.

[0434] Based on the above example, the first configuration information can be carried by a container, and QoE information can be transmitted through a PDU session, which can reduce the latency of QoE information transmission, improve the efficiency of QoE information transmission, and ensure the transmission of QoE information.

[0435] Figure 10 An example of another communication method is shown, in which the transmission of QoE configuration information (i.e., the first configuration information in this application) is implemented based on CP, and all QoE information transmission is implemented based on UP. Figure 9 The difference is that in this example, the NWDAF sends the first configuration information to the UE via the SMF. For example, the process in this example may include:

[0436] Step 1001: The PCF sends a first message to the UE. The first message includes first indication information, which is used to indicate the establishment of a PDU session for transmitting QoE information.

[0437] For details, please refer to the aforementioned descriptions, which will not be repeated here.

[0438] Step 1001 is an optional step.

[0439] Step 1002: The UE sends a second message to the SMF, which contains the QoE reporting capabilities supported by the UE.

[0440] The second message may be a PDU session establishment request sent by the UE.

[0441] The specific implementation process of the UE sending the second message can be found in the aforementioned document. Figure 4 The relevant descriptions involved in the illustrated embodiments will not be repeated here.

[0442] It should be understood that messages or information sent by the UE to the SMF can be transmitted through the RAN, which will not be described in detail in this application.

[0443] Optionally, the SMF can send a PDU session establishment accept message to the UE in response to the PDU session establishment request.

[0444] Step 1003: The SMF sends a fourth message to the NWDAF, which includes the QoE reporting capability supported by the UE.

[0445] The specific method by which SMF sends the fourth message to NWDAF can be found in the relevant descriptions of methods a1 and a2 mentioned above, and will not be repeated here.

[0446] Step 1004: NWDAF determines the first configuration information based on the QoE reporting capability supported by the UE.

[0447] The first configuration information can be found in the aforementioned document. Figure 4 The relevant descriptions involved in the illustrated embodiments will not be repeated here.

[0448] Step 1005: NWDAF sends a first transmission message to SMF, the first transmission message including first configuration information.

[0449] For details, please refer to the relevant descriptions mentioned above, which will not be repeated here.

[0450] Step 1006: The SMF sends the first NAS signaling to the UE. The first NAS signaling includes the first configuration information.

[0451] The first NAS signaling can be a PDU session accept message or a PDU session modify message.

[0452] For details, please refer to the relevant descriptions mentioned above, which will not be repeated here.

[0453] Optionally, the UE may send a message responding to the first NAS signaling to the SMF, such as an acknowledgment character (ACK) message; furthermore, the SMF may send a message responding to the first transmission message to the NWDAF, such as an ACK message.

[0454] Step 1007: The UE sends a first PDU session request to the SMF. The first PDU session request is used to request the establishment of a PDU session for transmitting QoE information (i.e., the first PDU session).

[0455] Optionally, when a service is in progress, the UE collects QoE information based on the first configuration information and triggers the establishment of the first PDU session, i.e., executes step 1007.

[0456] Optionally, the UE sends a first PDU session request to the SMF based on the first indication information.

[0457] Step 1008: SMF establishes the first PDU session.

[0458] Step 1009: The UE sends QoE information to the NWDAF through the first PDU session.

[0459] Based on the above example, the first configuration information can be carried by a container, and QoE information can be transmitted through a PDU session, which can reduce the latency of QoE information transmission, improve the efficiency of QoE information transmission, and ensure the transmission of QoE information.

[0460] Figure 11 An example of another communication method is shown, in which QoE configuration information and QoE information reporting can be implemented based on UP, and transmission between the UE and NWDAF is via the user plane. QoE information is carried by a dedicated PDU session to ensure real-time QoE information transmission. For example, the process of this example may include:

[0461] Step 1101: The PCF sends a first message and a fifth message to the UE. The first message includes a first indication information, which is used to indicate the establishment of a PDU session for transmitting QoE information. The fifth message includes a second indication information, which is used to indicate the establishment of a PDU session for transmitting first configuration information.

[0462] For details, please refer to the aforementioned descriptions, which will not be repeated here.

[0463] Step 1101 is an optional step.

[0464] Step 1102: NWDAF sends the first subscription information to AMF. The first subscription information is used to subscribe to events of QoE reporting capabilities supported by a specific UE, or to subscribe to events of QoE reporting capabilities supported by all UEs (which can also be understood as any UE).

[0465] Specifically, when the first subscription information is used to subscribe to events of the QoE reporting capability supported by a specific UE, the first subscription information may include the SUPI of that specific UE.

[0466] Step 1102 is optional.

[0467] For details, please refer to the above description, which will not be repeated here.

[0468] Step 1103: The UE sends a second message to the AMF, which contains the QoE reporting capabilities supported by the UE.

[0469] The second message can be a registration request message sent by the UE.

[0470] The specific implementation process of the UE sending the second message can be found in the aforementioned document. Figure 4 The relevant descriptions involved in the illustrated embodiments will not be repeated here.

[0471] It should be understood that messages or information sent by the UE to the AMF can be transmitted through the RAN, which will not be described in detail in this application.

[0472] Step 1104: The AMF sends a fourth message to the NWDAF, which includes the QoE reporting capability supported by the UE.

[0473] The specific method by which the AMF sends the fourth message to the NWDAF can be found in the relevant descriptions of the aforementioned methods a1 and a2, and will not be repeated here.

[0474] It should be understood that when the AMF sends the fourth message to the NWDAF in accordance with method a2, the aforementioned step 1102 exists.

[0475] Step 1105: NWDAF determines the first configuration information based on the QoE reporting capability supported by the UE.

[0476] The first configuration information can be found in the aforementioned document. Figure 4 The relevant descriptions involved in the illustrated embodiments will not be repeated here.

[0477] Step 1106: NWDAF sends a message to AMF requesting the UE to report QoE information.

[0478] Step 1107: The AMF sends a message to the UE requesting the UE to report QoE information.

[0479] Step 1108: The UE sends a first PDU session request and a second PDU session establishment request to the SMF. The first PDU session request is used to request the establishment of a PDU session for transmitting QoE information (i.e., the first PDU session). The second PDU session establishment request can be used to request the establishment of a PDU session for transmitting first configuration information (i.e., the second PDU session).

[0480] Optionally, when a service is in progress, the UE collects QoE information based on the first configuration information and triggers the establishment of the first PDU session, i.e., executes step 1108.

[0481] Optionally, the UE sends a first PDU session establishment request to the SMF according to the first indication information, and sends a second PDU session establishment request to the SMF according to the second indication information.

[0482] Step 1109: SMF establishes the first PDU session and the second PDU session.

[0483] Step 1110: The UE sends a third message to the NWDAF, which is used to establish a secure connection.

[0484] Step 1110 is an optional step.

[0485] Step 1111: NWDAF sends the first configuration information to the UE through the second PDU session.

[0486] Step 1112: The UE sends QoE information to the NWDAF through the first PDU session.

[0487] It is understood that this example illustrates that the first PDU session and the second PDU session are different. Optionally, the first PDU session and the second PDU session can be the same session, the first message and the fifth message are the same message, and the first indication information and the second indication information are the same indication information. In this case, in step 1101, only one message requesting the establishment of a PDU session for transmitting QoE-related data needs to be sent. SMF refers to establishing a PDU session. An established PDU session can be used to transmit the first configuration information and QoE information.

[0488] Based on the above example, the first configuration information and QoE information can be transmitted through the PDU session, which can reduce the latency of QoE information transmission, improve the efficiency of QoE information transmission, and ensure the transmission of QoE information.

[0489] Figure 12 This example illustrates another communication method where QoE configuration information and QoE information reporting can be implemented using an UP (Up-to-Up) approach, with transmission between the UE and NWDAF (Non-WDAF) via the user plane. QoE information is carried using a dedicated PDU session to ensure real-time QoE information transmission. Figure 11 The difference is that in this example, the SMF sends the UE-supported QoE reporting capabilities to the NWDAF. For example, the process in this example may include:

[0490] Step 1201: The PCF sends a first message and a fifth message to the UE. The first message includes a first indication information, which is used to indicate the establishment of a PDU session for transmitting QoE information. The fifth message includes a second indication information, which is used to indicate the establishment of a PDU session for transmitting first configuration information.

[0491] For details, please refer to the aforementioned descriptions, which will not be repeated here.

[0492] Step 1201 is an optional step.

[0493] Step 1202: NWDAF sends a second subscription message to SMF, which is used to indicate that NWDAF should be notified after a PDU session is established.

[0494] Step 1202 is optional.

[0495] For details, please refer to the above description, which will not be repeated here.

[0496] Step 1203: The UE sends a second message to the SMF, which contains the QoE reporting capabilities supported by the UE.

[0497] The second message can be a PDU session establishment request message sent by the UE.

[0498] The specific implementation process of the UE sending the second message can be found in the aforementioned document. Figure 4 The relevant descriptions involved in the illustrated embodiments will not be repeated here.

[0499] It should be understood that messages or information sent by the UE to the SMF can be transmitted through the RAN, which will not be described in detail in this application.

[0500] Step 1204: The SMF sends a fourth message to the NWDAF, which includes the QoE reporting capability supported by the UE.

[0501] The specific method by which SMF sends the fourth message to NWDAF can be found in the relevant descriptions of methods b1 and b2 mentioned above, and will not be repeated here.

[0502] It should be understood that when the SMF sends the fourth message to the NWDAF in accordance with method b2, the aforementioned step 1202 exists.

[0503] Step 1205: NWDAF determines the first configuration information based on the QoE reporting capability supported by the UE.

[0504] The first configuration information can be found in the aforementioned document. Figure 4 The relevant descriptions involved in the illustrated embodiments will not be repeated here.

[0505] Step 1206: NWDAF sends a message to AMF requesting the UE to report QoE information.

[0506] Step 1207: The AMF sends a message to the UE requesting the UE to report QoE information.

[0507] Step 1208: The UE sends a first PDU session request and a second PDU session establishment request to the SMF. The first PDU session request is used to request the establishment of a PDU session for transmitting QoE information (i.e., the first PDU session). The second PDU session establishment request can be used to request the establishment of a PDU session for transmitting first configuration information (i.e., the second PDU session).

[0508] Optionally, the UE sends a first PDU session establishment request to the SMF according to the first indication information, and sends a second PDU session establishment request to the SMF according to the second indication information.

[0509] Optionally, when a service is in progress, the UE collects QoE information based on the first configuration information and triggers the establishment of the first PDU session, i.e., executes step 1208.

[0510] Step 1209: SMF establishes the first PDU session and the second PDU session.

[0511] Step 1210: The UE sends a third message to the NWDAF, which is used to establish a secure connection.

[0512] Step 1210 is an optional step.

[0513] Step 1211: NWDAF sends the first configuration information to the UE through the second PDU session.

[0514] Step 1212: The UE sends QoE information to the NWDAF through the first PDU session.

[0515] It is understood that this example illustrates that the first PDU session and the second PDU session are different. Optionally, the first PDU session and the second PDU session can be the same session, the first message and the fifth message are the same message, and the first indication information and the second indication information are the same indication information. In this case, in step 1201, only one message requesting the establishment of a PDU session for transmitting QoE-related data needs to be sent. SMF refers to establishing a PDU session. An established PDU session can be used to transmit the first configuration information and QoE information.

[0516] Based on the above example, the first configuration information and QoE information can be transmitted through the PDU session, which can reduce the latency of QoE information transmission, improve the efficiency of QoE information transmission, and ensure the transmission of QoE information.

[0517] Based on the above embodiments, this application also provides a communication device, see below. Figure 13As shown, the communication device 1300 may include a transceiver unit 1301 and a processing unit 1302. The transceiver unit 1301 is used for communication by the communication device 1300, such as receiving or sending information (signals or data). The processing unit 1302 is used for controlling and managing the operation of the communication device 1300. The processing unit 1302 can also control the steps performed by the transceiver unit 1301.

[0518] For example, the communication device 1300 may specifically be a terminal device, a processor, chip, chip system, component, module, or functional module as described in the above embodiments. Alternatively, the communication device 1300 may specifically be a network data analysis function network element, a processor, chip, chip system, component, module, or functional module as described in the above embodiments. Alternatively, the communication device 1300 may specifically be a session management function network element or an access and mobility management function network element, a processor, chip, chip system, component, module, or functional module as described in the above embodiments. Alternatively, the communication device 1300 may specifically be a policy control function network element, a processor, chip, chip system, component, module, or functional module as described in the above embodiments.

[0519] In one embodiment, when the communication device 1300 is used to implement the functions of a terminal device, the transceiver unit 1301 can be used to receive first configuration information via first NAS signaling, the first configuration information being used to instruct the terminal device to collect or report Quality of Experience (QoE) information; the processing unit 1302 can be used to collect or the transceiver unit 1301 can also be used to report QoE information according to the first configuration information. The processing unit 1302 can also be used to control the operation of the transceiver unit 1301.

[0520] In one alternative implementation, the first NAS signaling includes a first container, the first container including the first configuration information.

[0521] For example, the first NAS signaling is a registration acceptance message, a downlink transmission message, or a session acceptance message.

[0522] In some examples, the transceiver unit 1301 can specifically be used to send the QoE information via a second NAS signaling.

[0523] For example, the second NAS signaling is a registration request message, an uplink transmission message, or a session request message.

[0524] Optionally, the second NAS signaling includes a second container, which includes the QoE information.

[0525] In some other examples, the transceiver unit 1301 may specifically be used to send the QoE information through the user plane.

[0526] In an optional implementation, the processing unit 1302 can also be used to establish a Protocol Data Unit (PDU) session for transmitting QoE information; when the transceiver unit 1301 sends the QoE information through the user plane, it can be used to send the QoE information through the PDU session.

[0527] In an optional implementation, the processing unit 1302 may also be used to receive a first message, the first message including first indication information, the first indication information being used to indicate the establishment of a Protocol Data Unit (PDU) session for transmitting QoE information.

[0528] For example, the first message includes a routing policy rule, which includes the first indication information.

[0529] Optionally, the routing policy rule includes a traffic descriptor, and the traffic descriptor includes the first indication information.

[0530] In an alternative implementation, the processing unit 1302 may also be used to send a third message, which is used to request the establishment of a secure connection.

[0531] In some embodiments, the first configuration information is determined based on the QoE reporting capability supported by the terminal device.

[0532] In an optional implementation, the processing unit 1302 may also be used to send a second message, the second message containing the QoE reporting capability supported by the terminal device.

[0533] Optionally, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity.

[0534] The second message can be a registration request message or a session request message.

[0535] In another embodiment, when the communication device 1300 is used to implement the function of a network data analysis function element, the transceiver unit 1301 can be used to send first configuration information through a first transmission message, the first configuration information being used to instruct the terminal device to collect or report Quality of Experience (QoE) information; and to receive QoE information. The processing unit 1302 can be used to control the operation of the transceiver unit 1301.

[0536] In one optional implementation, when receiving QoE information, the transceiver unit 1301 can be used to: receive the QoE information via a second transmission message.

[0537] In another alternative implementation, when receiving QoE information, the transceiver unit 1301 can be used to: receive the QoE information through the user plane.

[0538] Optionally, when receiving the QoE information through the user plane, the transceiver unit 1301 can be used to: receive the QoE information through a Protocol Data Unit (PDU) session for transmitting QoE information.

[0539] In some embodiments, the transceiver unit 1301 can also be used to receive a third message, which is used to request the establishment of a secure connection.

[0540] Optionally, the first configuration information is determined based on the QoE reporting capability supported by the terminal device.

[0541] In some embodiments, the transceiver unit 1301 can also be used to receive a fourth message, the fourth message containing the QoE reporting capability supported by the terminal device.

[0542] For example, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity.

[0543] Optionally, the fourth message is a subscription notification message or a QoE service message.

[0544] In another embodiment, when the communication device 1300 is used to implement the functions of a session management function network element or an access and mobility management function network element, the transceiver unit 1301 can be used to receive first configuration information through a first transmission message, wherein the first configuration information is used to instruct the terminal device to collect or report quality of experience (QoE) information; and to send the first configuration information through a first NAS signaling. The processing unit 1302 can be used to control the operation of the transceiver unit 1301.

[0545] Optionally, when the communication device is an access and mobility management function network element, the first NAS signaling includes a first container, and the first container includes the first configuration information.

[0546] For example, the first NAS signaling is a registration acceptance message, a downlink transmission message, or a session acceptance message.

[0547] In an optional implementation, the transceiver unit 1301 can also be used to receive the QoE information via a second NAS signaling and to send the QoE information via a second transmission message.

[0548] Optionally, the second NAS signaling is a registration request message, an uplink transmission message, or a session request message.

[0549] Optionally, when the communication device is an access and mobility management function network element, the second NAS signaling includes a second container, which includes the QoE information.

[0550] In an optional implementation, when the communication device is a session management function network element, the transceiver unit 1301 can also be used to receive a first PDU session establishment request, which is used to request the establishment of a PDU session for transmitting QoS information.

[0551] In one example, the first configuration information is determined based on the QoE reporting capability supported by the terminal device.

[0552] Optionally, the transceiver unit 1301 can also be used to receive a second message, the second message containing the QoE reporting capability supported by the terminal device.

[0553] For example, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity.

[0554] The second message can be a registration request message or a session request message.

[0555] Optionally, the transceiver unit 1301 can also be used to send a fourth message, which includes the QoE reporting capability supported by the terminal device.

[0556] For example, the fourth message is a subscription notification message or a QoE service message.

[0557] In another embodiment, when the communication device 1300 is used to implement the functions of the terminal device, the transceiver unit 1301 can be used to receive first configuration information, which is used to instruct the terminal device to collect or report QoE information; and send QoE information through second NAS signaling.

[0558] Optionally, the second NAS signaling includes a second container, which includes the QoE information.

[0559] For example, the second NAS signaling is a registration request message or an uplink transmission message.

[0560] In one optional implementation, when receiving the first configuration information, the transceiver unit 1301 can be used to receive the first configuration information via first NAS signaling.

[0561] Optionally, the first NAS signaling includes a first container, and the first container includes the first configuration information.

[0562] In another alternative implementation, when receiving the first configuration information, the transceiver unit 1301 can be used to receive the first configuration information through the user plane.

[0563] Optionally, the processing unit 1302 can also be used to establish a Protocol Data Unit (PDU) session for transmitting first configuration information; the transceiver unit 1301 can specifically be used to receive the first configuration information through the PDU session.

[0564] In one example, the transceiver unit 1301 can also be used to receive a fifth message, the fifth message including second indication information, the second indication information being used to indicate the establishment of a PDU session for transmitting first configuration information.

[0565] In some embodiments, the first configuration information is determined based on the QoE reporting capability supported by the terminal device.

[0566] Optionally, the transceiver unit 1301 can also be used to send a second message, the second message containing the QoE reporting capability supported by the terminal device.

[0567] For example, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity.

[0568] In another embodiment, when the communication device 1300 is used to implement the function of a network data analysis function element, the transceiver unit 1301 can be used to send first configuration information, which instructs the terminal device to collect or report QoE information; and to receive QoE information through a second transmission message. The processing unit 1302 can be used to control the operation of the transceiver unit 1301.

[0569] In one optional implementation, when sending the first configuration information, the transceiver unit 1301 can be used to: send the first configuration information via a first transmission message.

[0570] In another optional implementation, when sending the first configuration information, the transceiver unit 1301 can be used to: send the first configuration information through the user plane.

[0571] For example, when the transceiver unit 1301 sends the first configuration information through the user plane, it can be used to: send the first configuration information through a PDU session used to transmit the first configuration information.

[0572] Optionally, the first configuration information is determined based on the QoE reporting capability supported by the terminal device.

[0573] In one possible approach, the transceiver unit 1301 can also be used to receive a fourth message, the fourth message containing the QoE reporting capability supported by the terminal device.

[0574] For example, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity.

[0575] In another embodiment, when the communication device 1300 is used to implement the functions of a session management function network element or an access and mobility management function network element, the transceiver unit 1301 can be used to receive QoE information through a second NAS signaling, wherein the QoE information is collected or reported according to a first configuration information; and to send the QoE information through a second transmission message. The processing unit 1302 can be used to control the operation of the transceiver unit 1301.

[0576] Optionally, when the communication device is an access and mobility management function network element, the second NAS signaling includes a second container, which includes the QoE information.

[0577] In one example, the transceiver unit 1301 can also be used to: receive the first configuration information via a first transmission message; and send the first configuration information via a first NAS signaling.

[0578] Optionally, when the communication device is an access and mobility management function network element, the first NAS signaling includes a first container, and the first container includes the first configuration information.

[0579] In one possible approach, when the communication device is a session management function network element, the transceiver unit 1301 can also be used to: receive a second PDU session establishment request, wherein the second PDU session request is used to request the establishment of a PDU session for transmitting first configuration information.

[0580] In some embodiments, the first configuration information is determined based on the QoE reporting capability supported by the terminal device.

[0581] Optionally, the transceiver unit 1301 can also be used to receive a second message, the second message containing the QoE reporting capability supported by the terminal device.

[0582] For example, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity.

[0583] The second message can be a registration request message or a session request message.

[0584] Optionally, the transceiver unit 1301 can also be used to send a fourth message, which includes the QoE reporting capability supported by the terminal device.

[0585] For example, the fourth message can be a subscription notification message or a QoE service message.

[0586] In another embodiment, when the communication device 1300 is used to implement the functions of a terminal device, the transceiver unit 1301 can be used to receive first configuration information, which is used to indicate the collection or reporting of QoE information; the processing unit 1302 can be used to establish a Protocol Data Unit (PDU) session for transmitting QoE information; the transceiver unit 1301 can also be used to send the QoE information through the PDU session.

[0587] Optionally, the transceiver unit 1301 can also be used to receive a first message, the first message including first indication information, the first indication information being used to indicate the establishment of a Protocol Data Unit (PDU) session for transmitting QoE information.

[0588] For example, the first message includes a routing policy rule, which includes the first indication information.

[0589] For example, the routing policy rule includes a traffic descriptor, and the traffic descriptor includes the first indication information.

[0590] Optionally, the routing policy rule further includes a routing descriptor, which includes attributes for establishing the PDU session.

[0591] In one example, when receiving the first configuration information, the transceiver unit 1301 can be used to: receive the first configuration information via first NAS signaling.

[0592] Optionally, the first NAS signaling includes a first container, and the first container includes the first configuration information.

[0593] Optionally, the first NAS signaling is a registration accept message, a downlink transmission message, or a session accept message.

[0594] In another example, when receiving the first configuration information, the transceiver unit 1301 can be used to: receive the first configuration information through the user plane.

[0595] In one possible approach, the processing unit 1302 may also be used to establish a Protocol Data Unit (PDU) session for transmitting first configuration information; the transceiver unit 1301 may also be used to receive the first configuration information through the PDU session for transmitting the first configuration information.

[0596] Optionally, the transceiver unit 1301 can also be used to receive a fifth message, the fifth message including second indication information, the second indication information being used to indicate the establishment of a PDU session for transmitting first configuration information.

[0597] In some implementations, the first configuration information is determined based on the QoE reporting capability supported by the terminal device.

[0598] Optionally, the transceiver unit 1301 can also be used to send a second message, the second message containing the QoE reporting capability supported by the terminal device.

[0599] For example, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity.

[0600] Optionally, the transceiver unit 1301 can also be used to receive the first configuration information by subscription.

[0601] In another embodiment, when the communication device 1300 is used to implement the function of a network data analysis function element, the transceiver unit 1301 can be used to send first configuration information, which is used to instruct the collection or reporting of QoE information; and to receive QoE information through a Protocol Data Unit (PDU) session for transmitting QoE information. The processing unit 1302 can be used to control the operation of the transceiver unit 1301.

[0602] In some embodiments, when sending the first configuration information, the transceiver unit 1301 may be used to: send the first configuration information via a first transmission message.

[0603] In other embodiments, when sending the first configuration information, the transceiver unit 1301 may be used to send the first configuration information through the user plane.

[0604] Optionally, when the transceiver unit 1301 sends the first configuration information through the user plane, it can be used to send the first configuration information through a PDU session used for transmitting the first configuration information.

[0605] In some possible ways, the first configuration information is determined based on the QoE reporting capability supported by the terminal device.

[0606] Optionally, the transceiver unit 1301 can also be used to receive a fourth message, which includes the QoE reporting capability supported by the terminal device.

[0607] For example, the QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity.

[0608] In another embodiment, when the communication device 1300 is used to implement the function of a policy control function network element, the transceiver unit 1301 can be used to send a first message, the first message including first indication information, the first indication information being used to indicate the establishment of a Protocol Data Unit (PDU) session for transmitting QoE information. The processing unit 1302 can be used to control the operation of the transceiver unit 1301.

[0609] Optionally, the first message includes a routing policy rule, and the routing policy rule includes the first indication information.

[0610] For example, the routing policy rule includes a traffic descriptor, and the traffic descriptor includes the first indication information.

[0611] In some embodiments, the transceiver unit 1301 can also be used to send a fifth message, the fifth message including second indication information, the second indication information being used to indicate the establishment of a Protocol Data Unit (PDU) session for transmitting first configuration information.

[0612] In another embodiment, when the communication device 1300 is used to implement the function of a policy control function network element, the transceiver unit 1301 can be used to send a fifth message, the fifth message including second indication information, the second indication information being used to indicate the establishment of a Protocol Data Unit (PDU) session for transmitting first configuration information. The processing unit 1302 can be used to control the operation of the transceiver unit 1301.

[0613] Optionally, the fifth message includes a routing policy rule, and the routing policy rule includes the fifth indication information.

[0614] For example, the routing policy rule includes a traffic descriptor, and the traffic descriptor includes the fifth indication information.

[0615] In some embodiments, the transceiver unit 1301 can also be used to send a first message, the first message including first indication information, the first indication information being used to indicate the establishment of a Protocol Data Unit (PDU) session for transmitting QoE information.

[0616] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The functional units in the embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0617] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0618] Based on the above embodiments, this application also provides a communication device, see below. Figure 14 As shown, the communication device 1400 may include one or more processors 1402. Optionally, the communication device 1400 may also include one or more transceivers 1401. Optionally, the communication device 1400 may also include at least one memory 1403. The memory 1403 may be located inside or outside the communication device 1400. The processor 1402 can control the transceiver 1401 to receive and send information, messages, or data.

[0619] Specifically, the processor 1402 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor 1402 may further include a hardware chip. This hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0620] The transceiver 1401, processor 1402, and memory 1403 are interconnected. Optionally, the transceiver 1401, processor 1402, and memory 1403 are interconnected via a bus 1404; the bus 1404 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 14 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0621] In one optional embodiment, the memory 1403 is used to store programs, etc. Specifically, the program may include program code, which includes computer operation instructions. The memory 1403 may include RAM, and may also include non-volatile memory, such as one or more disk storage devices. The processor 1402 executes the application program stored in the memory 1403 to achieve the above-mentioned functions, thereby realizing the functions of the communication device 1400.

[0622] For example, the communication device 1400 can specifically implement the functions of the terminal device, network data analysis function network element, session management function network element, access and mobility management function network element, or policy control function network element in the above embodiments.

[0623] In one embodiment, when the communication device 1400 implements the functions of the terminal device in the aforementioned method embodiment, the transceiver 1401 can perform the send and receive operations executed by the terminal device in the aforementioned method embodiment; the processor 1402 can perform other operations besides the send and receive operations executed by the first terminal device in the aforementioned method embodiment. Specific details can be found in the relevant descriptions in the above method embodiments, and will not be elaborated upon here.

[0624] In another embodiment, when the communication device 1400 implements the functions of the terminal device in the aforementioned method embodiments, the processor 1402 can implement the operations performed by the terminal device in the aforementioned method embodiments. For specific details, please refer to the relevant descriptions in the above method embodiments, which will not be elaborated upon here.

[0625] In another embodiment, when the communication device 1400 implements the function of the network data analysis function network element in the aforementioned method embodiment, the transceiver 1401 can implement the transmit and receive operations performed by the network data analysis function network element in the aforementioned method embodiment; the processor 1402 can implement other operations besides the transmit and receive operations performed by the network data analysis function network element in the aforementioned method embodiment. Specific details can be found in the relevant descriptions in the above method embodiments, and will not be elaborated upon here.

[0626] In another embodiment, when the communication device 1400 implements the function of the network data analysis function network element in the aforementioned method embodiment, the processor 1402 can implement the operations performed by the network data analysis function network element in the aforementioned method embodiment. Specific details can be found in the relevant descriptions in the above method embodiments, and will not be elaborated upon here.

[0627] In another embodiment, when the communication device 1400 implements the function of the session management function network element in the aforementioned method embodiment, the transceiver 1401 can implement the transmit / receive operations performed by the session management function network element in the aforementioned method embodiment; the processor 1402 can implement other operations besides the transmit / receive operations performed by the session management function network element in the aforementioned method embodiment. Specific details can be found in the relevant descriptions in the above method embodiments, and will not be elaborated upon here.

[0628] In yet another embodiment, when the communication device 1400 implements the function of the session management function network element in the aforementioned method embodiments, the processor 1402 can implement the operations performed by the session management function network element in the aforementioned method embodiments. Specific details can be found in the relevant descriptions in the above method embodiments, and will not be elaborated upon here.

[0629] In another embodiment, when the communication device 1400 implements the functions of the access and mobility management function network element in the aforementioned method embodiments, the transceiver 1401 can implement the transmit and receive operations performed by the access and mobility management function network element in the aforementioned method embodiments; the processor 1402 can implement other operations performed by the access and mobility management function network element in the aforementioned method embodiments besides the transmit and receive operations. Specific details can be found in the relevant descriptions in the above method embodiments, and will not be described in detail here.

[0630] In yet another embodiment, when the communication device 1400 implements the functions of the access and mobility management function network element in the aforementioned method embodiments, the processor 1402 can implement the operations performed by the access and mobility management function network element in the aforementioned method embodiments. Specific details can be found in the relevant descriptions in the above method embodiments, and will not be elaborated upon here.

[0631] In another embodiment, when the communication device 1400 implements the function of the policy control function network element in the aforementioned method embodiments, the transceiver 1401 can implement the transmit / receive operations performed by the policy control function network element in the aforementioned method embodiments; the processor 1402 can implement other operations besides the transmit / receive operations performed by the policy control function network element in the aforementioned method embodiments. Specific details can be found in the relevant descriptions in the above method embodiments, and will not be elaborated upon here.

[0632] In yet another embodiment, when the communication device 1400 implements the function of the policy control function network element in the aforementioned method embodiments, the processor 1402 can implement the operations performed by the policy control function network element in the aforementioned method embodiments. Specific details can be found in the relevant descriptions in the above method embodiments, and will not be elaborated upon here.

[0633] Based on the above embodiments, this application provides a communication system that may include the terminal devices and network data analysis function network elements involved in the above embodiments.

[0634] This application provides a communication system that may include the terminal equipment, network data analysis function network element, session management function network element, and access and mobility management function network element involved in the above embodiments.

[0635] This application provides a communication system that may include the terminal equipment, network data analysis function network element, session management function network element, access and mobility management function network element, and policy control function network element involved in the above embodiments.

[0636] This application also provides a computer-readable storage medium for storing computer programs or instructions. When the computer programs or instructions are executed by a computer, the computer can implement the communication methods provided in the above-described method embodiments.

[0637] This application also provides a computer program product for storing computer programs or instructions. When the computer program or instructions are executed by a computer, the computer can implement the communication method provided in the above method embodiments.

[0638] This application also provides a chip or chip system, including logic circuitry, which is used to execute the communication method provided in the above-described method embodiments.

[0639] This application also provides a chip or chip system, including one or more processors, wherein the one or more processors are coupled to at least one memory, for calling a program in the memory to enable the chip or chip system to implement the communication method provided in the above method embodiments.

[0640] This application also provides a chip or chip system coupled to at least one memory, which is used to implement the communication method provided in the above method embodiments.

[0641] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0642] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0643] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0644] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0645] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method, characterized in that, include: The first configuration information is received via the first NAS signaling, and the first configuration information is used to instruct the terminal device to collect or report Quality of Experience (QoE) information. Collect or report QoE information based on the first configuration information.

2. The method as described in claim 1, characterized in that, The first NAS signaling includes a first container, and the first container includes the first configuration information.

3. The method as described in claim 1, characterized in that, The method further includes: The QoE information is sent via a second NAS signaling.

4. The method as described in claim 3, characterized in that, The second NAS signaling includes a second container, which includes the QoE information.

5. The method as described in claim 1, characterized in that, The method further includes: The QoE information is sent through the user plane.

6. The method as described in claim 5, characterized in that, Sending the QoE information via the user plane includes: Establish a Protocol Data Unit (PDU) session for transmitting QoE information; The QoE information is sent through the PDU session.

7. The method as described in claim 6, characterized in that, The method further includes: Receive a first message, the first message including first indication information, the first indication information being used to indicate the establishment of a Protocol Data Unit (PDU) session for transmitting QoE information.

8. The method according to any one of claims 5 to 7, characterized in that, The method further includes: A third message is sent, which is used to request the establishment of a secure connection.

9. The method according to any one of claims 1 to 8, characterized in that, The first configuration information is determined based on the QoE reporting capability supported by the terminal device.

10. The method as described in claim 9, characterized in that, The method further includes: Send a second message, which includes the QoE reporting capability supported by the terminal device.

11. The method as described in claim 9 or 10, characterized in that, The QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity.

12. A communication method, characterized in that, include: First configuration information is sent through a first transmission message, wherein the first configuration information is used to instruct the terminal device to collect or report Quality of Experience (QoE) information. Receive QoE information.

13. The method as described in claim 12, characterized in that, Receive QoE information, including: The QoE information is received via the second transmission message.

14. The method as described in claim 12, characterized in that, Receive QoE information, including: The QoE information is received through the user plane.

15. The method as described in claim 14, characterized in that, Receiving the QoE information through the user plane includes: The QoE information is received through a Protocol Data Unit (PDU) session used for transmitting QoE information.

16. The method as described in claim 14 or 15, characterized in that, The method further includes: A third message is received, which is used to request the establishment of a secure connection.

17. The method according to any one of claims 12-16, characterized in that, The first configuration information is determined based on the QoE reporting capability supported by the terminal device.

18. The method as described in claim 17, characterized in that, The method further includes: Receive a fourth message, the fourth message containing the QoE reporting capability supported by the terminal device.

19. The method as described in claim 17 or 18, characterized in that, The QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity.

20. A communication method, characterized in that, include: The first configuration information is received through the first transmission message, and the first configuration information is used to instruct the terminal device to collect or report Quality of Experience (QoE) information. The first configuration information is sent via the first NAS signaling.

21. The method as described in claim 20, characterized in that, The first NAS signaling includes a first container, and the first container includes the first configuration information.

22. The method as described in claim 20 or 21, characterized in that, The method further includes: The QoE information is received via the second NAS signaling; The QoE information is sent via a second transmission message.

23. The method as described in claim 22, characterized in that, The second NAS signaling includes a second container, which includes the QoE information.

24. The method as described in claim 20 or 22, characterized in that, The method further includes: Receive a first PDU session establishment request, which is used to request the establishment of a PDU session for transmitting QoS information.

25. The method according to any one of claims 20-24, characterized in that, The first configuration information is determined based on the QoE reporting capability supported by the terminal device.

26. The method as described in claim 25, characterized in that, The method further includes: Receive a second message, the second message containing the QoE reporting capability supported by the terminal device.

27. The method as described in claim 25 or 26, characterized in that, The QoE reporting capability includes one or more of the following: service granularity, application granularity, data network name granularity, or slice granularity.

28. The method according to any one of claims 25-27, characterized in that, The method further includes: Send a fourth message, which includes the QoE reporting capability supported by the terminal device.

29. A communication device, characterized in that, It includes a module or unit for performing the method according to any one of claims 1-11, or includes a module or unit for performing the method according to any one of claims 12-19, or includes a module or unit for performing the method according to any one of claims 20-28.

30. A communication device, characterized in that, The device includes a processor configured to cause the communication device to perform the method as claimed in any one of claims 1-11, or the method as claimed in any one of claims 12-19, or the method as claimed in any one of claims 20-28.