CN113556754A

CN113556754A - Service experience measurement collection method and device

Info

Publication number: CN113556754A
Application number: CN202010328494.1A
Authority: CN
Inventors: 李丽丝; 麻晓宁; 许丽香; 王弘
Original assignee: Samsung Electronics Co Ltd
Current assignee: Beijing Samsung Telecom R&D Center; Samsung Electronics Co Ltd
Priority date: 2020-04-23
Filing date: 2020-04-23
Publication date: 2021-10-26
Also published as: KR20210131268A; WO2021215886A1

Abstract

The present disclosure provides a method for collecting QMC through service experience measurement, which includes the following steps: transmitting, by a node, first information to one or more UEs; wherein the first information: generated by the node, or received by the node from other nodes.

Description

Service experience measurement collection method and device

Technical Field

The present application relates to wireless communication technologies, and in particular, to a method and device for collecting service experience measurements.

Background

In order to meet the increasing demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. Accordingly, the 5G or quasi-5G communication system is also referred to as a "super 4G network" or a "post-LTE system".

Wireless communication is one of the most successful innovations in modern history. Recently, the number of subscribers to wireless communication services has exceeded 50 billion and is continuing to grow rapidly. Due to the increasing popularity of smart phones and other mobile data devices (e.g., tablet computers, notebook computers, netbooks, e-book readers, and machine type devices) among consumers and businesses, the demand for wireless data services is growing rapidly. To meet the high-speed growth of mobile data services and support new applications and deployments, it is important to improve radio interface efficiency and coverage.

Disclosure of Invention

According to an aspect of the present disclosure, there is provided a traffic experience measurement collection QMC method, comprising the steps of: transmitting, by a node, first information to one or more UEs; wherein the first information: generated by the node, or received by the node from other nodes.

In one implementation, the first information is QMC configuration information.

In one implementation, the QMC configuration information is generated by the node based on second information received from other nodes or based on a reason of the node itself.

In one implementation, the second information includes a request for QMC or a PDU session modification or deletion.

In one implementation, the QMC configuration information comprises one or more QMC references, the different QMC references identifying different QMC tasks, each QMC task comprising one or more application references identifying a traffic type.

In one implementation, the QMC configuration information is one of the following types: activating QMC configuration information, deactivating QMC configuration information, or modifying QMC configuration information.

In one implementation, the activating QMC configuration information comprises configuration condition information, wherein the configuration condition information comprises one or more of geographical location information, network slice information, mobile speed information, and/or radio coverage environment information.

In one implementation, the node selects the one or more UEs based on the configuration condition information.

In one implementation, the activating QMC configuration information includes a reporting configuration, and the reporting configuration includes one of a session end report, a periodic report, or an event trigger-based report.

In one implementation, the triggering event based on reporting of the event trigger includes one or more of a serving cell change, a radio environment change, or a sudden degradation of user traffic experience.

In one implementation, an embodiment according to the present disclosure further includes: receiving a QMC report from at least one of the one or more UEs. Wherein the QMC report includes one or more of serving cell information, network slice information, QoS information, or DRB information.

In one implementation, an embodiment according to the present disclosure further includes: the node obtains the required service experience QoE information based on the QMC report, or deduces other QoE information based on the QoE information, or the node sends the QMC report, the QoE information or the other QoE information to other one or more nodes.

In one implementation, the activating QMC configuration information or modifying QMC configuration information includes a QMC reference requiring deactivation and/or an application reference indicating a measurement of a specific service in the QMC task requiring deactivation and/or the QMC task.

In one implementation, the modifying the QMC configuration further includes one or more of a reporting period, a buffering indication, or a buffering limitation condition.

In one implementation, the first information includes a range indication.

In one implementation, the first message further includes QMC reporting buffer information.

In one implementation, the QMC reports the buffer information indicating the buffer indication status or whether the reporting period is configured.

In one implementation, the first information is received by the node from other nodes, and the range indication is information indicating a result of checking configuration conditions by the other nodes in response to handover-related information including configuration condition information sent by the node.

According to still another aspect of the present disclosure, there is provided a traffic experience measurement collection QMC method, comprising the steps of: receiving, by a UE, a first message from a node; determining, by the UE, information related to the QMC based on the received first message.

In one implementation, the first message includes QMC configuration information that includes one or more QMC references, where different QMC references identify different QMC tasks, each QMC task including one or more application references that identify a traffic type.

In one implementation, wherein in response to the QMC configuration information being an active QMC configuration information, the determining, by the UE, information related to QMC based on the received first message comprises: and the UE determines whether to perform QoE measurement or not based on the configuration condition information included in the QMC configuration information, performs QoE measurement if the determination result is positive, and sends a QMC report obtained by measurement to the node.

In an implementation manner, the QMC configuration information further includes a reporting configuration, and the UE performs QMC reporting based on the reporting configuration.

In one implementation, wherein in response to the QMC configuration information being a deactivated QMC configuration information, the determining, by the UE, information related to QMC based on the received first message comprises: the UE determines to deactivate a corresponding QMC task and/or a measurement of a specific traffic in a QMC task based on a reference identifier included in the deactivation QMC configuration information, wherein the reference identifier includes a QMC reference and/or an application reference.

In one implementation, wherein in response to the QMC configuration information being a modified QMC configuration information, the determining, by the UE, information related to QMC based on the received first message comprises: depending on whether the modified QMC configuration information indicates to deactivate one or more of the plurality of QMC tasks or to deactivate one or more traffic measurements in the QMC tasks or to modify the reporting occasion for a QMC report, the UE deactivates the indicated QMC task or a measurement of a specific traffic in the QMC task or controls the time of reporting of a QMC report according to the content in the modified QMC configuration information.

In one implementation, wherein the first message is information regarding PDU session modification or deletion, the determining, by the UE, the information related to QMC based on the received first message comprises: the UE determines whether to start or stop QoE measurement based on information about PDU session modification or deletion.

In one implementation, the determining, by the UE, information related to QMC based on the received first message includes: in response to receiving the range indication, determining, by the UE, whether to perform QoE measurement based on the range indication, and if the determination is yes, starting the measurement and generating a QMC report including the assistance information; in response to receiving the reporting buffer information, performing, by the UE, based on the reporting buffer information, one of: buffering the QMC report, sending the QMC report to the node through an application layer measurement report message.

According to still another aspect of the present disclosure, there is provided a traffic experience measurement collection QMC method, including: receiving, by the first node, a first request message from the second node; and sending, by the first node, a response message related to QMC to the second node.

In one implementation, the first request message is a handover request message, and the response message is a handover request acknowledgement message; or, the first request message is a handover requirement message, and the response message is a handover command message, where the handover request message or the handover requirement message includes application layer measurement configuration information, and the application layer measurement configuration information includes at least one of the following: the method comprises the steps of QMC reference, application reference, QMC reporting cache information and configuration condition information, wherein the configuration condition information comprises one or more of network slice information, moving speed information and wireless coverage environment information, the reporting cache information indicates the state of cache indication or whether a reporting period is configured, the switching request confirmation message or the switching command message comprises a switching information container, and the switching information container comprises range indication information indicating the checking result of the configuration condition information.

In one implementation, the handover request acknowledge message or the handover command message further includes a buffering indication or a reporting period.

In one implementation, an embodiment according to the present disclosure further includes: wherein the first request message is a get UE context request message; the response message is an acquire UE context feedback message, where the acquire UE context feedback message includes application layer measurement configuration information, the application layer measurement configuration information includes at least one of a QMC reference, an application reference, QMC reporting buffer information, and configuration condition information, and the configuration condition information includes one or more of network slice information, mobility speed information, and radio coverage environment information.

In one implementation, an embodiment according to the present disclosure further includes: wherein the first request message is a message for requesting a QMC report or QoE information, and the response message is a message for feeding back the requested QMC report or QoE information; wherein the message for requesting the QMC report or the QoE information and the message for feeding back the requested QMC report or QoE information include one or more of cell information, network slice information, QoS information, or DRB information. According to yet another aspect of the present disclosure, there is provided a QMC apparatus comprising a processor, a memory, and a transceiver unit configured to receive and transmit wireless data, the memory configured to store data, the processor configured to perform a QMC method according to various embodiments of the present disclosure.

The present disclosure provides improved traffic experience measurement collection (QMC) methods and apparatus. According to the method or the equipment disclosed by the invention, an operator can be helped to collect user service experience information (QoE) on different network slices, under different mobile scenes and/or under different wireless environments, and the user service experience information can be more quickly and completely applied to network maintenance and optimization, so that the user service experience can be better ensured and improved, the user loyalty can be improved, and the operator income can be increased.

Drawings

FIG. 1 illustrates an exemplary system architecture for System Architecture Evolution (SAE);

fig. 2 illustrates an exemplary system architecture in accordance with various embodiments of the present disclosure;

FIG. 3 shows a 5G architecture diagram in accordance with various embodiments of the present disclosure;

FIG. 4 shows a schematic diagram of a management-based QMC;

fig. 5 illustrates an example of a QMC method according to an embodiment of the present disclosure;

fig. 6 illustrates an example of a QMC method according to yet another embodiment of the present disclosure;

fig. 7 illustrates an example of a QMC method according to yet another embodiment of the present disclosure;

fig. 8 illustrates an example of a QMC method according to yet another embodiment of the present disclosure;

fig. 9 illustrates an example of a QMC method according to yet another embodiment of the present disclosure;

fig. 10 illustrates an example of a QMC method according to yet another embodiment of the present disclosure;

fig. 11 illustrates an example of a QMC method according to yet another embodiment of the present disclosure;

fig. 12 illustrates an example of a QMC method according to yet another embodiment of the present disclosure;

fig. 13 illustrates an example of a QMC method according to yet another embodiment of the present disclosure;

fig. 14 illustrates an example of a QMC method according to yet another embodiment of the present disclosure;

fig. 15 shows a simplified block diagram of an example configuration of hardware components of a QMC device according to various embodiments of the present disclosure.

Detailed Description

5G refers to a fifth generation mobile communication technology. Unlike the previous four generations of communication technologies, 5G is not a single wireless communication technology, but a fusion of existing wireless communication technologies. Currently, the peak rate of LTE can reach 100Mbps, while the peak rate of 5G will reach 10Gbps, which is 100 times higher than that of 4G. The existing 4G network has limited processing spontaneous capability and cannot support partial services such as high-definition video, high-quality voice, augmented reality, virtual reality and the like. The 5G will introduce more advanced technology and meet the demand of mobile traffic increase through higher spectrum efficiency, more spectrum resources and denser cells, etc. to solve the problems faced by the 4G network, thereby constructing a network society with high transmission rate, high capacity, low delay, high reliability and excellent user experience.

Figures 1 through 15, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

Fig. 1 is an exemplary system architecture 100 for System Architecture Evolution (SAE). A User Equipment (UE)101 is a terminal device for receiving data. An evolved universal terrestrial radio access network (E-UTRAN)102 is a radio access network that includes macro base stations (eNodeB/NodeB) that provide access to a radio network interface for UEs. A Mobility Management Entity (MME)103 is responsible for managing mobility context, session context and security information of the UE. Serving Gateway (SGW)104 mainly provides the functions of the user plane, and MME 103 and SGW 104 may be in the same physical entity. A packet data network gateway (PGW)105 is responsible for charging, lawful interception, etc., and may also be in the same physical entity as the SGW 104. A Policy and Charging Rules Function (PCRF)106 provides quality of service (QoS) policy and charging criteria. The general packet radio service support node (SGSN)108 is a network node device in the Universal Mobile Telecommunications System (UMTS) that provides routing for the transmission of data. The Home Subscriber Server (HSS)109 is the home subsystem of the UE and is responsible for protecting user information including the current location of the user equipment, the address of the serving node, user security information, the packet data context of the user equipment, etc.

Fig. 2 is an exemplary system architecture 200 in accordance with various embodiments of the present disclosure. Other embodiments of the system architecture 200 can be used without departing from the scope of this disclosure.

A User Equipment (UE)201 is a terminal device for receiving data. The next generation radio access network (NG-RAN)202 is a radio access network comprising base stations (the gbb or enbs connected to the 5G core network 5GC, also called NG-gbb) providing access to radio network interfaces for UEs. An access control and mobility management function (AMF)203 is responsible for managing the mobility context of the UE, and security information. A user plane functional entity (UPF)204 mainly provides the functions of the user plane. The session management function entity SMF205 is responsible for session management. The Data Network (DN)206 contains services such as the operator, access to the internet, and services for third parties.

With the development of wireless technology, in the 5G architecture, the functional modules originally located on the same base station are separated. Some functional modules are closer and closer to users, and other modules are pool-assembled and virtualized for centralized deployment. That is, the base station may be divided into two parts, one of which is a Central Control Unit (CU) and the other of which is a Distribution Unit (DU). The DU is closer to the user, and the CU is far away from the antenna, so that multi-antenna connection can be supported, and the network performance is improved. One CU may connect multiple DUs and the functions on the CU may be virtualized. The CU and the DU are connected via an F1 interface, and the F1 interface is also called fronthaul interface or fronthaul connection. The functions of RRC (Radio Resource Control), PDCP (Packet Data Convergence Protocol) are implemented on the CU, and the functions of RLC (Radio Link Control), MAC (Media Access Control), and physical layer are implemented on the DU.

Fig. 3 is a schematic diagram of a 5G architecture 300 according to various embodiments of the present disclosure. Other embodiments of the 5G architecture 300 can be used without departing from the scope of this disclosure

As shown in fig. 3, the 5G architecture includes a 5G access network and a 5G core network. The UE communicates with the data network through an access network and a core network.

Referring to fig. 3, the central control unit CU may be further divided into a control function entity (hereinafter referred to as CU-CP entity or CP entity) and a user plane function entity (hereinafter referred to as CU-UP entity or UP entity). The CP entity and the UP entity may be separate physical entities. The interface between CP and UP is referred to as the E1 interface. Only control plane is between CP and UP, and data plane is established between core network, UP and DU. The CP is connected to the core network via NG-C and to the DUs via F1-C. The UP is connected to the core network via NG-U and to the DU via F1-U.

In third Generation (3G) and fourth Generation (4G) mobile communication systems, Quality of Experience (QoE) measurement collection for streaming media services and multimedia telephony services has been standardized by the third Generation Partnership (3rd Generation Partnership Project, 3 GPP). The service experience Measurement Collection (QMC) can collect UE application layer Measurement information, which may be Measurement Collection in a certain area or for a specific service or a certain service type of a specific UE (user equipment). The collected information may be transmitted to a data center (for example, a Measurement Collection Entity (MCE)), and then used to analyze and/or calculate a Key Performance Indicator (KPI) to optimize a network and improve user service experience, thereby finally improving user loyalty and increasing revenue.

Exemplary embodiments of the present disclosure are further described below in conjunction with the appended drawings.

The text and drawings are provided as examples only to aid in understanding the present disclosure. They should not be construed as limiting the scope of the disclosure in any way. While certain embodiments and examples have been provided, it will be apparent to those skilled in the art, based on the disclosure herein, that changes can be made in the embodiments and examples shown without departing from the scope of the disclosure.

The method or device for measuring and collecting service experience (QMC) provided by the disclosure can be helpful for operators to measure and collect service experience of users on network slices, and evaluate whether slice resource usage is reasonable or not according to measurement results and whether further optimization is needed or not. The method or apparatus of the present disclosure also facilitates measuring and collecting the business experience of users under different moving speeds and/or coverage conditions to assist in solving positioning and optimizing network problems. The methods or apparatus provided by the present disclosure also help to ensure the integrity of QMC reports in the event of network congestion or network functional imperfections. The method and the device are also beneficial to configuration, reading and using of the service experience (QoE) information by the wireless access network equipment, and the QoE information is more quickly applied to wireless network optimization and functions for assisting processes of resource scheduling, load balancing and the like, so that users in the network can obtain the best user service experience on limited resources, the loyalty of the users is improved, and the income of operators is increased.

The QMC may be classified into a management-based QMC and a signaling-based QMC according to an initiation manner. According to one implementation, QMC may be initiated by an element management node, this type of QMC is referred to as management-based QMC. In management-based QMC, an access network entity receives a QMC configuration message from a network element management node. According to another implementation, QMC may be initiated by a core network entity, this type of QMC is referred to as signaling-based QMC. In signaling based QMC, the access network entity receives a QMC configuration message from the core network entity. In some examples, the core network entity may be, for example, an Access and Mobility Management entity (AMF). However, it should be understood that this is merely an example. The core network entity sending the QMC configuration message may also be another entity.

Since the network side does not know whether the UE has the capability to measure and/or record the requested data, it is required that the UE reports to the network side whether the UE has the capability to measure at the time of session establishment. A UE with the capability required for measurement by the management system on the network side can start measurement when certain conditions are met.

Fig. 4 depicts a schematic of a management-based QMC. As shown in fig. 4, an Element Management node (EM) 401 sends a QMC configuration message to an access network node 402. The access network node 402 may be an eNB of a 4G system or may also be a gNB or eNB of a 5G system, or may also be a base station in other systems. The QMC configuration message includes QMC configuration information. The QMC configuration information may be activating QMC configuration or deactivating QMC configuration. The QMC configuration information mainly includes: QMC location selection conditions, reporting mechanism configuration, QMC Reference (QMC Reference), IP address of QMC central node 404 (e.g., MCE), etc.

The QMC position selection condition configures information about which position UEs can be selected as QMC-performing UEs. The location selection condition may be configured as a range of a cell, a range of a tracking area, or an entire PLMN. UEs within the range identified by the location selection condition may be selected as QMC-performing UEs. Each QMC reference uniquely identifies a QMC task. In each QMC task, the base station may select one or more UEs for QMC.

Upon receiving the QMC configuration message, access network node 402 selects UEs for QMC. When the access network node selects a UE, certain conditions are to be followed, e.g. considering whether the UE has measurement capabilities for the corresponding traffic indicated in the QMC configuration information and/or whether the UE is located within the range identified by the location selection condition in the QMC configuration information. If the UE does not have the measurement capability of the corresponding service or the UE does not satisfy the location selection condition, the UE cannot be selected as a QMC-performing UE. After the UE is selected, the access network node sends the QMC configuration information to the selected UE. The selected UE decides whether to turn on QoE measurement by checking the QMC configuration conditions at the start of each traffic session. If the UE decides to start the QoE measurement, the UE feeds back an indication of starting the measurement to the EM through the access network, and sends the measurement result to the network node when the reporting condition configured in the reporting mechanism configuration is met. The message for transmitting the QoE measurement result includes at least the identity of QMC, UE identity, session identity, and IP address of MCE. When receiving the message, the access network node sends the QoE measurement result to the MCE.

The signaling-based QMC differs in that a QMC configuration message is sent from a core network entity to an access network entity, wherein the QMC configuration message is allocated by the core network entity.

Various embodiments according to the present disclosure will be further described with reference to the accompanying drawings.

A QMC method 500 according to one embodiment of the present disclosure is depicted in fig. 5. Detailed descriptions of steps unrelated to the present disclosure or well known in the art are omitted in the figures and the description herein so as not to obscure the aspects of the present disclosure.

The method 500 includes the steps of:

in step 501, the first node sends QMC configuration information or QMC request information to the second node.

The first node may be a network element management node or a core network node or a base station or a CU-UP or DU. The core Network node may be an AMF (Session Management Function) or an SMF (Session Management Function) or an NWDAF (Network Data analysis Function). The second node may be a base station or a CU-CP. Those skilled in the art will appreciate that the above list of first nodes or second nodes is merely exemplary and not intended to be limiting, and that the first nodes or second nodes may also be other nodes or functional entities capable of implementing the corresponding functionality.

The QMC configuration information may be activating QMC configuration information, deactivating QMC configuration information, or modifying QMC configuration information. The QMC configuration information may include one or more QMC tasks, each of which is identified by a QMC reference, each of which may include one or more traffic types that need to be measured, and a measurement configuration of each of the traffic types is identified by an application reference. Configuration condition information may also be included in activating QMC configuration. Depending on the different scenarios for performing QMC, the configuration condition information may include one or more of geographical location information, network slice information, mobile speed information, and/or radio coverage environment information, etc. It should be understood that the configuration condition information is not limited to the above-mentioned several types of information, but may also include other types of information as long as the information contributes to QMC that is adapted for different scenes.

The QMC request information may be a request for measurement collection of specific traffic experience information on a specific UE or a specific cell or a specific network slice. The QMC request information may include one or more requested condition information, such as UE ID, Cell ID, network slice information, and traffic type.

Step 502, the second node receives and saves the QMC configuration information or the second node generates the QMC configuration information itself.

For the case where the second node generates the QMC configuration information by itself, the QMC configuration information may be generated by the second node according to the QMC request information described in step 501, or may be triggered by the second node according to another reason or message, or its own reason.

The QMC configuration information may be activating QMC configuration information, deactivating QMC configuration information, or modifying QMC configuration information. The second node checks the configuration condition information, the UE capability information and/or the UE context information, and the second node sends the QMC configuration information sent by the first node or generated by the second node to the UE meeting the conditions.

In step 503, after receiving the QMC configuration information, the UE performs the following processing according to different types of QMC configuration information:

case 1: if the active QMC configuration is received, the UE may decide whether to perform measurement according to the configuration condition information in the active QMC configuration when the service type indicated in the active QMC configuration is to start a session. The configuration condition information may include one or more condition information, and the UE may start to measure the QoE only when the UE simultaneously satisfies all the condition information.

If the UE receives the QMC configuration activation and the UE satisfies the measurement condition specified in the configuration condition information, QoE measurement is performed. After the measurement is completed, the UE proceeds to step 504. In step 504, the UE generates a QMC report. And if the reporting condition is met, the UE passes the QMC report to the second node.

Case 2: if it is received to deactivate the QMC configuration, the UE decides which measurements to deactivate according to a reference identifier in the deactivated QMC configuration, wherein the reference identifier comprises a QMC reference and/or an application reference. Deactivation can be achieved, for example, in two ways: in one implementation, the UE stops QoE measurement for the identified service according to the received reference identifier in deactivating the QMC configuration; in a second implementation, the UE will continue the current measurement for the identified service, but will not restart a new QoE measurement for the identified service.

It should be understood that the above are only two exemplary ways of implementation of deactivation, and that implementation of deactivation is not limited to the above two ways, but may include any implementation that would occur to one skilled in the art based on the present disclosure.

Case 3: if a QMC modification configuration is received, the UE performs an operation adapted to the modification configuration according to different situations of the QMC modification configuration.

As an example, in one implementation, the QMC modification configuration may be to deactivate one or more measurement tasks of the plurality of measurement tasks, in which case the UE may deactivate the corresponding measurement task according to the received QMC modification configuration, for example. The implementation of deactivation has been described above and will not be described here.

In another implementation, for example, the QMC modification configuration may be a modification of QMC

Reporting time of the report. The reporting timing of the modified QMC report may be, for example, that the reporting of the QMC report needs to be suspended or buffered for wireless side reasons. And the reporting time of the QMC report is modified, so that the measurement of the QoE by the UE is not influenced. In this case, the UE may control the reporting time of the QMC report according to the received QMC modification configuration.

Upon receiving the QMC report delivered by the UE, the second node may use the QMC report for various optimizations, scheduling, etc. in step 505. In one implementation, in step 505, the second node forwards the QMC report to an entity or node specified in the QMC activation configuration (e.g., according to an address included in the QMC activation configuration).

In another implementation, upon receiving the QMC report delivered by the UE, the second node may also process the QMC report and send the result to a specific entity or node in step 505. In one example, the Entity or node may be a data center such as an MCE or a TCE (Trace Collection Entity). In another example, the entity or node may also be a core network node or a base station. In addition, the core network node may be an AMF, an SMF, an NSSF, a PCF, an NWDAF, or the like. It should be understood that the examples of entities or nodes in this disclosure are illustrative only and are not intended to be limiting.

By utilizing the QMC method 500 according to an embodiment of the present disclosure, a UE and/or a node on the network side may collect user traffic experience information measured on different network slices, at different mobility speeds, or under different coverage conditions, thereby helping to better optimize the network.

Furthermore, QMC method 500 according to embodiments of the present disclosure, for example, by modifying the QMC configuration, also helps to guarantee the integrity of QMC reports in case of network congestion or functional imperfections.

On the other hand, according to the QMC method 500 of the embodiment of the present disclosure, for example, the base station itself may initiate or generate QMC configuration information, and directly utilize the QMC configuration information delivered by the UE, so that the wireless network optimization based on QoE is also faster, which is more beneficial to improving the user service experience.

A QMC method 600 according to one embodiment of the present disclosure is depicted in fig. 6. Detailed descriptions of steps unrelated to the present disclosure or well known in the art are omitted in the figures and the description herein so as not to obscure the aspects of the present disclosure.

Depending on the entity initiating QMC activation, QMC method 600 may start with steps 601a, 601b, respectively. As will be described in detail below.

If the active QMC configuration is triggered by OAM (Operation and Maintenance), the OAM sends the active QMC configuration information to the EM, and the EM sends the active QMC configuration information to the base station through an active measurement task message in step 601 a. The active QMC configuration information may include one or more parameter sets, where each parameter set may include the following information:

-QMC references (QMC references), each of which identifies one QMC measurement task, and one QMC measurement task may correspond to one or more configuration condition information and traffic type.

-Application references (Application references) for identifying measurement configurations corresponding to a certain service type in a QMC measurement task, each Application reference identifying a QMC configuration container corresponding to a service type, said QMC configuration container being a QoE metric dimension for a certain service, such as delay, throughput, cache and device information, etc., the metric dimension being different for different measured services.

-configuration condition information to limit the specific conditions for QMC, the QMC configuration being activated only for UEs simultaneously fulfilling all configuration conditions specified in the configuration condition information. The configuration condition information may include, for example, one or more of location selection information, network slice information, movement velocity information, and/or wireless coverage environment, among others. The checking of the configuration condition may be performed by the base station or the UE. In one implementation, the configuration condition information may be placed in an RRC message. In another implementation, the configuration condition information may be placed in a QMC configuration container. As an example, the configuration condition information may include one or more of the following information:

network slice information: side information (S-NSSAI) is selected for a single network slice to indicate the network slice for which measurements need to be taken. This type of configuration condition information can be checked by the base station as well as by the UE.

Moving speed information: the method is used for limiting the condition that the UE starts the QoE measurement only in a certain moving speed interval, for example, the UE moving at a high speed or at a low speed needs to perform the QoE measurement, and the moving speed information parameters may include parameters such as moving speed evaluation time, cell change time threshold, and evaluation delay. This type of configuration condition information may be checked by the UE.

Wireless network coverage environment information: the method is used for limiting the UE to start the QoE measurement only in a certain specific wireless environment, such as a weak coverage or high interference scenario. The radio coverage environment information parameters may include one or more reference signal received level (RSRP)/Reference Signal Received Quality (RSRQ) thresholds, evaluation time, and evaluation delay. This type of configuration condition information may be checked by the UE.

-reporting configuration: is the time when the UE reports the QMC report and/or the trigger event, which may be, as non-limiting examples, a session end report, a periodic report, or a report based on event trigger.

In case of event trigger based reporting, the event may be, for example: a change in serving cell, a change in radio environment, or a sudden degradation in user traffic experience. In this way, for example, the network side can be enabled to perform QMC more specifically for faster optimization.

If the active QMC configuration is triggered by the core network, the core network sends an active QMC configuration message to the base station in step 601 b. According to different registration states of the UE, different measurement objects, and different PDU session states, the process can be divided into the following scenarios:

scene 1: the trigger to activate QMC configuration is before UE registration:

in scenario 1, the core network will send the activation QMC configuration information to the base station through an initial context request message when the UE registers.

Scene 2: the trigger to activate QMC configuration is after UE registration:

if the trigger for activating the QMC configuration is after the PDU session is established, the core network sends the information for activating the QMC configuration to the base station through the tracking start message;

if the trigger for activating the QMC configuration is when the PDU session is established, and the establishment of the PDU session just uses the network slice indicated by the configuration condition information in the activation QMC configuration information, the core network sends the activation QMC configuration information to the base station through the PDU session resource establishment request message;

if the trigger for activating the QMC configuration is during PDU session modification and the UE modifies the S-NSSAI of the existing PDU session, the core network just uses the network slice corresponding to the S-NSSAI in the configuration condition information in the activated QMC configuration, and then the core network sends the activated QMC configuration information to the base station through the PDU session resource modification request message;

the content that may be included in the above-mentioned activation QMC configuration information is the same as that in step 601a, and for the sake of clarity, the description is omitted here. In addition, the specific contents included in the activation QMC configuration information may be different according to the purpose of triggering QMC.

After receiving the activated QMC configuration information from the EM or the core network, the base station checks to select a UE satisfying the condition according to one or more of the received activated QMC configuration information, QoE measurement capability of the UE served by the base station, location condition information and/or network slice information indicated by configuration condition information in the activated QMC configuration information, and the like. Wherein, the QoE measurement capability check of the UE can be completed by the base station. The checking of the location condition information, the network slice information, and the like may be performed by the base station or the UE. In the case where the checking of the condition indicated by the configuration condition information is done by the base station, if the QMC configuration is a measurement of traffic experience for a particular network slice, the base station queries the network slice information in the UE PDU session context to determine if there is a UE that is using the network slice indicated in the QMC configuration and has QoE measurement capability.

Step 603, the base station sends an RRC reconfiguration message to the UE, where the RRC reconfiguration message includes information for activating QMC configuration, so as to include information for establishing application layer configuration measurement configuration, that is, information for activating QMC configuration. The contents that may be included in the activation QMC configuration are the same as those in step 601a, and for the sake of clarity, the description is omitted here.

In step 604, after receiving the activated QMC configuration, when a service corresponding to the service type indicated in the activated QMC configuration starts a session, the UE checks configuration condition information in the activated QMC configuration information. The configuration condition information may be one or more configuration conditions. As non-limiting examples, the configuration condition may be location condition information, network slice information, movement speed information, and/or radio coverage environment information, among other information. If the configuration condition is checked by the UE and the activated QMC configuration includes the corresponding configuration condition information, the UE needs to check whether the configuration condition is satisfied according to the current location information, the network slice information, the cell change speed, and/or the current radio environment. And judging whether all the configuration conditions for QoE measurement are met at the moment according to the range indication of the checking result indicating the configuration condition information sent by the base station and/or the checking result of the UE. If so, starting QoE measurement; and if not, not starting QoE measurement.

If the UE turns on QoE measurement as a result of the determination, the UE will generate a QMC report according to the received active QMC configuration after turning on QoE measurement in step 605. And the UE sends the generated QMC report to the base station through an application layer measurement report message.

Depending on the entity initiating QMC, the base station, upon receiving the QMC report reported by the UE, performs one of the following steps 606a-606 b.

If the address included in the activated QMC configuration is address information of the data center, after the base station receives the QMC report, the base station proceeds to step 606a where the base station forwards the QMC report to the data center. As a non-limiting example, the data center may be a TCE or an MCE.

If the QMC reports are for a particular network slice, after a certain number of QMC reports are collected, the data center may count or analyze, according to a model, the overall situation of the user service experience currently on the network slice. According to the analysis result, the network side can evaluate whether the capacity of the network slice is enough, whether the resource allocation and the parameter configuration are reasonable and the like, further analyze the reason and output the expansion or optimization suggestion. After optimization, the network side can collect the QoE information again, and comparison is performed before and after optimization.

If the QMC report is for a user in some special mobile scenarios, such as a user in a high-speed mobile scenario, the data center may count or analyze the user service experience in the high-speed mobile scenario according to a model. According to the analysis result and by combining information such as network configuration and the like, the network side can evaluate whether the network configuration in the high-speed mobile scene is reasonable or not, whether further optimization is needed or not, and the like. After optimization, the network side can collect the QoE information again, and comparison before and after optimization is carried out.

If the QMC report is for a user in a specific coverage scenario, for example, a scenario of weak coverage, high interference, etc., the data center may count or analyze the user service experience in different coverage environments according to a model. The network side can evaluate the influence of the wireless environment on the user service experience, and further optimize the network configuration so as to improve the user service experience. After optimization, the network side can collect the QoE information again, and comparison before and after optimization is carried out.

In one implementation, the data center may analyze the QMC reports in the manner described in the above exemplary implementation, and perform network optimization based on the analysis results. In another implementation, the data center may also send relevant data obtained by analyzing the QMC report to other nodes to assist the other nodes in optimizing. In one implementation, the other node may be, for example, a base station or a core network node, and the core network node may be, for example, an AMF or an SMF or an NSSF or an NWDAF or a PCF, etc.

If the address included in the activated QMC configuration is the address of the core network node, the base station, upon receiving the QMC report, forwards the QMC report to the core network node in step 606 b. The core network node may be, for example, an AMF or SMF or NSSF or NWDAF or PCF.

The core network that receives the QMC report may perform statistics and analysis on the QMC report as described in step 606 a.

In particular, if the QMC report is a QoE measurement for a specific UE, the core network node (e.g., PCF) may evaluate and decide whether to adjust the QoS parameter of the UE according to the result of the statistics and analysis of the QMC report, so as to improve the user service experience of the UE.

In particular, if the QMC report is for a particular network slice, the core network node (e.g., NSSF) may evaluate whether the policy for network slice selection needs to be modified according to the result of the statistics and analysis of the QMC report, so as to meet the requirements for the user traffic experience on all network slices.

Through the QMC method 600 according to the present disclosure, various nodes on the network side may activate QMC configuration, thereby measuring and collecting user service experience information on different network slices, at different mobile speeds, or under different coverage conditions, thereby being able to more accurately optimize network slices, optimize user service experience in high-speed mobile scenes and in weak coverage high-interference areas, thereby improving user loyalty and increasing operator profits.

A QMC method 700 according to yet another embodiment of the present disclosure is shown in fig. 7. Detailed descriptions of steps unrelated to the present disclosure or well known in the art are omitted in the figures and the description herein so as not to obscure the aspects of the present disclosure.

Depending on the entity initiating QMC activation and/or the corresponding situation, QMC method 700 may start with steps 701a, 701b, 701c, respectively. As will be described in detail below.

Case 1: under a split architecture, a CU-UP or DU in the base station may initiate activation or request QMC configuration to the CU-CP for optimization purposes such as flow control or scheduling.

In this case, the CU-UP or DU sends activation or request QMC configuration information, which may be sent by a new message, to the CU-CP in step 701 a. As a non-limiting example, the new message is, for example, an application layer measurement configuration message or an application layer measurement configuration request message. The QMC configuration may be, for example, a QMC configuration of a particular Data Radio Bearer (DRB) for a particular UE.

If the QMC configuration is activated by application-layer measurement configuration messaging in step 701a, a specific QoE measurement configuration container is included in the message. As an example, the QoE measurement configuration container is a QoE metric dimension for a certain service, such as latency, throughput, cache and device information. The QoE measurement is for different services and the metric dimension is different. And the QoE measurement configuration container also comprises reporting configuration of QMC report. The reporting may be, for example, periodic reporting, end-of-session reporting, or event-triggered reporting.

If the QMC configuration request is passed through an application layer measurement configuration request message in step 701a, that is, CU-UP or DU sends an activate QMC configuration request to CU-CP, the application layer measurement configuration request message does not include a specific QoE measurement configuration container. The QoE measurement configuration container is generated by the CU-CP after receiving the request.

The application layer measurement configuration message or the application layer measurement configuration request message may further include one or more parameter sets, and each parameter set may include one or more of the following information:

-QMC references, each QMC reference identifying one QMC task, which may correspond to one or more configuration condition information and a traffic type.

-UE ID to indicate the UE that needs to make QoE measurements.

QoS identification, indicating the type of QoS to be measured, which may be 5QI (5G Quality)

Identity, 5G quality indicator) or QCI (QoS Class Identity).

-DRB ID to indicate the corresponding DRB information of the UE that needs to be measured.

-a traffic type indicating the type of traffic that needs to be measured, such as voice traffic, video traffic or gaming.

Case 2: in a radio access network, a base station may initiate activation or request QMC configuration to a neighboring base station for optimization purposes such as load balancing.

In this case, the second base station transmits the activation QMC configuration information or the QMC configuration request to the first base station in step 701 b. In one implementation, the activate QMC configuration information or QMC configuration request may be sent by a new message. As a non-limiting example, the new message is, for example, an application layer measurement configuration message or an application layer measurement configuration request message. In another implementation, the activate QMC configuration information or QMC configuration request may also be sent by an existing message, such as a resource status request message. The activating QMC configuration information or QMC configuration request may include information on a request for QoE measurement for a specific QoS traffic or a specific network slice within a cell.

If the active QMC configuration information is sent through an application layer measurement configuration message, a specific QoE measurement configuration container may be included in the application layer measurement configuration message. The QoE measurement configuration container configures QoE metric dimensions for a certain service, such as delay, throughput, cache, and device information. The metrics vary from traffic to traffic. The QoE measurement configuration container may further include reporting configuration. The reporting configuration may indicate periodic reporting, session end reporting, or event triggered reporting, etc.

If the QMC configuration request is sent through an application layer measurement configuration request message, the application layer measurement configuration request message does not include a specific QoE measurement configuration container. And the QoE measurement configuration container is generated according to the situation after the first base station receives the request.

One or more parameter sets may also be included in the application layer measurement configuration message or the application layer measurement configuration request message. Each parameter set may include one or more of the following information:

Cell ID, indicating the Cell for which QoE measurements are required.

-S-NSSAI to indicate the network slice in the cell for which QoE measurements are required.

QoS identifier, which indicates the QoS type of QoE measurement, and may be 5QI or QCI.

Case 3: the base station may initiate activating QMC configuration itself for optimization purposes such as scheduling.

In this case, the first base station itself generates activation QMC configuration information, which may be QoE measurements for a specific UE and/or a specific network slice and/or a specific traffic, in step 701 c. The information of the QMC configuration may be the same as in step 701a and/or step 701 b.

In step 702, the first base station selects UEs meeting the conditions according to the received QMC configuration information or configuration condition information in the QMC configuration information generated by the first base station, QoE measurement capability of the UEs, and/or network slice information being used by a UE PDU session. Wherein, the QoE measurement capability check of the UE must be completed by the base station. And the checking of the configured condition (e.g., S-NSSAI and/or Cell ID and/or QoS identification) may be done by the base station or by the UE. If the configuration conditions are checked by the base station, the configuration condition information does not need to be sent to the UE, the base station needs to check whether the UE meets all the configuration conditions, and if so, the activated QMC configuration information is sent to the UE; and if not, not transmitting to the UE.

In step 703, the first base station or CU-CP sends a message to the UE that satisfies the condition to deliver the active QMC configuration information. The message may be, for example, an RRC reconfiguration message including application layer measurement configuration, i.e., activating QMC configuration information. The message may include content as described in steps 701a-701 c.

In step 704, after receiving the QMC configuration activation information, if the configuration condition is checked by the UE, the UE checks the configuration condition when starting a session, and determines whether to start QoE measurement based on the check result. If the detection result is that the UE meets the configuration condition, the UE starts QoE measurement; and if the detection result is that the UE does not meet the configuration condition, the UE does not start QoE measurement.

If the UE starts QoE measurement, after the measurement is started, in step 705, the UE generates a QMC report according to the reporting configuration. And the UE sends the QMC report to a first base station or a CU-CP. QoE reports and/or other assistance information may be included in the QMC report. The QoE report is a measurement result generated from QoE metric dimensions in a QoE measurement configuration container. The auxiliary information may be Cell ID, QoS identifier and/or DRB ID, and is used to assist the network side in analyzing the positioning problem.

After the CU-CP or the first base station receives the QMC report, one of steps 706a to 706c will proceed depending on the entity that originally initiated the QMC activation and the corresponding situation described above.

For example, if a QMC activation is generated by step 701a, i.e., QMC activation is initially triggered by a CU-UP or DU, CU-CP sends a QMC report or QoE information to CU-UP/DU in step 706 a.

In one implementation, the QMC report may be forwarded directly to the CU-UP/DU. Alternatively, the QMC report may be processed and sent to the CU-UP/DU. The QoE information sent to the CU-UP/DU may be generated from the processed QMC report or may be inferred by other methods.

If the CU-CP sends a QMC report, the QMC report can be delivered by a new message, such as an application layer measurement report message; if the CU-CP sends QoE information, the QoE information can be delivered by a new message, such as an application layer information indication message.

The QMC report after processing may include related information obtained by converting QoE dimensions into Mean Opinion Score (MoS) through a model or screening some important QoE dimensions.

After receiving the QMC report or QoE information, the CU-UP/DU may calculate or have directly obtained the service experience information of a specific DRB or a specific service type of a specific UE at the application layer. The information can be applied to a flow control strategy of the CU-UP or a scheduling strategy on the DU, so that the functions on the CU-UP or the DU can more accurately allocate or schedule resources based on granularity smaller than QoS, and the aim of optimizing the user service experience is fulfilled.

If QMC activation is generated by step 701b, i.e. QMC activation is initially triggered by the second base station, the first base station sends a QMC report or QoE information to the second base station in step 706 b.

In one implementation, the QMC report may be forwarded directly to the second base station. Alternatively, the QMC report may be processed and sent to the second base station. The QoE information may be generated from the processed QMC report or may be inferred by other methods.

The QMC report may be sent by a resource status update message if the first base station sent a QMC report. Alternatively, the QMC report may also be delivered by a new message, e.g. an application layer measurement report message. The QoE information may be transmitted by a resource status update message if the QoE information is transmitted by the first base station. Alternatively, the QoE information may also be delivered by a new message, e.g. an application layer information indication message.

After receiving the QMC report or the QoE information, the second base station may calculate or directly obtain the service experience information of the neighboring cell specific network slice or the specific QoS type at the application layer. These information and the self QoE measurement results can be used for QoE-aware-based load balancing or traffic grooming functions between base stations. The function considers the user service experience on the basis of the judgment of the original base station load. The method and the device implement load balancing or traffic grooming on the premise of ensuring the service experience, not only can meet the service experience of users and reasonably utilize resources, but also can reduce unnecessary switching caused by the load balancing or the traffic grooming, thereby reducing the risk of switching failure and user service experience decline in the switching process.

If the QMC activation is generated in step 701c, that is, the base station initiates the QMC activation by itself for the optimization purpose such as scheduling, the base station may optimize the configuration of the base station after processing the received QMC report or the QoE information reflected by the QMC report. Therefore, the base station can quickly acquire the required QMC report or QoE information, so that the configuration of the base station can be adjusted more quickly by using the QoE information.

By the QMC method according to the embodiment of the present disclosure, a plurality of nodes on the network side may initiate activating QMC configuration, so that QoE information can be configured and collected faster according to actual needs or actual situations, and the collected information can be used in functions of wireless network scheduling, resource allocation, load balancing, and the like faster. According to the QMC method disclosed by the embodiment of the disclosure, a wireless network can be optimized more quickly, and the service experience of a user is ensured and improved, so that the loyalty of the user is improved, and the income of an operator is increased.

Fig. 8 illustrates an example of a QMC method 800 for performing a deactivation or modification of QMC in accordance with the present disclosure. Detailed descriptions of steps not relevant to the present disclosure are omitted here.

As shown in fig. 8, the QMC method may start with one of 801a-801d depending on the entity or the situation of the initiation of deactivating the QMC configuration or modifying the QMC configuration.

If the deactivation of the QMC configuration or the modification of the QMC configuration is initiated by the OAM, the OAM sends the deactivation of the QMC configuration or the modification of the QMC configuration to the EM, then in step 801a, the EM sends the deactivation of the QMC configuration information or the modification of the QMC configuration information to the base station through a deactivation measurement task message or a modification measurement task message.

Since there may be multiple QMC tasks in the QMC configuration message, the multiple tasks are respectively identified by QMC references, and one QMC task may have multiple services that need to be measured, and the measured services are identified by application references, if only one or more of the QMC tasks or one of the QMC tasks needs to be deactivated, the message carries the QMC references and/or application references that need to be deactivated to indicate that the base station and/or the UE needs to deactivate the QMC measurement tasks and/or the measurement of a specific service of the QMC measurement tasks.

If the deactivation of the QMC configuration or the modification of the QMC configuration is initiated by the core network, in step 801b, the core network sends the deactivation of the QMC configuration information or the modification of the QMC configuration information to the base station, and the specific message for delivering the deactivation of the QMC configuration or the modification of the QMC configuration is divided into the following cases:

-if the PDU session does not change, the core network sends a deactivation tracking message or a tracking modification message to the base station; the deactivation trace message or the trace modification message may carry the deactivation QMC configuration or the modification QMC configuration, respectively;

-if the PDU session is modified, the core network sending a PDU session resource modification request to the base station,

wherein a deactivated QMC configuration or a modified QMC configuration may be carried;

-if the PDU session is released, the core network sends a PDU session resource release order to the base station,

where a deactivated QMC configuration or a modified QMC configuration may be carried.

The activating QMC configuration or modifying QMC configuration carries QMC reference and/or application reference to be activated to indicate the QMC task which is activated by the base station and/or the UE and/or the measurement of the specific service in the QMC task. Since multiple QMC tasks may be configured simultaneously in activating the QMC configuration, each QMC task is identified by a QMC reference, if the core network only needs to deactivate one or more QMC tasks, the QMC reference corresponding to the QMC task that needs to be deactivated specifically needs to be carried in deactivating the QMC configuration. Since it is also possible to include measurements for multiple services in one QMC task, each service is identified by an application reference, if the core network only needs to deactivate the measurement of one or more services therein, the QMC reference corresponding to the QMC task that needs to be deactivated and the application reference corresponding to the service need to be carried in the deactivation configuration.

In one case, if, for example, in step 801c, the base station receives a message from the core network, where the message may be a PDU session resource release command or a PDU session resource modification request message, and the message indicates that the PDU session deletion or the change of the corresponding S-NSSAI requires rechecking the QMC configuration condition, the base station may also decide to initiate to deactivate the QMC configuration or modify the QMC configuration according to the actual situation. The QMC configuration condition may be checked in two ways, one is base station check and one is UE check, for example. If the base station checks the QMC configuration condition, for example, if the base station finds that the S-NSSAI used by the UE service that has configured the QMC has changed, the base station may initiate to deactivate the QMC configuration or modify the QMC configuration. The messages sent by the base station to the UE for transferring the QMC deactivation information or modifying the QMC configuration information carry the QMC reference and/or the application reference to be deactivated so as to indicate the QMC task to be deactivated by the UE and/or the measurement of a specific service in the QMC task.

In another case, if the base station decides to deactivate the QMC configuration or modify the QMC configuration for its own reasons, the base station itself generates a message to transfer the deactivated QMC configuration information or the modified QMC configuration information and sends it to the UE in step 801 d. The message carries a QMC reference and/or an application reference which needs to be deactivated to indicate the QMC task which needs to be deactivated by the UE and/or the measurement of a specific service in the QMC task.

Next, after one of the above steps 801a to 801d, the base station performs one of the steps 802a to 802b according to the corresponding situation.

If the deactivation QMC configuration or modification QMC configuration is sent to the base station by the EM or the core network, or is generated by the base station for its own reason, the base station sends the deactivation QMC configuration or modification QMC configuration information, which is conveyed by the RRC reconfiguration message, to the UE in step 802 a. The RRC reconfiguration message includes release information of application layer measurement configuration, that is, information for deactivating QMC configuration or modifying QMC configuration. The UE knows to stop the corresponding QMC task or only stop the measurement of a specific service in the QMC task based on the QMC reference and/or the application reference in the received message. The advantage of such a configuration is to help the operator to control QMC more flexibly according to the customer subscription situation.

If the core network sends PDU session modification or deletion to the base station to trigger the deactivation of QMC configuration or the modification of QMC configuration and the condition change is checked by the UE, in step 802b, the base station notifies the UE of the PDU session modified S-NSSAI or the deleted PDU session ID through an RRC reconfiguration message. When the UE is ready to start the next QoE measurement, the S-NSSAI in the PDU session is checked, and if the S-NSSAI changes, the UE cannot start the QoE measurement. If the PDU session has been deleted, the UE will not start QoE measurement.

The QMC method according to the present disclosure supports the deactivation of QMC configuration of a corresponding network slice when the network slice serving a UE PDU session changes. Meanwhile, the QMC method disclosed by the invention enables an operator to more flexibly deactivate the QMC configuration or the measurement configuration of one or more service types in the QMC configuration.

Fig. 9 shows an example of a QMC method 900 according to the present disclosure. Detailed descriptions of steps not related to the present invention are omitted herein.

As shown in fig. 9, the QMC method 900 comprises the following steps:

in step 901, the base station triggers QMC configuration modification.

Reasons for triggering the modification may be:

the base station load is high, and the QMC reporting can be suspended or the QMC reporting period can be increased;

the base station load decreases and the initial QMC reporting configuration can be restarted.

During the handover, the target bs does not support the radio bearer for QMC reporting, and may suspend QMC reporting;

during the handover, the source bs does not support the radio bearer for QMC reporting, and the target bs supports the radio bearer for QMC reporting, so that the initial QMC reporting configuration may be restarted.

In step 902, the base station sends an RRC reconfiguration message to the UE, where the RRC reconfiguration message includes a modification to the measurement configuration of the application layer, that is, a modification to the QMC configuration information, and may be used to modify the reporting condition of the QMC. The modified QMC configuration information includes QMC references and/or application references corresponding to QMC tasks that need to be modified, and may further include one or more of the following information:

the reporting period, which does not affect the generation of the report at the UE side, only affects the time for reporting the QMC report by the UE. If the reporting period is configured in the modified QMC configuration information, the UE may buffer the QMC report until a time condition corresponding to the reporting period is satisfied or a new reporting instruction is received.

-a buffering indication to instruct the UE to buffer the QMC report or to instruct the UE to stop buffering and continue reporting the QMC report.

Buffer limitation conditions, which indicate the time or capacity limitation for the UE to buffer QMC reports, etc., may be a time parameter, number of files or occupied capacity. If the buffer reaches the limit condition, the UE no longer buffers the report or deletes the oldest report.

In step 903, after the UE generates the QMC report, the UE checks the reporting configuration. If there is no buffering indication or reporting period configuration, the UE sends an application layer measurement report to the base station in step 904, where the report may include previously buffered QMC report information; if the buffering indication exists, the UE buffers the QMC report and temporarily does not send the QMC report to the base station; if the reporting period configuration exists, the UE caches the QMC report until the reporting period time is up, and after the time is up, the UE sends the QMC report to the base station.

The QMC method according to the present disclosure can ensure the integrity of the QMC report when the wireless network is congested or has incomplete functions, and ensure that all measurement reports can be completely transmitted to the data center or related nodes. And more complete QoE information can be collected under the condition of not influencing the service experience of other users of the network, so as to be used for more accurately optimizing the network.

Fig. 10 shows an example of a QMC method 1000 according to the present disclosure. Detailed descriptions of steps not relevant to the present disclosure are omitted here.

As shown in fig. 10, the QMC method 1000 may comprise the steps of:

step 1001, the source base station sends a handover request message to the destination base station. If the UE to be handed over has an ongoing QMC task, the handover request message may include application layer measurement configuration information, where the application layer measurement configuration information may include one or more of all information that may be included in the aforementioned active QMC configuration information, for example, may include: QMC reference, application reference, and/or configuration condition information, etc. The configuration condition information may include information of S-NSSAI, a moving speed condition, and a radio coverage environment condition. The details of which may be as described in step 601a, for example.

The application layer measurement configuration information may further include QMC reporting buffer information, such as a buffer indication status or whether a reporting period is configured. And the target base station determines whether to modify the buffering indication or the reporting period configuration according to the base station load and/or the conditions of whether to support the wireless bearer for QMC reporting and the like. The modified reporting period configuration may be the time for deleting the reporting period or modifying the reporting period. Specifically, for example, the following two cases may be included but not limited to: in the first case, if the buffering indication of the UE in the source base station is not buffered or no reporting period is configured, and the target base station has a high load or does not support a radio bearer for QMC reporting, the target base station may decide to set the buffering indication to be buffered or configure a longer reporting period; in the second case, the UE may set the buffering indication to be not buffered or the reporting period is configured when the buffering indication of the source base station is buffered or the reporting period is configured, and the target base station has a low load or supports the radio bearer for QMC reporting.

Step 1002, the destination base station feeds back a handover request acknowledgement message to the source base station, where the message may include a handover information container that is finally required to be sent to the UE. The handover information container may include range indication information indicating a result of checking the configuration condition information, if the configuration condition information is checked by the base station. The configuration condition information includes location information, network slice information, and the like. If the target base station to which the UE is switched does not meet the configuration condition information, the range indication is not displayed within the range, so that the UE is informed that the QoE measurement does not need to be continued or a new QoE measurement does not need to be started after the UE is switched to the target base station; and if the target base station to which the UE is switched meets the configuration condition information, displaying the range indication in the range, and informing the UE that the QoE measurement needs to be continued or a new QoE measurement can be started after the UE is switched to the target base station.

If the target base station is to reconfigure the QMC reporting buffer information and is to be issued to the UE in the handover execution process, the handover request acknowledgement message may include a buffer indication or a reporting period.

According to the QMC method disclosed by the invention, when the UE changes the serving cell along with the movement, the user service experience information on different network slices, at different moving speeds or under different coverage conditions can be more completely collected and measured, the network slices can be more accurately optimized, the user service experience in high-speed moving scenes and weak coverage high-interference areas can be optimized, the user loyalty is finally improved, and the operator income is increased.

Fig. 11 shows an example of a QMC method 1100 according to the present disclosure. Detailed descriptions of steps not relevant to the present disclosure are omitted here.

As shown in fig. 11, the QMC method 1100 includes the following steps:

step 1101, the source base station sends a switching demand message to the core network, step 1102, the core network sends a switching request message to the destination base station. The messages may each include application layer measurement configuration information if the handed over UE has an ongoing QMC task. The application layer measurement configuration information may include one or more of all information that may be included in the QMC configuration information in the foregoing embodiments, and may include, for example: QMC reference, application reference, and configuration condition information, etc. The configuration condition information includes information such as S-NSSAI, moving speed condition, and radio coverage environment condition. For details, reference may be made to the description related to step 601 a.

The application layer measurement configuration information may further include QMC reporting buffer information, such as a buffer indication status or whether a reporting period is configured. And the target base station determines whether to modify the buffer indication or the configured reporting period according to the base station load and/or the conditions of whether to support the wireless bearer for QMC reporting and the like. The modified reporting period may be a time for deleting the reporting period or modifying the reporting period. Specifically, the following two cases may be included: in the first case, if the buffering indication of the UE at the source base station is not buffered or no reporting period is configured, and the target base station has a high load or does not support a radio bearer for QMC reporting, the target base station may determine to set the buffering indication to be buffered or configure a longer reporting period; in the second case, the UE may set the buffering indication to be not buffered or delete the reporting period configuration when the buffering indication of the source base station is buffered or configured with the reporting period and the target base station has low load or supports the radio bearer for QMC reporting.

Step 1103, the destination base station sends a handover request acknowledgement to the core network, and step 1104, the core network sends a handover command message to the source base station. If the configuration condition information is checked by the network side, the handover request acknowledgement and the handover command message may include a range indication indicating a checking result of the configuration condition information, so as to notify the UE whether to continue QoE measurement and reporting after handover.

If the target base station is to reconfigure the QMC reporting buffer information and issue the QMC reporting buffer information to the UE in the handover execution process, the handover request acknowledgement and the handover command message may include the QMC reporting buffer information, such as a buffer indication or a reporting period.

According to the QMC method 1100 disclosed by the present disclosure, when the UE changes in the serving cell with the movement, the information of the user service experience on different network slices, at different moving speeds, or under different coverage conditions can be collected and measured more completely, so that the network slices can be optimized more accurately, the user service experience in high-speed moving scenes and in weak coverage high-interference areas can be optimized, the user loyalty can be improved, and the operator profits can be increased.

Fig. 12 shows an example of a QMC method 1200 according to one embodiment of the present disclosure. Detailed descriptions of steps not relevant to the present disclosure are omitted here.

As shown in fig. 12, the QMC method 1200 may comprise the steps of:

step 1201, the first base station sends a request message for obtaining the UE context to the second base station. The message carries the identity of the UE in the wireless network.

Step 1202, if the context information of the UE is stored in the second base station, the second base station sends a message for obtaining the UE context feedback to the first base station. If the UE has an ongoing QMC task, the message may include application layer measurement configuration information. The application layer measurement configuration information may include one or more of all information that may be included in the QMC configuration information in the foregoing embodiments, and may include, for example: QMC reference, application reference, and configuration condition information, etc. The configuration condition information may include information of S-NSSAI, a moving speed condition, and a radio coverage environment condition. For specific details, see, e.g., the associated description in step 601 a.

The application layer measurement configuration information may further include QMC reporting buffer information, for example, whether there is a buffer indication or whether a reporting period is configured. The first base station determines whether to modify the buffering indication or the reporting period according to the base station load and/or whether to support the radio bearer for the QMC reporting. The modified reporting period may be a time for deleting the reporting period or modifying the reporting period. If the reporting period of the buffering indication or the configuration needs to be modified, the first base station may send the modified QMC configuration information to the UE after receiving the message for obtaining the UE context feedback.

According to the QMC method disclosed by the invention, when the UE radio link fails, the user service experience information on different network slices, at different moving speeds or under different coverage conditions can be more completely collected and measured, so that the network slices can be more accurately optimized, the user service experience in a high-speed moving scene and a weak coverage high-interference area can be optimized, the user loyalty is finally improved, and the operator income is increased.

Fig. 13 shows an example of a QMC method 1300 according to one embodiment of the present disclosure. Detailed descriptions of steps not relevant to the present disclosure are omitted here.

As shown in fig. 13, the QMC method 1300 may comprise the steps of:

in step 1301, the UE generates a QMC report and sends the QMC report to the first node if appropriate.

Some side information, such as network slice information, serving cell information, and/or DRB information, may also be included in the QMC report. For the generated QMC report, the UE checks whether there is a buffering indication or reporting period configuration. If the buffering indication exists or the time corresponding to the reporting period is not reached, the UE buffers the QMC report; and if no buffer indication exists or the time corresponding to the reporting period is reached, the UE sends the QMC report to the first node through the application layer measurement report message. The first node may be a base station or a CU-CP.

In step 1302, the first node receives a QMC report from the UE, reads and analyzes the QMC report, and obtains the required QoE information. The QoE information may be an MOS value calculated according to a model, or an important QoE dimension screened according to an optimization purpose.

Alternatively, if there is no QMC report, the first node may also infer the required QoE information from other information, which may be key performance parameters for user QoS type statistics, such as throughput, packet loss, and latency.

In step 1303, the first node sends a QMC report or QoE information to the second node.

The second node can be a base station or a CU-UP/DU or a core network node or a network management element management node or a MCE or a TCE. The core network node may be an AMF or an SMF or an NSSF or an NWDAF or a PCF. The first node communicates the QMC report or QoE information to the second node, which may include, for example, the following cases:

case 1, the address information of the node collecting QoE, which is pre-configured in the previous QMC configuration or QMC request, is the address information of the second node;

in case 2, the second node requests QoE information, and the first node feeds back QoE information.

In case 3, the first node actively delivers QoE information.

In step 1304, the second node receives the QMC report or QoE information.

The second node may perform further analysis processing according to the received QMC report or QoE information, so as to optimize the network and improve the user service experience.

According to the QMC method of the present disclosure, the base station may read or process or infer QoE information and send to any possible node. This enables a faster, more accurate optimization. In addition, many functional entities can adjust resources after obtaining QoE, so that resources can be utilized more reasonably and better user experience can be provided more conveniently.

According to the QMC method disclosed by the invention, user service experience information on different network slices, different moving speeds or different coverage scenes can be collected, so that the network can be better optimized. In addition, according to the QMC method disclosed by the invention, the integrity of the QMC report can be ensured under the condition of network congestion or incomplete functions, and meanwhile, the wireless network optimization based on QoE can be faster, thereby being more beneficial to improving the service experience of users.

Fig. 14 shows an example of a QMC method 1400 according to one embodiment of the present disclosure. Detailed descriptions of steps not relevant to the present disclosure are omitted here.

As shown in fig. 14, the QMC method 1400 may comprise the steps of:

the QMC method 1400 may start in step 1401a or 1401b, depending on the way the first base station or CU-CP obtains QoE information.

In step 1401a, the UE sends a QMC report to the first base station or CU-CP, which is conveyed by an application layer measurement report message. The message may also include the following information:

-a QMC reference to indicate for which QMC task/tasks the QoE measurement is.

-applying a reference to indicate for which specific service/services the QoE measurement results are measurements.

A QoE report container, a specific measurement value output by the application layer, derived from the QoE metric dimension in the QMC configuration container. Such as latency, buffering, throughput or user equipment information, etc.

-S-NSSAI to indicate network slice information used in QoE measurements.

Cell ID to indicate Cell information where QoE measurements are located.

DRB ID to indicate DRB information used in QoE measurement.

The information such as S-NSSAI, Cell ID and DRB ID is optional information and is used in a specific optimization scene. Such information may be included in the QoE report container or outside the QoE report container.

After receiving the QMC report, the first base station may directly forward the report to other nodes or entities according to the QMC configuration information, or may read the report for further analysis and processing, and generate QoE information. The analysis processing process is different according to different optimization purposes and different processing modes. As a non-limiting example, if the optimization objective is to know the overall experience satisfaction of the service, the first base station may model each dimension measurement of QoE in multiple QMC reports into MOS; if the optimization aim is to collect certain important dimension information of the QoE for artificial intelligence calculation, switching conditions or scheduling conditions and the like, the first base station can screen out one or more dimension information, such as the cache level and the number of times of blocking of video services, the interaction delay of VR services and the like.

In step 1401b, the first base station or CU-CP may also infer QoE information from other information. The other information may be key performance parameters for user QoS type statistics, such as throughput, packet loss, and latency.

Depending on the entity requesting QoE information, QMC method 1400 may comprise step 1402a or 1402 b.

In step 1402a, the CU-UP or DU transmits QoE information request information to the CU-CP.

The request information may include one or more parameter sets, each parameter set and may include one or more of the following:

-UE ID to indicate the UE that needs to collect QoE information;

QoS identifier, which indicates the QoS type for which QoE information needs to be collected, and may be 5QI (5G Quality Identity) or qci (QoS Class Identity);

-DRB ID to indicate corresponding DRB information for UEs needing to collect QoE information;

-a traffic type indicating the type of traffic that needs to collect QoE information, such as voice traffic, video traffic, or games.

In one implementation, the QoE information request message may be delivered by a new message, for example, an application layer information request message. The CU-CP can decide whether to feed back QoE information to the CU-UP or DU according to the situation.

In step 1402b, the second base station sends QoE information request information to the first base station, where the request information may include one or more parameter sets, and each parameter set may include one or more of the following information:

-Cell ID to indicate the Cell that needs to collect QoE information;

-S-NSSAI to indicate the network slice for which QoE information needs to be collected;

-QoS identifier, which indicates the QoS type for which QoE information needs to be collected, and may be 5QI or QCI;

In one implementation, the QoE information request message may be sent by an E-UTRA-NR cell resource coordination request message or a resource status request message. In another implementation, the QoE information request message may be delivered by a new message, such as an application layer information request message. The first base station may decide whether to feed back the QoE information to the second base station according to the situation.

Corresponding to step 1402a or 1402b, QMC method 1400 may proceed to step 1403a or 1403 b.

If the QMC or QoE information measurement is CU-UP or DU originated or requested, CU-CP sends a message to CU-UP and/or DU conveying QMC report or QoE information at step 1403 a. In one implementation, the message may be delivered by a new message, such as an application layer measurement report message or an application layer information indication message. In consideration of the timeliness of the application, the application layer related information can also carry information such as time marks and the like.

After receiving the QMC report or QoE information, the CU-UP or DU may calculate or directly obtain the service experience information of a specific DRB or a specific service type of a specific UE. The information can be used for a flow control strategy of the CU-UP or a scheduling strategy on the DU, and each function on the CU-UP or the DU can be more accurately allocated or scheduled on the basis of granularity smaller than QoS, so that the aim of optimizing the user service experience is fulfilled.

If the QMC measurement or QoE information is initiated or requested by the second base station, or there is cell information about the second base station in the QMC report, the first base station sends a message conveying the QMC report or QoE information to the second base station in step 1403 b. In one implementation, the message may be an evolved universal terrestrial radio access-new air interface (E-UTRA-NR) cell resource coordination feedback message or a resource status update message. In another implementation, the message is a new message, such as an application layer measurement report message or an application layer information indication message. In consideration of the timeliness of the application, the application layer related information may carry information such as a time stamp.

After receiving the QMC report or QoE information, the second base station may calculate or directly obtain the service experience information of the neighboring cell or the specific network slice of the cell or the specific QoS type. Such information may be used for QoE-aware based load balancing or traffic grooming functions between base stations. The function adds and considers user service experience on the basis of the judgment of the original base station load, thereby realizing load balancing or service grooming on the premise of ensuring the service experience. Therefore, the method can meet the user service experience and reasonably utilize resources, and can reduce unnecessary switching caused by load balancing or service grooming, thereby reducing the risk of switching failure and user service experience reduction in the switching process. In the multi-connection mode, the QoE information of the primary cell and the secondary cell is obtained through the process, so as to assist resource coordination.

Further, if the data center address is carried in the initial QMC configuration or the data center requests QoE information, the QMC method 1400 may proceed to step 1403c, where the first base station sends a QMC report or QoE information to the data center.

If the QMC report or QoE information is specific to a particular network slice, after a certain number of QMC reports or QoE information are collected, the data center may count or analyze the overall user service experience situation on the current network slice according to a model. According to the analysis result, the network side can evaluate whether the capacity of the network slice is enough, whether the resource allocation and the parameter configuration are reasonable and the like, further analyze the reason according to the problem, and output expansion or optimization suggestions and the like. After optimization, QoE information is collected again, and comparison before and after optimization is carried out.

If the QMC report or the QoE information is for a user in some special mobile scenarios, such as a user in a high-speed mobile scenario, the data center may count or analyze the user service experience in the high-speed mobile scenario according to the model, and evaluate whether the network configuration in the high-speed mobile scenario is reasonable or not and whether further optimization is needed or not according to the analysis result and information such as the network configuration. After optimization, the QoE information is collected again, and comparison before and after optimization is carried out.

If the QMC report or the QoE information is for a user in a specific coverage scenario, for example, a scenario such as weak coverage, high interference, etc., the data center may count or analyze user service experiences in different coverage environments according to a model, evaluate the influence of a wireless environment on the user service experiences, and further optimize network configuration to improve the user service experiences. After optimization, the QoE information is collected again, and comparison before and after optimization is carried out.

The data center may analyze the QMC report or the QoE information according to the above description, perform network optimization according to the analysis result, and may also transmit the analyzed data to other nodes to assist the other nodes in optimizing. The other node may be, for example, a base station or a core network node, and the core network node may be, for example, an AMF or an SMF or an NSSF or an NWDAF or a PCF, etc.

Further, if the core network node information is carried in the initial QMC configuration or the core network node requests QoE information, the QMC method 1400 may proceed to step 1403d, where the first base station sends a QMC report or QoE information to the core network node. The message for forwarding the QMC report or QoE information may use an existing message or a new message, such as a trace report message or an application layer measurement report message or an application layer information indication message.

The core network may perform statistics and analysis of the QMC reports or QoE information as described in step 1402 c.

In particular, if the QMC report or the QoE information is a measurement for a specific UE, the core network node (e.g., PCF) may evaluate and decide whether to adjust the QoS parameter of the UE according to the analysis result, so as to improve the user service experience.

In particular, if the QMC report or QoE information is for a specific network slice, the core network node (e.g., NSSF) may evaluate whether to modify the policy for network slice selection according to the analysis result, so as to enable the user traffic experience on all network slices to meet the requirement.

According to the QMC method disclosed by the invention, a wireless network can obtain QoE information more quickly, and the information is used in functions of wireless network scheduling, resource allocation, load balancing and the like, so that the wireless network can be optimized more quickly, and the user service experience is ensured and improved. The QMC method can also collect user service experience information on different network slices, at different moving speeds or under different coverage conditions, thereby more accurately optimizing the network slices, optimizing the user service experience in high-speed moving scenes and weak coverage high-interference areas, finally improving the loyalty of users and increasing the income of operators.

Fig. 15 shows a simplified block diagram of an example configuration of hardware components of a QMC apparatus 1500, which may implement a QMC method according to various embodiments of the present disclosure, according to various embodiments of the present disclosure.

The QMC apparatus may be implemented in any apparatus that may perform the relevant steps in the QMC method according to the present disclosure. As non-limiting examples, the QMC apparatus may be implemented in a network node such as a base station, a user equipment, a core network, a data center, an EM, or any similar apparatus.

As shown in fig. 15, the QMC apparatus 1500 includes a transceiving unit 1501, a processor 1502, and a memory 1503.

The transceiving unit 1501 is configured to receive and/or transmit signals.

The processor 1502 is operatively connected to the transceiving unit 1501 and the memory 1503. The processor 1502 may be implemented as one or more processors configured to operate in accordance with the QMC methods described in the various embodiments of the present disclosure.

The memory 1503 is configured to store data. The memory 1503 may include non-transitory memory for storing operations and/or code instructions executable by the processor 1502. The memory 1503 may include processor-readable non-transitory instructions that, when executed, cause the processor 1502 to implement the steps of the QMC method according to various embodiments of the present disclosure. The memory 1503 may also include random access memory or buffer(s) to store intermediate processing data from the various functions performed by the processor 1502.

Those of ordinary skill in the art will realize that the description of the QMC method and apparatus is illustrative only and is not intended to be limiting in any way. Other embodiments will readily suggest themselves to such skilled persons having the benefit of this disclosure.

For the sake of clarity, not all of the conventional features of embodiments of the QMC method and apparatus have been shown and described. It will of course be appreciated that in the development of any such actual implementation of the QMC method and apparatus, numerous implementation-specific decisions may need to be made in order to achieve the developer's specific goals, such as compliance with application, system, network, and business-related constraints, and that these specific goals will vary from one implementation to another and from one developer to another.

The modules, processing operations, and/or data structures described in accordance with the present disclosure may be implemented using various types of operating systems, computing platforms, network devices, computer programs, and/or general purpose machines. Further, those of ordinary skill in the art will recognize that less general purpose devices, such as hardwired devices, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), or the like, may also be used. Where a method comprising a series of operations and sub-operations is implemented by a processor, computer, or machine, and those operations and sub-operations may be stored as a series of non-transitory code instructions readable by the processor, computer, or machine, they may be stored on a tangible and/or non-transitory medium.

The modules of the QMC methods and apparatus described herein may comprise software, firmware, hardware, or any combination(s) of software, firmware, or hardware suitable for the purposes described herein.

In the QMC method described herein, various operations and sub-operations may be performed in various orders, and some of the operations and sub-operations may be optional.

While the foregoing disclosure of the present application has been made by way of non-limiting illustrative embodiments, these embodiments can be modified at will within the scope of the appended claims without departing from the spirit and nature of the disclosure.

Claims

1. A traffic experience measurement collection QMC method, comprising the steps of:

transmitting, by a node, first information to one or more UEs;

wherein the first information: generated by the node, or received by the node from other nodes.

2. The method of claim 1, wherein the first information is QMC configuration information, an

Wherein the QMC configuration information is one of the following types: activating QMC configuration information, deactivating QMC configuration information, or modifying QMC configuration information.

3. The method of claim 2, wherein the QMC configuration information is generated by the node based on second information received from other nodes or based on a cause of the node itself.

4. The method of claim 3, wherein the second information comprises a request for QMC or PDU session modification or deletion.

5. The method of claim 2, wherein the QMC configuration information comprises one or more QMC references, different QMC references identifying different QMC tasks,

each QMC task includes one or more application references that identify a traffic type.

6. The method of claim 2, wherein the activating QMC configuration information comprises configuration condition information, wherein the configuration condition information comprises one or more of geographical location information, network slice information, mobile speed information, and/or radio coverage environment information.

7. The method of claim 2, wherein the activating QMC configuration information further comprises a reporting configuration comprising one of an end-of-session report, a periodic report, or an event-triggered based report,

wherein the reported triggering event based on event triggering includes one or more of a serving cell change, a radio environment change, or a sudden user service experience degradation.

8. The method of any of claims 1-7, further comprising: receiving a QMC report from at least one of the one or more UEs,

wherein the QMC report includes one or more of serving cell information, network slice information, QoS information, or DRB information.

9. The method of claim 8, further comprising: the node obtains the required service experience QoE information based on the QMC report, or deduces other QoE information based on the QoE information, or the node sends the QMC report, the QoE information or the other QoE information to other one or more nodes.

10. The method of claim 2, wherein the deactivating QMC configuration information or modifying QMC configuration information comprises a QMC reference requiring deactivation and/or an application reference indicating a measurement of a specific traffic in the QMC task requiring deactivation and/or QMC task.

11. The method of claim 2, wherein the modifying QMC configuration information further comprises one or more of reporting period, buffering indication, or buffering limitation condition.

12. A traffic experience measurement collection QMC method, comprising the steps of:

receiving, by a UE, a first message from a node;

determining, by the UE, information related to the QMC based on the received first message.

13. The method of claim 12, wherein the first message comprises QMC configuration information comprising one or more QMC references, wherein different QMC references identify different QMC tasks,

each QMC task includes one or more application references identifying the traffic type,

14. The method of claim 13, wherein, in response to the QMC configuration information being an active QMC configuration information, the determining, by the UE, information related to QMC based on the received first message comprises:

the UE determines whether to perform QoE measurement based on configuration condition information included in the QMC configuration information, performs QoE measurement and transmits a QMC report obtained by measurement to the node if the determination result is positive,

the QMC configuration information further includes a reporting configuration, and the UE reports the QMC based on the reporting configuration.

15. The method of claim 13, wherein, in response to the QMC configuration information being a deactivation QMC configuration information or a modification QMC configuration information, the determining, by the UE, information related to QMC based on the received first message comprises:

in response to including a QMC reference and/or an application reference in the first message, the UE deactivates measurement of a specific traffic in a corresponding QMC task and/or QMC task,

in response to the first message including information on modifying reporting timing of a QMC report, the UE controls a time of reporting of a QMC report based on the information.

16. The method of claim 12, wherein the first message is information regarding PDU session modification or deletion, the determining, by the UE, QMC-related information based on the received first message comprises:

the UE determines whether to start or stop QoE measurement based on information about PDU session modification or deletion.

17. The method of claim 12, wherein the first message is a message comprising a range indication and/or reporting buffer information, the reporting buffer information comprising one or more of a reporting period, a buffer indication, or a buffer restriction condition, and

wherein the determining, by the UE, the information related to QMC based on the received first message comprises:

in response to receiving the range indication, determining, by the UE, whether to perform QoE measurement based on the range indication, and if the determination is yes, starting the measurement and generating a QMC report including the assistance information;

in response to receiving the reporting buffer information, performing, by the UE, based on the reporting buffer information, one of: buffering the QMC report, sending the QMC report to the node through an application layer measurement report message.

18. A traffic experience measurement collection, QMC, method comprising:

receiving, by the first node, a first request message from the second node; and

sending, by the first node, a response message related to QMC to the second node.

19. The QMC method of claim 18, wherein:

the first request message is a handover request message, and the response message is a handover request acknowledgement message; or

The first request message is a handover requirement message, and the response message is a handover command message; or

The first request message is a request message for obtaining UE context, and the response message is a feedback message for obtaining UE context; or

The first request message is a message for requesting a QMC report or QoE information, and the response message is a message for feeding back the requested QMC report or QoE information;

wherein the handover request message or handover required message or obtaining UE context feedback message includes application layer measurement configuration information, and the application layer measurement configuration information includes at least one of the following: a QMC reference, an application reference, a QMC report buffer information, and a configuration condition information, the configuration condition information including one or more of network slice information, mobile speed information, and radio coverage environment information, the QMC report buffer information indicating a buffer indicated state or whether a reporting period is configured,

wherein the handover request acknowledge message or the handover command message includes a handover information container, the handover information container includes range indication information indicating a checking result of the configuration condition information, or further includes a buffering indication or a reporting period,

wherein the message for requesting the QMC report or the QoE information and the message for feeding back the requested QMC report or QoE information include one or more of cell information, network slice information, QoS information, or DRB information.

20. A QMC apparatus, comprising:

a transceiving unit configured to receive and transmit wireless data,

a memory configured to store data, an

A processor configured to perform the method of claims 1-19.