A QoE measurement configuration method, apparatus, electronic device, and storage medium

Abstract

This application provides a QoE measurement configuration method, apparatus, electronic device, and storage medium, relating to the field of communication technology. It addresses the current issues in NR-DC network scenarios, such as insufficient flexibility in configuring and reporting QoE measurements of different priorities, and the network's inability to distinguish QoE reports related to MN or SN services. The method includes: a terminal receiving first configuration information from a primary base station; wherein the first configuration information instructs the terminal to perform QoE measurement, and includes first indication information indicating the target base station corresponding to the QoE measurement; the terminal sending a QoE measurement report to the target base station based on the first configuration information; wherein the target base station includes a primary base station or a secondary base station. This application is used for QoE measurement configuration in NR-DC network scenarios.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a QoE measurement configuration method, apparatus, electronic device, and storage medium. Background Technology

[0002] In the 5th Generation Mobile Communication Technology (5G), in the New Radio Dual Connectivity (NR-DC) network, if the secondary gNodeB (SN) is successfully added, the SN's Radio Resource Control (RRC) signaling is reported directly to the SN via Signalalling Radio Bearer (SRB) 3 or directly to the MN via SRB1, and then transmitted by the MN to the SN.

[0003] However, the existing reporting mechanism for Quality of Experience (QoE) measurements can only transmit RRC signaling via the lower-priority SRB4 to the base station, which conflicts with the signaling scheduling of NR-DC. Reports related to the Master gNodeB (MN) are always slower than SN-related QoE measurement reports due to the lower scheduling priority of SRB4. For some higher-priority MN-related QoE measurement configurations, the existing mechanism actually lowers the priority of MN-related QoE reports.

[0004] Furthermore, on the network management side, such as the Operation Administration and Maintenance (OAM) network element and the base station side, it is not possible to batch configure the QoE configuration of a certain type of service as MN or SN related. After receiving the QoE configuration, the UE is also unable to batch upload MN or SN related QoE reports according to the service type for OAM to perform statistical analysis. Summary of the Invention

[0005] This application provides a QoE measurement configuration method, apparatus, electronic device, and storage medium, which can solve the problems of insufficient flexibility in configuring and reporting QoE measurements of different priorities in the current NR-DC network scenario, and the network's inability to distinguish QoE reports related to MN or SN services.

[0006] To solve the above-mentioned technical problems, this application adopts the following technical solution:

[0007] In a first aspect, this application provides a QoE measurement configuration method, the method comprising: a terminal receiving first configuration information from a primary base station; wherein the first configuration information is used to instruct the terminal to perform QoE measurement, the first configuration information including first indication information, the first indication information being used to instruct the terminal to target base station corresponding to the QoE measurement; the terminal sending a QoE measurement report to the target base station according to the first configuration information; wherein the target base station includes a primary base station or a secondary base station.

[0008] Based on the above technical solution, this application includes mrdc-MN Measurement information in the QoE configuration message sent by the primary base station (MN) to the terminal. This information is used to distinguish between QoE measurements related to the primary base station (MN) and those related to the secondary base station (SN), thereby enabling user experience collection for primary / secondary nodes. The terminal then sends the QoE measurement report to the corresponding target base station. Therefore, this application can flexibly report QoE measurement configurations of different priorities, and the network can distinguish between QoE measurement reports related to MN or SN services.

[0009] In conjunction with the first aspect above, in one possible implementation, the terminal sends a QoE measurement report to the target base station according to the first configuration information, specifically including: if the target base station indicated by the first indication information is a primary base station, the terminal sends a QoE measurement report to the primary base station; if the target base station indicated by the first indication information is a secondary base station, and the signaling radio bearer SRB3 is configured and the secondary cell group SCG is not deactivated, the terminal sends a QoE measurement report to the secondary base station; if the target base station indicated by the first indication information is a secondary base station, and SRB3 is not configured or SCG has been deactivated, the terminal sends a QoE measurement report to the primary base station.

[0010] In conjunction with the first aspect above, in one possible implementation, the method further includes: after receiving the first indication information, the terminal determines the target user corresponding to the QoE measurement; the terminal performs QoE measurement on the target user and determines a QoE measurement report.

[0011] In conjunction with the first aspect mentioned above, in one possible implementation, the target users include primary base station users or secondary base station users.

[0012] In conjunction with the first aspect mentioned above, in one possible implementation, the first configuration message is the App Layer MeasConfig message, and the first indication information is the mrdc-MN Measurement field information.

[0013] In conjunction with the first aspect above, in one possible implementation, the QoE measurement report is carried in a MeasurementReport App Layer message. The MeasurementReport App Layer message includes second indication information, which is used to indicate the target base station related to the QoE measurement report.

[0014] In conjunction with the first aspect mentioned above, in one possible implementation, the second indication information is the mrdc-MNMeasurement field information.

[0015] Secondly, this application provides a QoE measurement configuration method, the method comprising: a main base station sending first configuration information to a terminal; wherein the first configuration information is used to instruct the terminal to perform QoE measurement, the first configuration information including first indication information, the first indication information being used to instruct the terminal to perform QoE measurement on a target base station corresponding to the QoE measurement; and the main base station receiving a QoE measurement report from the terminal.

[0016] In conjunction with the second aspect above, in one possible implementation, the method further includes: the first configuration message is an App Layer Meas Config message, and the first indication information is mrdc-MN Measurement field information.

[0017] In conjunction with the second aspect above, in one possible implementation, the QoE measurement report is carried in a MeasurementReport App Layer message. The MeasurementReport App Layer message includes second indication information, which is used to indicate the target base station related to the QoE measurement report.

[0018] In conjunction with the second aspect mentioned above, in one possible implementation, the second indication information is the mrdc-MNMeasurement field information.

[0019] Thirdly, this application provides a QoE measurement configuration device, which includes: a receiving unit and a transmitting unit; the receiving unit is configured to receive first configuration information from a primary base station; wherein the first configuration information is used to instruct a terminal to perform QoE measurement, and the first configuration information includes first indication information, which instructs the terminal to target base stations corresponding to the QoE measurement; the transmitting unit is configured to send a QoE measurement report to the target base station according to the first configuration information; wherein the target base station includes a primary base station or a secondary base station.

[0020] In conjunction with the third aspect above, in one possible implementation, the sending unit is further configured to send a QoE measurement report to the primary base station when the target base station indicated by the first indication information is the primary base station; the sending unit is further configured to send a QoE measurement report to the secondary base station when the target base station indicated by the first indication information is the secondary base station, and the signaling radio bearer SRB3 is configured and the secondary cell group SCG is not deactivated; the sending unit is further configured to send a QoE measurement report to the primary base station when the target base station indicated by the first indication information is the secondary base station, and SRB3 is not configured or SCG has been deactivated.

[0021] In conjunction with the third aspect above, in one possible implementation, the QoE measurement configuration device further includes: a processing unit; the processing unit is configured to determine the target user corresponding to the QoE measurement after receiving the first indication information; the processing unit is configured to perform QoE measurement on the target user and determine a QoE measurement report.

[0022] In conjunction with the third aspect mentioned above, in one possible implementation, the target users include either primary base station users or secondary base station users.

[0023] In conjunction with the third aspect mentioned above, in one possible implementation, the first configuration message is the App Layer MeasConfig message, and the first indication information is the mrdc-MN Measurement field information.

[0024] In conjunction with the third aspect mentioned above, in one possible implementation, the QoE measurement report is carried in a MeasurementReport App Layer message. The MeasurementReport App Layer message includes second indication information, which is used to indicate the target base station related to the QoE measurement report.

[0025] In conjunction with the third aspect mentioned above, in one possible implementation, the second indication information is the mrdc-MNMeasurement field information.

[0026] Fourthly, this application provides a QoE measurement configuration device, which includes: a transmitting unit and a receiving unit; the transmitting unit is used to transmit first configuration information to a terminal; wherein the first configuration information is used to instruct the terminal to perform QoE measurement, and the first configuration information includes first indication information, which is used to indicate the target base station corresponding to the QoE measurement; the receiving unit is used to receive a QoE measurement report from the terminal.

[0027] In conjunction with the fourth aspect mentioned above, in one possible implementation, the first configuration message is the App Layer MeasConfig message, and the first indication information is the mrdc-MN Measurement field information.

[0028] In conjunction with the fourth aspect above, in one possible implementation, the QoE measurement report is carried in a MeasurementReport App Layer message. The MeasurementReport App Layer message includes second indication information, which is used to indicate the target base station related to the QoE measurement report.

[0029] In conjunction with the fourth aspect mentioned above, in one possible implementation, the second indication information is the mrdc-MNMeasurement field information.

[0030] Fifthly, this application provides an electronic device comprising: a processor and a communication interface; the communication interface and the processor are coupled, the processor being configured to run computer programs or instructions to implement the QoE measurement configuration method as described in the first aspect and any possible implementation thereof or in the second aspect and any possible implementation thereof.

[0031] In a sixth aspect, this application provides a computer-readable storage medium storing instructions that, when executed on a terminal, cause the terminal to perform the QoE measurement configuration method as described in the first aspect and any possible implementation thereof, or the second aspect and any possible implementation thereof.

[0032] In a seventh aspect, this application provides a computer program product containing instructions that, when run on a QoE measurement configuration device, cause the QoE measurement configuration device to perform the QoE measurement configuration method as described in the first aspect and any possible implementation thereof, or in the second aspect and any possible implementation thereof.

[0033] Eighthly, this application provides a chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being configured to run computer programs or instructions to implement the QoE measurement configuration method as described in the first aspect and any possible implementation of the first aspect or the second aspect and any possible implementation of the second aspect.

[0034] Specifically, the chip provided in this application also includes a memory for storing computer programs or instructions.

[0035] It should be noted that the aforementioned computer instructions may be stored, in whole or in part, on a computer-readable storage medium. This computer-readable storage medium may be packaged together with the processor of the device, or it may be packaged separately from the processor of the device; this application does not impose any limitation on this.

[0036] Ninthly, this application provides a QoE measurement configuration system, including: a terminal and a first access network device, wherein the terminal is configured to execute the QoE measurement configuration method as described in the first aspect and any possible implementation thereof, and the first access network device is configured to execute the QoE measurement configuration method as described in the second aspect and any possible implementation thereof.

[0037] The descriptions of aspects two through nine in this application can be referenced to the detailed description of aspect one; and the beneficial effects of the descriptions of aspects two through nine can be referenced to the analysis of the beneficial effects of aspect one, which will not be repeated here.

[0038] In this application, the names of the aforementioned terminal, first access network device, and QoE measurement and configuration device do not limit the devices or functional modules themselves. In actual implementation, these devices or functional modules may appear under other names. As long as the functions of each device or functional module are similar to those in this application, they fall within the scope of the claims of this application and their equivalents.

[0039] These or other aspects of this application will become more readily apparent in the following description. Attached Figure Description

[0040] Figure 1 A flowchart of signaling-based QoE measurement provided for embodiments of this application;

[0041] Figure 2 A flowchart of a managed QoE measurement provided for embodiments of this application;

[0042] Figure 3 A schematic diagram illustrating the process of adding a SN in the NR-DC network provided in this application embodiment;

[0043] Figure 4 This is a schematic diagram of the RRC Transfer process provided in an embodiment of this application;

[0044] Figure 5 An architecture diagram of a communication system provided in an embodiment of this application;

[0045] Figure 6 A flowchart illustrating a QoE measurement configuration method provided in an embodiment of this application;

[0046] Figure 7A flowchart illustrating another QoE measurement configuration method provided in this application embodiment;

[0047] Figure 8 A flowchart illustrating another QoE measurement configuration method provided in this application embodiment;

[0048] Figure 9 This is a schematic diagram of the structure of a QoE measurement configuration device provided in an embodiment of this application;

[0049] Figure 10 A schematic diagram of another QoE measurement configuration device provided in an embodiment of this application;

[0050] Figure 11 This is a schematic diagram of another QoE measurement configuration device provided in an embodiment of this application. Detailed Implementation

[0051] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0052] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0053] The terms "first" and "second," etc., used in the specification and drawings of this application are used to distinguish different objects or to distinguish different treatments of the same object, rather than to describe a specific order of objects.

[0054] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0055] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0056] In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0057] The following explanations of the terms used in the embodiments of this application are provided to facilitate the reader's understanding.

[0058] I. QoE Measurement

[0059] QoE measurement refers to measuring users' overall subjective experience of the quality and performance of services (including effectiveness and availability). In other words, it measures users' experience using service applications, allowing operators to comprehensively evaluate service quality and performance through QoE measurement results. This enables operators to identify problems in the services based on the comprehensive evaluation results of users and make adaptive adjustments to the communication network accordingly.

[0060] It should be noted that QoE measurement includes: 1.1, signaling-based QoE measurement, and 1.2, management-based QoE measurement. These will be explained in detail below:

[0061] 1.1 Signaling-based QoE measurement

[0062] Signaling-based QoE measurement refers to QoE measurement performed on a specific terminal, and signaling-based QoE measurement can be performed in real time.

[0063] like Figure 1 As shown, the signaling-based QoE measurement process includes the following steps 101 to 108.

[0064] Step 101: The terminal's access stratum (AS) layer sends a capability message to the access network device. Correspondingly, the access network device receives the capability message sent from the terminal's AS layer.

[0065] Among them, the capability message is used to characterize the terminal's ability to perform QoE measurement. The access network equipment can be a radio access network (NG-RAN) in a 5G network.

[0066] In one possible implementation, the aforementioned capability message can be a Capability Information message sent by the terminal to the access network device.

[0067] Step 102: The Operation Administration and Maintenance (OAM) device sends a Configuration QoE Measurement Message to the core network device. Correspondingly, the core network device receives the Configuration QoE Measurement Message from the OAM.

[0068] The configuration QoE measurement message is used to trigger the core network equipment to perform QoE measurement configuration and carries QoE measurement configuration parameters.

[0069] In one possible implementation, the configuration QoE measurement message can be a Configure QoE Measurement message sent by the OAM to the core network device.

[0070] It should be noted that the above-mentioned QoE measurement configuration message may include the configuration range of QoE measurement and the parameter information of the required QoE measurement.

[0071] It should be noted that if the access network device determines, based on the capability message, that the terminal does not have the capability for QoE measurement, the OAM will also send a configuration QoE measurement message to the core network device. In other words, if the access network device determines, based on the capability message, that the terminal does not have the capability for QoE measurement, steps 102-103 will still be executed, but steps 104-108 will not be executed.

[0072] Step 103: The core network device sends an Activate QoE Measurement message to the access network device. Correspondingly, the access network device receives the Activate QoE Measurement message from the core network device.

[0073] The QoE measurement activation message includes QoE measurement configuration parameters.

[0074] In one possible implementation, the Activate QoE Measurement message can be an Activate QoE Measurement message sent by the core network device to the access network device.

[0075] It should be noted that after receiving the configuration QoE measurement message from OAM, the core network device generates an activation QoE measurement message based on the configuration QoE measurement message.

[0076] Step 104: The access network device sends a Radio Resource Control (RRC) message to the AS layer of the terminal. Correspondingly, the terminal's AS layer receives the RRC message from the access network device.

[0077] The radio resource control message includes QoE measurement configuration parameters.

[0078] It should be noted that radio resource control messages are sent from the access network device to the terminal in the form of radio resource control signaling.

[0079] In one possible implementation, the Radio Resource Control (RRC) message can be an RRC message sent by the access network device to the access layer of the terminal.

[0080] Step 105: The terminal AS layer sends mobile terminal commands to the terminal application (APP) layer. Correspondingly, the terminal APP layer receives the mobile terminal commands from the terminal's AS layer.

[0081] The mobile terminal commands include QoE measurement configuration parameters.

[0082] In one possible implementation, the mobile terminal command could be an Access Terminate command.

[0083] Step 106: The terminal APP layer sends mobile terminal commands to the terminal AS layer. Correspondingly, the terminal AS layer receives the mobile terminal commands from the terminal APP layer.

[0084] Among them, the mobile terminal command is used to instruct the terminal APP layer to report the QoE measurement report to the terminal's AS layer.

[0085] In one possible implementation, the QoE measurement message can be configured as an Access Terminate command.

[0086] It should be noted that after the terminal's APP layer receives the mobile terminal command, which includes QoE measurement configuration parameters, sent from the terminal's AS layer, the terminal performs QoE measurement according to the QoE measurement configuration parameters and generates a QoE measurement report.

[0087] Step 107: The terminal AS layer sends a Radio Resource Control (RRC) message to the access network device. Correspondingly, the access network device receives the RRC message from the terminal AS layer.

[0088] The radio resource control message includes a QoE measurement report.

[0089] In one possible implementation, the Radio Resource Control (RRC) message can be an RRC message sent by the terminal's AS layer to the access network device.

[0090] Step 108: The access network device sends a QoE measurement report to the terminal control element (TCE) / media access control element (MCE). Correspondingly, the TCE / MCE receives the QoE measurement report from the access network device.

[0091] In one possible implementation, the configured QoE measurement message can be a QoE Report sent by the access network device to the TCE / MCE.

[0092] The above provides a detailed explanation of the signaling-based QoE measurement process. The following section provides a detailed explanation of management-based QoE measurement.

[0093] 1.2 Management-Based QoE Measurement

[0094] Managed QoE measurement refers to QoE measurement performed on all terminals connected to a specific access network device, and managed QoE measurement is mostly used in the post-processing stage (i.e., the next stage after the pre-processing stage is completed).

[0095] like Figure 2 As shown, the management-based QoE measurement process includes the following steps 201 to 207.

[0096] Step 201: The terminal's AS layer sends a capability message to the access network device. Correspondingly, the access network device receives the capability message sent from the terminal's AS layer.

[0097] It should be noted that step 201 is similar to step 101 above, and can be understood by referring to step 101 above. It will not be repeated here.

[0098] Step 202: OAM sends an Activate QoE Measurement message to the access network device. Correspondingly, the access network device receives the Activate QoE Measurement message from OAM.

[0099] The QoE measurement activation message carries QoE measurement configuration parameters.

[0100] In one possible implementation, the QoE measurement activation message can be the Activate QoE Measurement message sent by the OAM to the access network device.

[0101] It should be noted that the difference between step 202 and step 102 above is that step 201 can directly send the activation QoE measurement message to the access network device via OAM; while step 102 requires OAM to first send a configuration QoE measurement message to the core network device, and then the core network device generates the activation QoE measurement message based on the configuration QoE measurement message and sends the activation QoE measurement message to the access network device. Since managed QoE measurement does not require message relay by the core network device, the activation QoE measurement message can be directly sent from OAM to the access network device.

[0102] Step 203: The access network device sends a Radio Resource Control (RRC) message to the AS layer of the terminal. Correspondingly, the terminal's AS layer receives the RRC message from the access network device.

[0103] It should be noted that step 203 is similar to step 104 above, and can be understood by referring to step 104 above, so it will not be repeated here.

[0104] Step 204: The terminal AS layer sends a mobile terminal command to the terminal APP layer. Correspondingly, the terminal APP layer receives the mobile terminal command from the terminal's AS layer.

[0105] It should be noted that step 204 is similar to step 105 above, and can be understood by referring to step 105 above, so it will not be repeated here.

[0106] Step 205: The terminal APP layer sends mobile terminal commands to the terminal AS layer. Correspondingly, the terminal AS layer receives the mobile terminal commands from the terminal APP layer.

[0107] It should be noted that step 205 is similar to step 106 above, and can be understood by referring to step 106 above, so it will not be repeated here.

[0108] Step 206: The terminal AS layer sends a Radio Resource Control (RRC) message to the access network device. Correspondingly, the access network device receives the RRC message from the terminal AS layer.

[0109] It should be noted that step 206 is similar to step 107 above, and can be understood by referring to step 107 above, so it will not be repeated here.

[0110] Step 207: The access network device sends a QoE measurement report to the TCE / MCE. Correspondingly, the TCE / MCE receives the QoE measurement report from the access network device.

[0111] It should be noted that step 207 is similar to step 108 above, and can be understood by referring to step 108 above, so it will not be repeated here.

[0112] The above is a brief introduction to some of the concepts involved in the embodiments of this application.

[0113] It should be noted that this application mainly involves signaling-based QoE measurement, as described in steps 101-108. The main purpose of signaling-based QoE measurement is to send a configuration message from an OAM to the core network and then to the NG-RAN (also known as gNB), enabling terminals matching the unique ID in the configuration message to perform QoE configuration. In other words, the NG-RAN forwards the received configuration message with the terminal identifier to the target terminal, thereby initiating QoE measurement.

[0114] II. New Air Entrance

[0115] NR stands for New Radio, also known as New Air Interface / New Wireless, which is the wireless network of 5G.

[0116] Mobile communication technology can generally be divided into two parts: the wireless network and the core network. 5G's wireless network technology has undergone significant changes. In fact, it is precisely the introduction of new wireless network technologies that enables 5G to achieve speeds far exceeding 4G. Therefore, 5G's wireless network is called NR, a completely new air interface (wireless). Because the wireless network is indeed crucial in 5G, 5G is sometimes directly referred to as NR, and many articles use NR to refer to 5G.

[0117] 5G NR is a global 5G standard based on a completely new air interface design using OFDM, and it is also a very important foundation for the next generation of cellular mobile technology. The sub-6GHz 5G NR prototype system and test platform launched in October 2016 was a crucial step towards the commercialization of 5G. The 6GHz frequency band is a key factor in achieving high-quality 5G coverage and will utilize numerous technologies.

[0118] III. Dual Connection

[0119] Dual Connectivity (DC)

[0120] This means that when a mobile phone or other terminal is in a connected state, it can simultaneously use the wireless resources of at least two different base stations (divided into master station and slave station).

[0121] Dual connectivity introduces the concept of "split transmission," which means that data is split between two base stations at the Packet Data Convergence Protocol (PDCP) layer. The PDCP layer on the user plane of the master station is responsible for functions such as Packet Data Unit (PDU) numbering, data splitting and aggregation between the master and slave stations.

[0122] IV. Main base station and auxiliary base station

[0123] In the NR-DC architecture, the master base station is called MN (Master Node) and the secondary base station is called SN (Secondary Node).

[0124] (1) For example, such as Figure 3 As shown, the process for adding a SN in an NR-DC network is as follows:

[0125] Step 301: MN sends an add request message to SN.

[0126] Understandably, in step 301, MN decides to add an SN as a secondary node, and MN sends an SN Addition Request message (specifically, an SN Addition Request) to the target SN to be added.

[0127] Step 302: SN sends an add request response message to MN.

[0128] Understandably, in step 302, the target SN replies with an SN Addition Request Acknowledge response (specifically, an SNAddition Request Acknowledge) to the MN.

[0129] Optionally, step 302 may be followed by step 302a:

[0130] Step 302a: SN sends a data transmission address message to MN.

[0131] Understandably, in step 302a, the target SN sends a data transmission address message (specifically, Xn-U Address Indication) to the MN.

[0132] Step 303: MN sends an RRC reconfiguration message to UE.

[0133] It is understandable that step 303 is the process by which the MN sends an RRC reconfiguration message (specifically an RRC Reconfiguration Message) to the UE to add the SN after receiving the SN addition request response from the SN side.

[0134] Step 304: The UE sends an RRC reconfiguration complete message to the MN.

[0135] It is understandable that in step 304, after the UE completes the RRC reconfiguration process, it sends an RRC reconfiguration complete message (specifically, an RRC Reconfiguration Complete Message) to the MN.

[0136] Step 305: MN sends a reconfiguration complete message to SN.

[0137] Understandably, in step 305, the MN will notify the target SN of the UE reconfiguration complete message (specifically, SNReconfiguration Complete).

[0138] Step 306: The UE randomly accesses the target SN.

[0139] It is understandable that in step 306, after the UE randomly accesses the target SN, it completes the random access process with the target SN.

[0140] Step 307: MN sends a secondary base station status transfer message to SN (specifically, SN Status Transfer).

[0141] Step 308: The user plane function (UPF) forwards data with the MN and SN.

[0142] It should be noted that the specific process of data forwarding between UPF and MN / SN is existing technology and will not be described in detail here.

[0143] Steps 309-312: The access and mobility management function (AMF) performs user plane path update with the UPF, MN, and SN.

[0144] It should be noted that the specific process of updating user plane paths between AMF, UPF, MN, and SN is existing technology and will not be described in detail here.

[0145] The above describes the process of adding a SN in NR-DC networking.

[0146] (2) For information transmission of UE in NR-DC architecture, if SN has been successfully added at this time, the following rules shall be followed:

[0147] 2.1 If SRB3 is configured during SN establishment and the secondary cell group (SCG) is not deactivated, the SN can directly transmit RRC messages to the UE through SRB3, including reconfiguration messages and RRC reconfiguration completion messages.

[0148] 2.2 If SRB3 is not configured, MN sends the SN's RRC message to the UE via SRB1. Simultaneously, the UE reports the RRC message via SRB1 encapsulated in the ULInformationTransferMRDC message. After receiving the ULInformationTransferMRDC message, MN can transmit the required RRC message to the SN through the Xn interface via the RRC transfer procedure.

[0149] (3) For example, the RRC Transfer process mentioned above is as follows: Figure 4 As shown, the specific steps involve transmitting RRC messages between 5G radio access network nodes (NG-RAN nodes) of MN or SN.

[0150] For example, the following messages are already supported by existing 3rd Generation Partnership Project (3GPP) protocols:

[0151] 3.1. the NR RRC message container with the NR measurements;

[0152] 3.2. the E-UTRA RRC message container with the E-UTRA measurements;

[0153] 3.3. the NR RRC message container with the NR failure information;

[0154] 3.4. the NR RRC message container with the RRCReconfigurationCompletemessage;

[0155] 3.5. the NR RRC message container with the UE assistance information.

[0156] (4) For information transmission of UE in NR-DC architecture, if SN is not added, that is, only MN exists, the following rules shall be followed:

[0157] 4.1 MN sends its RRC message to UE through SRB1, and UE reports the RRC message through SRB1 at the same time.

[0158] For QoE configuration and reporting message transmission in SA architecture, the base station (gNB) sends a QoE configuration message to the UE via the RRC reconfiguration message in SRB1, and the UE reports the QoE report to the base station (gNB) via the Measurement Report App Layer message in SRB4. Therefore, it can be seen that in the NR-DC network, if the SN is not added successfully, QoE can directly upload the report to the gNB, i.e., the MN, via SRB4.

[0159] 4.2 Regarding RRC signaling scheduling priority: SRB1 and SRB3 have the same priority, while SRB4 has a lower priority than both SRB1 and SRB3.

[0160] The above provides an introduction to the technical terms and background technology involved in this application.

[0161] As can be seen from the above introduction of the background technology, in the NR-DC network, if the SN is successfully added, the SN's RRC signaling is reported directly to the SN via SRB3 or directly to the MN via SRB1, and then transmitted to the SN by the MN.

[0162] However, the existing QoE measurement reporting mechanism can only carry RRC signaling via the lower-priority SRB4 and upload reports to the base station, which conflicts with the signaling scheduling of NR-DC. MN-related reports are always slower than SN-related QoE measurement reports due to the lower scheduling priority of SRB4. For some higher-priority MN-related QoE measurement configurations, the existing mechanism actually reduces the priority of MN-related QoE reports.

[0163] Furthermore, on the network management side, such as the OAM network element and the base station side, it is not possible to batch configure the QoE configuration of a certain type of service as MN or SN related. After receiving the QoE configuration, the UE is also unable to batch upload MN or SN related QoE reports for OAM to perform statistical analysis based on the service type.

[0164] In view of this, this application provides a QoE measurement configuration method and apparatus. By including mrdc-MN Measurement information in the QoE configuration process sent from the base station to the UE, it distinguishes between MN-related and SN-related QoE measurements, thereby enabling user experience collection for primary / secondary nodes. Simultaneously, since the QoE configuration report sent by the UE to the gNB includes mrdc-MN Measurement information, the UE can distinguish between MN-related and SN-related QoE reporting and perform user experience report reporting for primary / secondary nodes.

[0165] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0166] like Figure 3 As shown, Figure 5 A schematic diagram of a communication system 50 provided in an embodiment of this application is shown. The communication system 50 may include: an access network device 501 and a terminal device 502.

[0167] Access network device 501 is a device located on the access network side of the aforementioned communication system 50, and has wireless transceiver capabilities, or a chip or chip system that can be installed in the device. Access network device 501 includes, but is not limited to: access points (APs) in WiFi systems, such as home gateways, routers, servers, switches, bridges, etc.; evolved NodeBs (eNBs), radio network controllers (RNCs), NodeBs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved NodeBs, or home NodeBs, HNBs), base band units (BBUs), wireless relay nodes, wireless backhaul nodes, transmission and reception points (TRPs or transmission points, TPs), etc., and can also be 5G base stations, such as New Radio (NR). Access network equipment 501 can refer to gNBs in NR (Radio over NodeB) systems, or transmission points (TRPs or TPs), antenna panels (including multiple antenna panels) of base stations in 5G systems, or network nodes constituting gNBs or transmission points, such as baseband units (BBUs), distributed units (DUs), roadside units (RSUs) with base station functionality, or 5G access network (NG radioaccess network, NG-RAN) equipment. Access network equipment 501 also includes base stations in different networking modes, such as master evolved NodeBs (MeNBs) and secondary eNBs (SeNBs, or secondary gNBs, SgNBs). Access network equipment 501 also includes different types, such as terrestrial base stations, airborne base stations, and satellite base stations.

[0168] Optionally, the access network device 501 may include: a first access network device 501 and a second access network device 501.

[0169] Terminal equipment 502 is a device with wireless communication capabilities that can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted. It can also be deployed on water (such as on ships) or in the air (e.g., on airplanes, balloons, and satellites). Terminal equipment 502 is also known as user equipment (UE), mobile station (MS), mobile terminal (MT), and terminal, and is a device that provides voice and / or data connectivity to users. For example, terminal equipment 502 includes handheld devices and vehicle-mounted devices with wireless connectivity. Currently, terminal device 502 can be: mobile phone, tablet computer, laptop computer, PDA, mobile internet device (MID), wearable device (e.g., smartwatch, smart bracelet, pedometer, etc.), in-vehicle device (e.g., car, bicycle, electric vehicle, airplane, ship, train, high-speed rail, etc.), virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, smart home device (e.g., refrigerator, television, air conditioner, electricity meter, etc.), smart robot, workshop equipment, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, or wireless terminal in smart home, flying device (e.g., smart robot, hot air balloon, drone, airplane), etc. In one possible application scenario of this application, the terminal device is a terminal device that frequently operates on the ground, such as an in-vehicle device. In this application, for ease of description, the chip deployed in the above-mentioned device, such as a system-on-a-chip (SOC), a baseband chip, or other chip with communication functions, may also be referred to as terminal device 502.

[0170] Optionally, the terminal device 502 can be an embedded communication device or a user handheld communication device, including mobile phones, tablets, etc.

[0171] As an example, in this embodiment, the terminal device 502 can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0172] It should be noted that the electronic device may include the first access network device 501 and the terminal device 502 mentioned above.

[0173] It should be noted that, Figure 5 This is just an example framework diagram. Figure 5 The number of nodes included is unlimited, and except for Figure 5 In addition to the functional nodes shown, other nodes may also be included, such as OAM devices and core network devices, and this application does not impose any restrictions on this.

[0174] OAM (Operational Management) equipment refers to functional network elements that operate, manage, and maintain communication networks according to the actual needs of network operation by operators. Operation mainly refers to the analysis, prediction, planning, and configuration of the communication network and its services. Management mainly refers to the management and monitoring of data within the communication network. Maintenance mainly refers to the testing and fault management of the communication network and its services.

[0175] The OAM device is used to generate QoE measurement range information for access network device 501 and send the QoE measurement range information of access network device 501 to access network device 501. The QoE measurement range information can be carried within the activated QoE measurement information.

[0176] In one possible implementation, the OAM device connects to the access network device 501 wirelessly. The access network device 501 can connect to the terminal device 502 via a wired connection or wirelessly.

[0177] The aforementioned core network equipment may include at least one of the following network element functional entities: access and mobility management function (AMF), session management function (SMF), user plane function (UPF), authentication server function (AUSF), network slice selection function (NSSF), network exposure function (NEF), policy control function (PCF), and unified data management (UDM).

[0178] The specific functions of the aforementioned network element functional entities are as follows: AMF is responsible for user access and mobility management; SMF is responsible for user session management; AUSF is responsible for authenticating user 3GPP and non-3GPP access; UPF is responsible for user plane processing; NSSF is responsible for selecting the network slice used by user services; NEF is responsible for opening up the capabilities of the 5G network to external systems; PCF is responsible for user policy control, including session policies, mobility policies, etc.; and UDM is responsible for user subscription data management.

[0179] Terminal device 502 is used to send the target value of terminal device 502 to access network device 501.

[0180] The target values ​​of terminal device 502 include at least one of the following: the average speed of terminal device 502 during the target time period and the number of cells that terminal device 502 hands over during the target time period.

[0181] Access network device 501 is used to acquire QoE measurement range information and target values ​​of target terminal devices, and determine the QoE measurement range of target terminal devices based on multiple QoE measurement ranges and target values ​​of target terminal devices.

[0182] The QoE measurement range information is used to indicate multiple QoE measurement ranges.

[0183] In one possible implementation, the aforementioned QoE measurement range information is obtained by the access network device 501 from the OAM device. In this case, the QoE measurement is a managed QoE measurement.

[0184] In another possible implementation, the QoE measurement range information mentioned above is obtained by the access network device 501 from the core network device. In this case, the QoE measurement is a signaling-based QoE measurement.

[0185] The communication system 50 provided in this application embodiment can be various communication systems, such as: code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency-division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and other systems. The term "system" can be used interchangeably with "network." A CDMA system can implement wireless technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. UTRA can include wideband CDMA (WCDMA) technology and other CDMA variants. CDMA2000 can cover interim standard (IS) 2000 (IS-2000), IS-95, and IS-856 standards. A TDMA system can implement wireless technologies such as Global System for Mobile Communication (GSM). OFDMA systems can implement wireless technologies such as Evolved Universal Radio Terrestrial Access (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash OFDMA. UTRA and E-UTRA are UMTS and its evolved versions, respectively. 3GPP's Long Term Evolution (LTE) and various versions based on LTE are newer versions of UMTS using E-UTRA. 5G communication systems and New Radio (NR) are communication systems under investigation. Furthermore, the communication system can also be adapted to future-oriented communication technologies, all of which are applicable to the technical solutions provided in the embodiments of this application.

[0186] Furthermore, the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new communication systems, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0187] In this application, the access network device 501 may specifically be the main base station MN.

[0188] Specifically, MN sends first configuration information to terminal 502. This first configuration information instructs the terminal to perform QoE measurement. The first configuration information includes first indication information, which indicates the target base station corresponding to the QoE measurement.

[0189] Furthermore, depending on the specific circumstances, the access network device 501 is either the main base station MN or the auxiliary base station SN.

[0190] Scenario 1: If the target base station indicated by the first indication information is the main base station, then the access network device 501 is the main base station MN.

[0191] Scenario 2: If the target base station indicated by the first indication information is a secondary base station, and the signaling radio bearer SRB3 has been configured and the secondary cell group SCG has not been deactivated, then the access network device 501 is the secondary base station SN.

[0192] Scenario 3: If the target base station indicated by the first indication information is a secondary base station, and SRB3 has been configured and SCG has not been deactivated, then the access network device 501 is the primary base station MN.

[0193] For example, such as Figure 6 As shown, Figure 6 This application provides a flowchart illustrating a QoE measurement configuration method, which includes the following steps:

[0194] Step 601: The main base station sends the first configuration information to the terminal. Correspondingly, the terminal receives the first configuration information.

[0195] The first configuration information is used to instruct the terminal to perform QoE measurement. The first configuration information includes first indication information, which is used to instruct the terminal to perform QoE measurement on the target base station.

[0196] In one possible implementation, the first configuration message can be implemented as an App Layer Meas Config message, that is, the main base station sends the first configuration information to the terminal through an App Layer Meas Config message. The specific format of one type of App Layer Meas Config message involved in this application is described below:

[0197] App Layer Meas Config information element

[0198] -- ASN1START

[0199] -- TAG-APP LAYER MEAS CONFIG-START

[0200] App Layer Meas Config-r17 ::=SEQUENCE {

[0201] measConfigAppLayerToAddModList-r17SEQUENCE (SIZE(1..maxNrofAppLayerMeas-r17)) OF MeasConfigAppLayer-r17OPTIONAL, -- Need N

[0202] measConfigAppLayerToReleaseList-r17SEQUENCE (SIZE(1..maxNrofAppLayerMeas-r17)) OF MeasConfigAppLayerId-r17OPTIONAL, -- Need N

[0203] rrc-SegAllowed-r17ENUMERATED {enabled}OPTIONAL, -- Need M ...

[0204] }

[0205] MeasConfigAppLayer-r17 ::=SEQUENCE {

[0206] measConfigAppLayerId-r17MeasConfigAppLayerId-r17,

[0207] measConfigAppLayerContainer-r17OCTET STRING (SIZE (1..8000))OPTIONAL,-- Need N

[0208] mrdc-MN MeasurementBOOLEAN, -- Need M

[0209] serviceType-r17ENUMERATED {streaming, mtsi, vr, spare5, spare4,spare3, spare2, spare1}OPTIONAL, -- Need M

[0210] pauseReportingBOOLEAN,

[0211] transmissionOfSessionStartStopBOOLEAN,

[0212] ran-VisibleParameters-r17SetupRelease {RAN-VisibleParameters-r17}OPTIONAL, -- Need M ...

[0213] }

[0214] RAN-VisibleParameters-r17 ::=SEQUENCE {

[0215] ran-VisiblePeriodicityENUMERATED {ms120, ms240, ms480, ms640, ms1024}OPTIONAL, -- Need S

[0216] numberOfBufferLevelEntriesINTEGER (1..8)OPTIONAL, -- Need R

[0217] reportInitialPlayOutDelayBOOLEAN, ...

[0218] }

[0219] -- TAG-APP LAYER MEAS CONFIG-STOP

[0220] -- ASN1STOP

[0221] The above describes the format of the App Layer Meas Config message.

[0222] The following explains the function of each field in the App Layer Meas Config message:

[0223] (1) measConfigAppLayerContainer field

[0224] This field contains the configuration for application layer measurements, see Appendix L (Normative) of TS 26.247

[68] , Clause 16.5 of TS 26.114

[69] and TS 26.118

[70] .

[0225] (2) mrdc-MN Measurement field

[0226] This field indicates whether the application layer measurement is related to MN.

[0227] (3) numberOfBufferLevelEntries field

[0228] This field contains the maximum number of buffer-level entries that can be reported for RAN-visible application layer measurements.

[0229] (4) pauseReporting field

[0230] This field indicates whether the transmission of measReportAppLayerContainer is paused.

[0231] (5) ran-VisiblePeriodicity field

[0232] This field indicates the periodicity of RAN visible reports. A value of ms120 indicates a period of 120 milliseconds, a value of ms240 indicates a period of 240 milliseconds, and so on. If no value is specified and the endpoint is configured to provide RAN visible reports, the same period indicated in the measConfigAppLayerContainer field is used.

[0233] (6) reportInitialPlayoutDelay field

[0234] This field indicates whether the terminal should report the initial playback delay measured by the RAN-visible application layer.

[0235] (7) rrc-SegAllowed field

[0236] When this field is received in the MeasConfigAApp Layer Meas ConfigList, it indicates that RRC segmentation of the Measurement Report App Layer is permitted. It can only appear if the UE supports RRC message segmentation.

[0237] (8) serviceType field

[0238] This field indicates the type of application layer metrics. A value of streaming indicates the set of experience quality metrics for streaming services (see TS 26.247

[68] ); a value of mtsi indicates the set of experience quality metrics for mtsi (see TS26.114

[69] ); and a value of vr indicates the set of experience quality metrics for vr services (see TS 26.118

[70] ). When initially configuring application layer metrics and in fullConfig, the network always configures serviceType.

[0239] (9) transmissionOfSessionStartStop field

[0240] This field indicates whether the terminal should send an indication when a session begins and ends in the application layer. If a session has already started in the application layer, the terminal sends a session start indication when this field is configured.

[0241] The above describes the function of each field in the App Layer Meas Config message involved in this application.

[0242] It should be noted that the first indication information in this embodiment can be the mrdc-MN Measurement field information in the App Layer Meas Config message. This mrdc-MN Measurement field information is used to indicate whether the application layer measurement is related to MN.

[0243] For example, if the mrdc-MN Measurement field information is set to TRUE, the application layer measurement value is related to MN. If the mrdc-MN Measurement field information is set to FALSE, the application layer measurement value is related to SN.

[0244] In other words, in one possible implementation, the mrdc-MN Measurement field in the App Layer Meas Config message has been improved in this application embodiment so that the terminal receiving the first configuration message can know whether the QoE configuration corresponding to the first indication information is MN-related or SN-related.

[0245] Step 602: The terminal sends a QoE measurement report to the target base station according to the first configuration message.

[0246] Optionally, after receiving the first configuration message, the terminal executes the QoE measurement procedure. It should be noted that the specific procedure for the terminal to execute the QoE measurement can be found in steps 101-108 above, and will not be repeated here.

[0247] Optionally, the target base station can be a primary base station MN or a secondary base station SN.

[0248] In one possible implementation, referring to the example in step 601, taking the first configuration message as an App LayerMeas Config message and the first indication information as the mrdc-MN Measurement field information as an example, the terminal can determine whether to send the QoE measurement report to the primary base station or the secondary base station based on three situations, as follows:

[0249] Case 1: The value of the mrdc-MN Measurement field is TRUE.

[0250] In this case, if the value of the mrdc-MN Measurement field in the App Layer Meas Config message is TRUE, then after the terminal receives the App Layer Meas Config message, it determines that the QoE measurement configuration of the corresponding measConfigAppLayerId is related to the main base station MN.

[0251] Subsequently, after completing the collection of QoE measurement reports, the terminal uploads the QoE measurement report corresponding to measConfigAppLayerId to the main base station MN.

[0252] Scenario 2: The value of the mrdc-MN Measurement field is FALSE, and SRB3 is configured and SCG is not deactivated.

[0253] In this case, if the value of the mrdc-MN Measurement field in the App Layer Meas Config message is FALSE, then after the terminal receives the App Layer Meas Config message, it determines that the QoE measurement configuration of the corresponding measConfigAppLayerId is related to the secondary base station SN.

[0254] Furthermore, since SRB3 is configured and SCG is not deactivated, the terminal directly uploads the QoE measurement report corresponding to measConfigAppLayerId to the secondary base station SN, or first uploads the QoE measurement report to the primary base station MN and then to the secondary base station SN. That is, the secondary base station SN ultimately receives the QoE measurement report sent by the terminal.

[0255] Case 3: The value of the mrdc-MN Measurement field is FALSE, and SRB3 is not configured or SCG has been deactivated.

[0256] In this case, if the value of the mrdc-MN Measurement field in the App Layer Meas Config message is FALSE, then after the terminal receives the App Layer Meas Config message, it determines that the QoE measurement configuration of the corresponding measConfigAppLayerId is related to the secondary base station SN.

[0257] However, since SRB3 is not configured or SCG has been deactivated, the terminal will upload the QoE measurement report related to the secondary base station SN with the corresponding measConfigAppLayerId to the primary base station MN.

[0258] In one possible implementation, the terminal sends the QoE measurement report to the target base station within a Measurement Report App Layer message. Specifically, the QoE measurement report is sent to the primary base station MN or the secondary base station SN via the Measurement Report App Layer message.

[0259] Optionally, the Measurement Report App Layer message includes second indication information, which is used to indicate whether the target base station related to the QoE measurement report is the primary base station MN or the secondary base station SN.

[0260] The following describes the specific format of a Measurement Report App Layer message involved in this application:

[0261] Measurement Report App Layer message

[0262] -- ASN1START

[0263] -- TAG-MEASUREMENT REPORT APP LAYER-START

[0264] Measurement Report App Layer-r17 ::=SEQUENCE {

[0265] criticalExtensionsCHOICE {

[0266] Measurement Report App LayerList-r17SEQUENCE (SIZE(1..maxNrofAppLayerMeas-r17)) OF Measurement Report App Layer-r17-IEs,

[0267] criticalExtensionsFutureSEQUENCE {}

[0268] }

[0269] }

[0270] Measurement Report App Layer-r17-IEs ::= SEQUENCE {

[0271] measConfigAppLayerId-r17MeasConfigAppLayerId-r17,

[0272] measReportAppLayerContainer-r17OCTET STRING OPTIONAL,

[0273] mrdc-MN MeasurementBOOLEAN,

[0274] appLayerSessionStatus-r17ENUMERATED {started, stopped}OPTIONAL,

[0275] ran-VisibleMeasurements-r17RAN-VisibleMeasurements-r17OPTIONAL,

[0276] lateNonCriticalExtensionOCTET STRINGOPTIONAL,

[0277] nonCriticalExtensionSEQUENCE{}OPTIONAL

[0278] }

[0279] RAN-VisibleMeasurements-r17 ::=SEQUENCE {

[0280] appLayerBufferLevelList-r17SEQUENCE (SIZE (1..8)) OFAppLayerBufferLevel-r17OPTIONAL,

[0281] initialPlayoutDelay-r17INTEGER (0..30000)OPTIONAL,

[0282] pdu-SessionIdList-r17SEQUENCE (SIZE (1..maxNrofPDU-Sessions-r17)) OFPDU-SessionIDOPTIONAL, ...

[0283] }

[0284] AppLayerBufferLevel-r17 ::= INTEGER (0..30000)

[0285] -- TAG-MEASUREMENT REPORT APP LAYER-STOP

[0286] -- ASN1STOP

[0287] The above describes the format of Measurement Report App Layer messages.

[0288] It should be noted that in the Measurement Report App Layer message, the mrdc-MN Measurement field is used to indicate whether the base station associated with the QoE measurement report is the primary base station (MN) or the secondary base station (SN). That is, the mrdc-MN Measurement field can serve as the second indication information described above.

[0289] Based on the above technical solution, this application includes mrdc-MN Measurement information in the QoE configuration message sent by the primary base station MN to the terminal. This information is used to distinguish between QoE measurements related to the primary base station MN and those related to the secondary base station SN, thereby enabling user experience collection for primary / secondary nodes. Simultaneously, since the terminal's QoE configuration report sent to the primary base station MN includes mrdc-MN Measurement information, the primary base station can distinguish between MN-related and SN-related QoE reports and report user experience reports for primary / secondary nodes. Therefore, this application can flexibly report QoE measurement configurations of different priorities, and the network can distinguish between QoE measurement reports related to MN or SN services.

[0290] For example, combined Figure 6 ,like Figure 7 As shown, the QoE measurement configuration method provided in this application may specifically include the following steps:

[0291] Step 701: The main base station sends the first configuration information to the terminal. Correspondingly, the terminal receives the first configuration information.

[0292] The first configuration information is used to instruct the terminal to perform QoE measurement. The first configuration information includes first indication information, which is used to instruct the terminal to perform QoE measurement on the target base station.

[0293] In one possible implementation, the main base station sends first configuration information to the terminal via an App Layer Meas Config message. The specific format of one such App Layer Meas Config message is described below:

[0294] App Layer Meas Config information element

[0295] -- ASN1START

[0296] -- TAG-APP LAYER MEAS CONFIG-START

[0297] App Layer Meas Config-r17 ::=SEQUENCE {

[0298] measConfigAppLayerToAddModList-r17SEQUENCE (SIZE(1..maxNrofAppLayerMeas-r17)) OF MeasConfigAppLayer-r17OPTIONAL, -- Need N

[0299] measConfigAppLayerToReleaseList-r17SEQUENCE (SIZE(1..maxNrofAppLayerMeas-r17)) OF MeasConfigAppLayerId-r17OPTIONAL, -- Need N

[0300] rrc-SegAllowed-r17ENUMERATED {enabled}OPTIONAL, -- Need M ...

[0301] }

[0302] MeasConfigAppLayer-r17 ::=SEQUENCE {

[0303] measConfigAppLayerId-r17MeasConfigAppLayerId-r17,

[0304] measConfigAppLayerContainer-r17OCTET STRING (SIZE (1..8000))OPTIONAL,-- Need N

[0305] mrdc-MN MeasurementBOOLEAN, -- Need M

[0306] serviceType-r17ENUMERATED {streaming, mtsi, vr, spare5, spare4,spare3, spare2, spare1}OPTIONAL, -- Need M

[0307] pauseReportingBOOLEAN,

[0308] transmissionOfSessionStartStopBOOLEAN,

[0309] ran-VisibleParameters-r17SetupRelease {RAN-VisibleParameters-r17}OPTIONAL, -- Need M ...

[0310] }

[0311] RAN-VisibleParameters-r17 ::=SEQUENCE {

[0312] ran-VisiblePeriodicityENUMERATED {ms120, ms240, ms480, ms640, ms1024}OPTIONAL, -- Need S

[0313] numberOfBufferLevelEntriesINTEGER (1..8)OPTIONAL, -- Need R

[0314] reportInitialPlayOutDelayBOOLEAN, ...

[0315] }

[0316] -- TAG-APP LAYER MEAS CONFIG-STOP

[0317] -- ASN1STOP

[0318] The above describes the format of the App Layer Meas Config message.

[0319] The following explains the function of each field in the App Layer Meas Config message:

[0320] (1) measConfigAppLayerContainer field

[0321] This field contains the configuration for application layer measurements, see Appendix L (Normative) of TS 26.247

[68] , Clause 16.5 of TS 26.114

[69] and TS 26.118

[70] .

[0322] (2) mrdc-MN Measurement field

[0323] This field indicates whether the application layer measurement is related to MN.

[0324] (3) numberOfBufferLevelEntries field

[0325] This field contains the maximum number of buffer-level entries that can be reported for RAN-visible application layer measurements.

[0326] (4) pauseReporting field

[0327] This field indicates whether the transmission of measReportAppLayerContainer is paused.

[0328] (5) ran-VisiblePeriodicity field

[0329] This field indicates the periodicity of RAN visible reports. A value of ms120 indicates a period of 120 milliseconds, a value of ms240 indicates a period of 240 milliseconds, and so on. If no value is specified and the endpoint is configured to provide RAN visible reports, the same period indicated in the measConfigAppLayerContainer field is used.

[0330] (6) reportInitialPlayoutDelay field

[0331] This field indicates whether the terminal should report the initial playback delay measured by the RAN-visible application layer.

[0332] (7) rrc-SegAllowed field

[0333] When this field is received in the MeasConfigAApp Layer Meas ConfigList, it indicates that RRC segmentation of the Measurement Report App Layer is permitted. It can only appear if the UE supports RRC message segmentation.

[0334] (8) serviceType field

[0335] This field indicates the type of application layer metrics. A value of streaming indicates the set of experience quality metrics for streaming services (see TS 26.247

[68] ); a value of mtsi indicates the set of experience quality metrics for mtsi (see TS26.114

[69] ); and a value of vr indicates the set of experience quality metrics for vr services (see TS 26.118

[70] ). When initially configuring application layer metrics and in fullConfig, the network always configures serviceType.

[0336] (9) transmissionOfSessionStartStop field

[0337] This field indicates whether the terminal should send an indication when a session begins and ends in the application layer. If a session has already started in the application layer, the terminal sends a session start indication when this field is configured.

[0338] The above describes the function of each field in the App Layer Meas Config message involved in this application.

[0339] It should be noted that the first indication information in this embodiment can be the mrdc-MN Measurement field information in the App Layer Meas Config message. This mrdc-MN Measurement field information is used to indicate whether the application layer measurement is related to MN.

[0340] For example, if the mrdc-MN Measurement field information is set to TRUE, the application layer measurement value is related to MN. If the mrdc-MN Measurement field information is set to FALSE, the application layer measurement value is related to SN.

[0341] In other words, in one possible implementation, the mrdc-MN Measurement field in the App Layer Meas Config message has been improved in this application embodiment so that the terminal receiving the first configuration message can know whether the QoE configuration corresponding to the first indication information is MN-related or SN-related.

[0342] Step 702: After receiving the first instruction information, the terminal determines the target user corresponding to the QoE measurement.

[0343] Optionally, after receiving the first configuration message, the terminal determines the target user corresponding to the QoE measurement based on the first indication information contained therein. The target user includes both the primary base station user and the secondary base station user.

[0344] For example, the terminal determines the target user in the following two ways:

[0345] Scenario 1: If the target base station indicated by the first indication information is the main base station, then the terminal determines that the target user is the main base station user.

[0346] Scenario 2: If the target base station indicated by the first indication information is a secondary base station, then the terminal determines that the target user is a user of the secondary base station.

[0347] Step 703: The terminal performs QoE measurement on the target user and generates a QoE measurement report.

[0348] It should be noted that the specific process for performing QoE measurement on the terminal can be found in steps 101-108 above, and will not be repeated here.

[0349] Step 704: The terminal sends a QoE measurement report to the target base station according to the first configuration message.

[0350] Optionally, the target base station can be a primary base station MN or a secondary base station SN.

[0351] In one possible implementation, referring to the example in step 601, taking the first configuration message as an App LayerMeas Config message and the first indication information as the mrdc-MN Measurement field information as an example, the terminal can determine whether to send the QoE measurement report to the primary base station or the secondary base station based on three situations, as follows:

[0352] Case 1: The value of the mrdc-MN Measurement field is TRUE.

[0353] In this case, if the value of the mrdc-MN Measurement field in the App Layer Meas Config message is TRUE, then after the terminal receives the App Layer Meas Config message, it determines that the QoE measurement configuration of the corresponding measConfigAppLayerId is related to the main base station MN.

[0354] Subsequently, after completing the collection of QoE measurement reports, the terminal uploads the QoE measurement report corresponding to measConfigAppLayerId to the main base station MN.

[0355] Scenario 2: The value of the mrdc-MN Measurement field is FALSE, and SRB3 is configured and SCG is not deactivated.

[0356] In this case, if the value of the mrdc-MN Measurement field in the App Layer Meas Config message is FALSE, then after the terminal receives the App Layer Meas Config message, it determines that the QoE measurement configuration of the corresponding measConfigAppLayerId is related to the secondary base station SN.

[0357] Furthermore, since SRB3 is configured and SCG is not deactivated, the terminal directly uploads the QoE measurement report corresponding to measConfigAppLayerId to the secondary base station SN, or first uploads the QoE measurement report to the primary base station MN and then to the secondary base station SN. That is, the secondary base station SN ultimately receives the QoE measurement report sent by the terminal.

[0358] Case 3: The value of the mrdc-MN Measurement field is FALSE, and SRB3 is not configured or SCG has been deactivated.

[0359] In this case, if the value of the mrdc-MN Measurement field in the App Layer Meas Config message is FALSE, then after the terminal receives the App Layer Meas Config message, it determines that the QoE measurement configuration of the corresponding measConfigAppLayerId is related to the secondary base station SN.

[0360] However, since SRB3 is not configured or SCG has been deactivated, the terminal uploads the QoE measurement report related to the secondary base station SN with the corresponding measConfigAppLayerId to the primary base station MN. After this, the primary base station forwards the QoE measurement report related to the secondary base station SN to the secondary base station SN.

[0361] In one possible implementation, the terminal sends the QoE measurement report to the target base station within a Measurement Report App Layer message. Specifically, the QoE measurement report is sent to the primary base station MN or the secondary base station SN via the Measurement Report App Layer message.

[0362] Optionally, the Measurement Report App Layer message includes second indication information, which is used to indicate whether the target base station related to the QoE measurement report is the primary base station MN or the secondary base station SN.

[0363] The following describes the specific format of a Measurement Report App Layer message involved in this application:

[0364] Measurement Report App Layer message

[0365] -- ASN1START

[0366] -- TAG-MEASUREMENT REPORT APP LAYER-START

[0367] Measurement Report App Layer-r17 ::=SEQUENCE {

[0368] criticalExtensionsCHOICE {

[0369] Measurement Report App LayerList-r17SEQUENCE (SIZE(1..maxNrofAppLayerMeas-r17)) OF Measurement Report App Layer-r17-IEs,

[0370] criticalExtensionsFutureSEQUENCE {}

[0371] }

[0372] }

[0373] Measurement Report App Layer-r17-IEs ::= SEQUENCE {

[0374] measConfigAppLayerId-r17MeasConfigAppLayerId-r17,

[0375] measReportAppLayerContainer-r17OCTET STRINGOPTIONAL,

[0376] mrdc-MN MeasurementBOOLEAN,

[0377] appLayerSessionStatus-r17ENUMERATED {started, stopped}OPTIONAL,

[0378] ran-VisibleMeasurements-r17RAN-VisibleMeasurements-r17OPTIONAL,

[0379] lateNonCriticalExtensionOCTET STRINGOPTIONAL,

[0380] nonCriticalExtensionSEQUENCE{}OPTIONAL

[0381] }

[0382] RAN-VisibleMeasurements-r17 ::=SEQUENCE {

[0383] appLayerBufferLevelList-r17SEQUENCE (SIZE (1..8)) OFAppLayerBufferLevel-r17OPTIONAL,

[0384] initialPlayoutDelay-r17INTEGER (0..30000)OPTIONAL,

[0385] pdu-SessionIdList-r17SEQUENCE (SIZE (1..maxNrofPDU-Sessions-r17)) OFPDU-SessionIDOPTIONAL, ...

[0386] }

[0387] AppLayerBufferLevel-r17 ::= INTEGER (0..30000)

[0388] -- TAG-MEASUREMENT REPORT APP LAYER-STOP

[0389] -- ASN1STOP

[0390] The above describes the format of Measurement Report App Layer messages.

[0391] It should be noted that in the Measurement Report App Layer message, the mrdc-MN Measurement field is used to indicate whether the base station associated with the QoE measurement report is the primary base station (MN) or the secondary base station (SN). That is, the mrdc-MN Measurement field can serve as the second indication information described above.

[0392] Based on the above technical solution, this application includes mrdc-MN Measurement information in the QoE configuration message sent by the primary base station MN to the terminal. This information is used to distinguish between QoE measurements related to the primary base station MN and those related to the secondary base station SN, thereby enabling user experience collection for primary / secondary nodes. Simultaneously, since the terminal's QoE configuration report sent to the primary base station MN includes mrdc-MN Measurement information, the primary base station can distinguish between MN-related and SN-related QoE reports and report user experience reports for primary / secondary nodes. Therefore, this application can flexibly report QoE measurement configurations of different priorities, and the network can distinguish between QoE measurement reports related to MN or SN services.

[0393] For example, combined Figure 7 ,like Figure 8 As shown, the QoE measurement configuration method provided in this application may specifically include the following steps:

[0394] Step 801: The main base station sends the first configuration information to the terminal. Correspondingly, the terminal receives the first configuration information.

[0395] The first configuration information is used to instruct the terminal to perform QoE measurement. The first configuration information includes first indication information, which is used to instruct the terminal to perform QoE measurement on the target base station.

[0396] In one possible implementation, the main base station sends first configuration information to the terminal via an App Layer Meas Config message. The specific format of one such App Layer Meas Config message is described below:

[0397] App Layer Meas Config information element

[0398] -- ASN1START

[0399] -- TAG-APP LAYER MEAS CONFIG-START

[0400] App Layer Meas Config-r17 ::=SEQUENCE {

[0401] measConfigAppLayerToAddModList-r17SEQUENCE (SIZE(1..maxNrofAppLayerMeas-r17)) OF MeasConfigAppLayer-r17OPTIONAL, -- Need N

[0402] measConfigAppLayerToReleaseList-r17SEQUENCE (SIZE(1..maxNrofAppLayerMeas-r17)) OF MeasConfigAppLayerId-r17OPTIONAL, -- Need N

[0403] rrc-SegAllowed-r17ENUMERATED {enabled}OPTIONAL, -- Need M ...

[0404] }

[0405] MeasConfigAppLayer-r17 ::=SEQUENCE {

[0406] measConfigAppLayerId-r17MeasConfigAppLayerId-r17,

[0407] measConfigAppLayerContainer-r17OCTET STRING (SIZE (1..8000))OPTIONAL,-- Need N

[0408] mrdc-MN MeasurementBOOLEAN, -- Need M

[0409] serviceType-r17ENUMERATED {streaming, mtsi, vr, spare5, spare4,spare3, spare2, spare1}OPTIONAL, -- Need M

[0410] pauseReportingBOOLEAN,

[0411] transmissionOfSessionStartStopBOOLEAN,

[0412] ran-VisibleParameters-r17SetupRelease {RAN-VisibleParameters-r17}OPTIONAL, -- Need M ...

[0413] }

[0414] RAN-VisibleParameters-r17 ::=SEQUENCE {

[0415] ran-VisiblePeriodicityENUMERATED {ms120, ms240, ms480, ms640, ms1024}OPTIONAL, -- Need S

[0416] numberOfBufferLevelEntriesINTEGER (1..8)OPTIONAL, -- Need R

[0417] reportInitialPlayOutDelayBOOLEAN, ...

[0418] }

[0419] -- TAG-APP LAYER MEAS CONFIG-STOP

[0420] -- ASN1STOP

[0421] The above describes the format of the App Layer Meas Config message.

[0422] The following explains the function of each field in the App Layer Meas Config message:

[0423] (1) measConfigAppLayerContainer field

[0424] This field contains the configuration for application layer measurements, see Appendix L (Normative) of TS 26.247

[68] , Clause 16.5 of TS 26.114

[69] and TS 26.118

[70] .

[0425] (2) mrdc-MN Measurement field

[0426] This field indicates whether the application layer measurement is related to MN.

[0427] (3) numberOfBufferLevelEntries field

[0428] This field contains the maximum number of buffer-level entries that can be reported for RAN-visible application layer measurements.

[0429] (4) pauseReporting field

[0430] This field indicates whether the transmission of measReportAppLayerContainer is paused.

[0431] (5) ran-VisiblePeriodicity field

[0432] This field indicates the periodicity of RAN visible reports. A value of ms120 indicates a period of 120 milliseconds, a value of ms240 indicates a period of 240 milliseconds, and so on. If no value is specified and the endpoint is configured to provide RAN visible reports, the same period indicated in the measConfigAppLayerContainer field is used.

[0433] (6) reportInitialPlayoutDelay field

[0434] This field indicates whether the terminal should report the initial playback delay measured by the RAN-visible application layer.

[0435] (7) rrc-SegAllowed field

[0436] When this field is received in the MeasConfigAApp Layer Meas ConfigList, it indicates that RRC segmentation of the Measurement Report App Layer is permitted. It can only appear if the UE supports RRC message segmentation.

[0437] (8) serviceType field

[0438] This field indicates the type of application layer metrics. A value of streaming indicates the set of experience quality metrics for streaming services (see TS 26.247

[68] ); a value of mtsi indicates the set of experience quality metrics for mtsi (see TS26.114

[69] ); and a value of vr indicates the set of experience quality metrics for vr services (see TS 26.118

[70] ). When initially configuring application layer metrics and in fullConfig, the network always configures serviceType.

[0439] (9) transmissionOfSessionStartStop field

[0440] This field indicates whether the terminal should send an indication when a session begins and ends in the application layer. If a session has already started in the application layer, the terminal sends a session start indication when this field is configured.

[0441] The above describes the function of each field in the App Layer Meas Config message involved in this application.

[0442] It should be noted that the first indication information in this embodiment can be the mrdc-MN Measurement field information in the App Layer Meas Config message. This mrdc-MN Measurement field information is used to indicate whether the application layer measurement is related to MN.

[0443] For example, if the mrdc-MN Measurement field information is set to TRUE, the application layer measurement value is related to MN. If the mrdc-MN Measurement field information is set to FALSE, the application layer measurement value is related to SN.

[0444] In other words, in one possible implementation, the mrdc-MN Measurement field in the App Layer Meas Config message has been improved in this application embodiment so that the terminal receiving the first configuration message can know whether the QoE configuration corresponding to the first indication information is MN-related or SN-related.

[0445] Step 802: After receiving the first instruction information, the terminal determines the target user corresponding to the QoE measurement.

[0446] Optionally, after receiving the first configuration message, the terminal determines the target user corresponding to the QoE measurement based on the first indication information contained therein. The target user includes both the primary base station user and the secondary base station user.

[0447] For example, the terminal determines the target user in the following two ways:

[0448] Scenario 1: If the target base station indicated by the first indication information is the main base station, then the terminal determines that the target user is the main base station user.

[0449] Scenario 2: If the target base station indicated by the first indication information is a secondary base station, then the terminal determines that the target user is a user of the secondary base station.

[0450] Step 803: The terminal performs QoE measurement on the target user and generates a QoE measurement report.

[0451] It should be noted that the specific process for performing QoE measurement on the terminal can be found in steps 101-108 above, and will not be repeated here.

[0452] It should be noted that after the terminal determines the QoE measurement report, based on the example in step 801 above where the first configuration message is implemented as the App Layer Meas Config message and the first indication information is implemented as the mrdc-MN Measurement field, the terminal sends the QoE measurement report to the target base station according to three different scenarios, specifically including the following steps 804a-804c:

[0453] Step 804a: The terminal sends a QoE measurement report to the main base station.

[0454] It should be noted that in this step, the value of the mrdc-MNMeasurement field in the App Layer Meas Config message received by the terminal is TRUE, which means that the QoE measurement configuration of the corresponding measConfigAppLayerId executed by the terminal is related to the main base station MN.

[0455] Therefore, the terminal sends a QoE measurement report to the main base station MN.

[0456] Step 804b: The terminal sends a QoE measurement report to the secondary base station.

[0457] It should be noted that in this step, the value of the mrdc-MNMeasurement field in the App Layer Meas Config message received by the terminal is FLASE, which means that the QoE measurement configuration corresponding to measConfigAppLayerId executed by the terminal is related to the secondary base station SN.

[0458] Furthermore, since SRB3 was already configured and SCG was not deactivated at this time, the terminal sent a QoE measurement report to the secondary base station SN.

[0459] Step 804c: The terminal sends a QoE measurement report to the primary base station, which then forwards the QoE measurement reports related to the secondary base station SN to the secondary base station SN.

[0460] It should be noted that in this step, the value of the mrdc-MNMeasurement field in the App Layer Meas Config message received by the terminal is FLASE, which means that the QoE measurement configuration corresponding to measConfigAppLayerId executed by the terminal is related to the secondary base station SN.

[0461] However, because SRB3 is not configured or SCG has been deactivated, the terminal sends a QoE measurement report to the primary base station MN. Subsequently, the primary base station forwards the QoE measurement reports related to the secondary base station SN to the secondary base station SN.

[0462] In one possible implementation, a QoE measurement report is sent to either the primary base station (MN) or the secondary base station (SN) via a Measurement Report App Layer message. Specifically, the mrdc-MNMeasurement field in the Measurement Report App Layer message indicates whether the base station associated with the QoE measurement report is the primary base station (MN) or the secondary base station (SN).

[0463] Therefore, after receiving the QoE measurement report sent by the terminal, the main base station determines whether the QoE measurement report is related to the secondary base station SN based on the value of the mrdc-MN Measurement field in the Measurement Report AppLayer message. If the QoE measurement report is related to the secondary base station SN, the main base station MN sends the QoE measurement report to the secondary base station SN.

[0464] In one possible implementation, the terminal sends the QoE measurement report to the target base station within a Measurement Report App Layer message. Specifically, the QoE measurement report is sent to the primary base station MN or the secondary base station SN via the Measurement Report App Layer message.

[0465] Optionally, the Measurement Report App Layer message includes second indication information, which is used to indicate whether the target base station related to the QoE measurement report is the primary base station MN or the secondary base station SN.

[0466] The following describes the specific format of a Measurement Report App Layer message involved in this application:

[0467] Measurement Report App Layer message

[0468] -- ASN1START

[0469] -- TAG-MEASUREMENT REPORT APP LAYER-START

[0470] Measurement Report App Layer-r17 ::=SEQUENCE {

[0471] criticalExtensionsCHOICE {

[0472] Measurement Report App LayerList-r17SEQUENCE (SIZE(1..maxNrofAppLayerMeas-r17)) OF Measurement Report App Layer-r17-IEs,

[0473] criticalExtensionsFutureSEQUENCE {}

[0474] }

[0475] }

[0476] Measurement Report App Layer-r17-IEs ::= SEQUENCE {

[0477] measConfigAppLayerId-r17MeasConfigAppLayerId-r17,

[0478] measReportAppLayerContainer-r17OCTET STRINGOPTIONAL,

[0479] mrdc-MN MeasurementBOOLEAN,

[0480] appLayerSessionStatus-r17ENUMERATED {started, stopped}OPTIONAL,

[0481] ran-VisibleMeasurements-r17RAN-VisibleMeasurements-r17OPTIONAL,

[0482] lateNonCriticalExtensionOCTET STRINGOPTIONAL,

[0483] nonCriticalExtensionSEQUENCE{}OPTIONAL

[0484] }

[0485] RAN-VisibleMeasurements-r17 ::=SEQUENCE {

[0486] appLayerBufferLevelList-r17SEQUENCE (SIZE (1..8)) OFAppLayerBufferLevel-r17OPTIONAL,

[0487] initialPlayoutDelay-r17INTEGER (0..30000)OPTIONAL,

[0488] pdu-SessionIdList-r17SEQUENCE (SIZE (1..maxNrofPDU-Sessions-r17)) OFPDU-SessionIDOPTIONAL, ...

[0489] }

[0490] AppLayerBufferLevel-r17 ::= INTEGER (0..30000)

[0491] -- TAG-MEASUREMENT REPORT APP LAYER-STOP

[0492] -- ASN1STOP

[0493] The above describes the format of Measurement Report App Layer messages.

[0494] It should be noted that in the Measurement Report App Layer message, the mrdc-MN Measurement field is used to indicate whether the base station associated with the QoE measurement report is the primary base station (MN) or the secondary base station (SN). That is, the mrdc-MN Measurement field can serve as the second indication information described above.

[0495] Step 805: The main base station sends a QoE measurement report to the Master Communication Equipment (MCE). Correspondingly, the MCE receives the QoE measurement report.

[0496] Understandably, after receiving all QoE measurement reports, the main base station MN sends the QoE report to the MCE. The specific implementation process of step 805 is prior art and will not be described in detail here.

[0497] Based on the above technical solution, this application includes mrdc-MN Measurement information in the QoE configuration message sent by the primary base station MN to the terminal. This information is used to distinguish between QoE measurements related to the primary base station MN and those related to the secondary base station SN, thereby enabling user experience collection for primary / secondary nodes. Simultaneously, since the terminal's QoE configuration report sent to the primary base station MN includes mrdc-MN Measurement information, the primary base station can distinguish between MN-related and SN-related QoE reports and report user experience reports for primary / secondary nodes. Therefore, this application can flexibly report QoE measurement configurations of different priorities, and the network can distinguish between QoE measurement reports related to MN or SN services.

[0498] This application embodiment can divide the QoE measurement configuration device into functional modules or functional units according to the above method example. For example, each function can be divided into a separate functional module or functional unit, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or in software functional modules or functional units. The module or unit division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0499] like Figure 9 The diagram shown is a structural schematic of a QoE measurement configuration device 900 provided in an embodiment of this application. The QoE measurement configuration device 900 includes: a receiving unit 901, a transmitting unit 902, and a processing unit 903.

[0500] The receiving unit 901 is configured to receive first configuration information from the main base station; wherein the first configuration information is used to instruct the terminal to perform QoE measurement, and the first configuration information includes first indication information, which is used to indicate the target base station corresponding to the terminal and the QoE measurement.

[0501] The sending unit 902 is used to send a QoE measurement report to the target base station according to the first configuration information; wherein the target base station includes the primary base station or the secondary base station.

[0502] Optionally, the sending unit 902 is further configured to send the QoE measurement report to the main base station when the target base station indicated by the first indication information is the main base station.

[0503] Optionally, the sending unit 902 is further configured to send the QoE measurement report to the secondary base station when the target base station indicated by the first indication information is the secondary base station, and the signaling radio bearer SRB3 has been configured and the secondary cell group SCG has not been deactivated.

[0504] Optionally, the sending unit 902 is further configured to send the QoE measurement report to the primary base station when the target base station indicated by the first indication information is the secondary base station, and SRB3 is not configured or SCG has been deactivated.

[0505] Optionally, the processing unit 903 is configured to determine the target user corresponding to the QoE measurement after receiving the first indication information;

[0506] Optionally, the processing unit 903 is configured to perform the QoE measurement on the target user and determine the QoE measurement report.

[0507] Optionally, the QoE measurement configuration device 900 may also include a storage unit ( Figure 9 (shown in dashed box) The storage unit stores a program or instruction. When the receiving unit 901, the sending unit 902, and the processing unit 903 execute the program or instruction, the QoE measurement configuration device can perform the QoE measurement configuration method described in the above method embodiment.

[0508] also, Figure 9 The technical effects of the QoE measurement configuration device 900 can be referred to the technical effects of the QoE measurement configuration method described in the above embodiments, and will not be repeated here.

[0509] For example, Figure 10 This is another possible structural schematic diagram of the QoE measurement configuration device 1000 involved in the above embodiments. For example... Figure 10 As shown, the QoE measurement configuration device 1000 includes a transmitting unit 1001 and a receiving unit 1002.

[0510] The sending unit 1001 is used to send first configuration information to the terminal; wherein the first configuration information is used to instruct the terminal to perform QoE measurement, and the first configuration information includes first indication information, which is used to indicate the target base station corresponding to the terminal and the QoE measurement.

[0511] The receiving unit 1002 is used to receive a QoE measurement report from the terminal.

[0512] Optionally, the QoE measurement configuration device 1000 may also include a storage unit ( Figure 10 (shown in dashed box) The storage unit stores a program or instruction. When the sending unit 1001 and the receiving unit 1002 execute the program or instruction, the QoE measurement configuration device can execute the QoE measurement configuration method described in the above method embodiment.

[0513] also, Figure 10 The technical effects of the QoE measurement configuration device 1000 can be referred to the technical effects of the QoE measurement configuration method described in the above embodiments, and will not be repeated here.

[0514] Figure 11 A possible structural schematic diagram of the QoE measurement configuration device involved in the above embodiments is shown. The QoE measurement configuration device 110 includes a processor 1102 and a communication interface 1103. The processor 1102 is used to control and manage the operation of the QoE measurement configuration device, for example, executing the steps performed by the receiving unit 901, transmitting unit 902, processing unit 903, and transmitting unit 1001 and receiving unit 1002, and / or performing other processes of the technology described herein. The communication interface 1103 is used to support communication between the QoE measurement configuration device and other network entities. The QoE measurement configuration device may also include a memory 1101 and a bus 1104. The memory 1101 is used to store the program code and data of the QoE measurement configuration device.

[0515] The memory 1101 may be a memory in a QoE measurement configuration device, and the memory may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as read-only memory, flash memory, hard disk or solid-state drive; the memory may also include a combination of the above types of memory.

[0516] The processor 1102 described above can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0517] Bus 1104 can be an Extended Industry Standard Architecture (EISA) bus, etc. Bus 1104 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 11 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0518] Figure 11 The QoE measurement configuration device can also be a chip. The chip includes one or more processors 1102 and a communication interface 1103.

[0519] In some embodiments, the chip further includes a memory 1101, which may include read-only memory and random access memory, and provides operation instructions and data to the processor 1102. A portion of the memory 1101 may also include non-volatile random access memory (NVRAM).

[0520] In some implementations, memory 1101 stores elements such as execution modules or data structures, or subsets thereof, or extended sets thereof.

[0521] In this embodiment of the application, the corresponding operation is executed by calling the operation instructions stored in the memory 1101 (the operation instructions can be stored in the operating system).

[0522] Through the above description of the embodiments, those skilled in the art will clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device, and unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0523] This application provides a computer program product containing instructions that, when run on a computer, cause the computer to execute the QoE measurement configuration method in the above method embodiments.

[0524] This application also provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the QoE measurement configuration method in the method flow shown in the above method embodiments.

[0525] The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires; a portable computer disk drive; a hard disk drive; a random access memory (RAM); a read-only memory (ROM); an erasable programmable read-only memory (EPROM); a register; a hard disk drive; an optical fiber; a portable compact disc read-only memory (CD-ROM); an optical storage device; a magnetic storage device; or any suitable combination thereof; or any other form of computer-readable storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may reside in an application-specific integrated circuit (ASIC). In the embodiments of this application, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0526] Since the QoE measurement configuration device, computer-readable storage medium, and computer program product in the embodiments of this application can be applied to the above method, the technical effects that can be obtained can also be referred to the above method embodiments. The embodiments of this application will not be repeated here.

[0527] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0528] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0529] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0530] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for configuring and measuring Quality of Experience (QoE), characterized in that, The method includes: The terminal receives first configuration information from the primary base station; wherein, the first configuration information is used to instruct the terminal to perform QoE measurement, and the first configuration information includes first indication information, application layer measurement configuration, maximum number of buffer level entries that can be reported for RAN visible application layer measurement, periodicity of RAN visible reporting, whether the terminal should report the initial playback delay of RAN visible application layer measurement, and type of application layer metric; the first indication information is used to indicate the target base station corresponding to the terminal and the QoE measurement; the target base station includes the primary base station or the secondary base station; the first configuration information is an App Layer Meas Config message, and the first indication information is mrdc-MN Measurement field information; If the target base station indicated by the first indication information is the secondary base station, and the signaling radio bearer SRB3 has been configured and the secondary cell group SCG has not been deactivated, then the terminal sends the QoE measurement report to the secondary base station through the primary base station. If the target base station indicated by the first indication information is the secondary base station, and SRB3 is not configured or SCG has been deactivated, then the terminal sends the QoE measurement report to the primary base station. The QoE measurement report is carried in a Measurement Report App Layer message, which includes an mrdc-MN Measurement field. The mrdc-MN Measurement field is used to indicate the target base station associated with the QoE measurement report.

2. The method according to claim 1, characterized in that, Also includes: If the target base station indicated by the first indication information is the main base station, then the terminal sends the QoE measurement report to the main base station.

3. The method according to claim 2, characterized in that, The method further includes: After receiving the first indication information, the terminal determines the target user corresponding to the QoE measurement; The terminal performs the QoE measurement on the target user and generates a QoE measurement report.

4. The method according to claim 3, characterized in that, The target users include users of the main base station or users of the auxiliary base station.

5. A QoE measurement configuration method, characterized in that, The method includes: The primary base station sends first configuration information to the terminal; wherein, the first configuration information is used to instruct the terminal to perform QoE measurement, and the first configuration information includes first indication information, configuration of application layer measurement, maximum number of buffer level entries that can be reported for RAN visible application layer measurement, periodicity of RAN visible reporting, whether the terminal should report the initial playback delay of RAN visible application layer measurement, and type of application layer metric. The first indication information is used to indicate the target base station corresponding to the terminal and the QoE measurement; the target base station includes the primary base station or the secondary base station; if the target base station indicated by the first indication information is the secondary base station, and the signaling radio bearer SRB3 is configured and the secondary cell group SCG is not deactivated, then the terminal is used to send a QoE measurement report to the secondary base station through the primary base station; if the target base station indicated by the first indication information is the secondary base station, and SRB3 is not configured or SCG has been deactivated, then the terminal is used to send the QoE measurement report to the primary base station; the first configuration information is an App Layer Meas Config message, and the first indication information is mrdc-MN Measurement field information. The main base station receives a QoE measurement report from the terminal; the QoE measurement report is carried in a MeasurementReport App Layer message, which includes mrdc-MN Measurement field information, and the mrdc-MN Measurement field information is used to indicate the target base station associated with the QoE measurement report.

6. A QoE measurement configuration device, characterized in that, The QoE measurement configuration device includes: a receiving unit and a transmitting unit; The receiving unit is configured to receive first configuration information from the primary base station; wherein, the first configuration information is used to instruct the terminal to perform QoE measurement, and the first configuration information includes first indication information, configuration of application layer measurement, maximum number of buffer level entries that can be reported for RAN visible application layer measurement, periodicity of RAN visible reporting, whether the terminal should report the initial playback delay of RAN visible application layer measurement, and type of application layer metric; the first indication information is used to indicate the target base station corresponding to the terminal and the QoE measurement; the target base station includes the primary base station or the secondary base station; the first configuration information is an App Layer Meas Config message, and the first indication information is mrdc-MNMeasurement field information; The sending unit is configured to send the QoE measurement report to the secondary base station through the primary base station when the target base station indicated by the first indication information is the secondary base station, and the signaling radio bearer SRB3 has been configured and the secondary cell group SCG has not been deactivated. The sending unit is further configured to send the QoE measurement report to the primary base station when the target base station indicated by the first indication information is the secondary base station, and SRB3 is not configured or SCG has been deactivated.

7. The QoE measurement configuration device according to claim 6, characterized in that, The sending unit is further configured to send the QoE measurement report to the main base station when the target base station indicated by the first indication information is the main base station.

8. The QoE measurement configuration device according to claim 7, characterized in that, The QoE measurement configuration device further includes: a processing unit; The processing unit is configured to determine the target user corresponding to the QoE measurement after receiving the first indication information; The processing unit is used to perform the QoE measurement on the target user and determine the QoE measurement report.

9. The QoE measurement configuration device according to claim 8, characterized in that, The target users include users of the main base station or users of the auxiliary base station.

10. A QoE measurement configuration device, characterized in that, The QoE measurement configuration device includes: a transmitting unit and a receiving unit; The sending unit is configured to send first configuration information to the terminal; wherein, the first configuration information is used to instruct the terminal to perform QoE measurement, and the first configuration information includes first indication information, configuration of application layer measurement, maximum number of buffer level entries that can be reported for RAN visible application layer measurement, periodicity of RAN visible reporting, whether the terminal should report the initial playback delay of RAN visible application layer measurement, and type of application layer metric; the first indication information is used to indicate the target base station corresponding to the terminal and the QoE measurement; the target base station includes a primary base station or a secondary base station; if the target base station indicated by the first indication information is a secondary base station, and the signaling radio bearer SRB3 is configured and the secondary cell group SCG is not deactivated, then the terminal is configured to send the QoE measurement report to the secondary base station through the primary base station; if the target base station indicated by the first indication information is the secondary base station, and SRB3 is not configured or SCG has been deactivated, then the terminal is configured to send the QoE measurement report to the primary base station; the first configuration information is an App Layer Meas Config message, and the first indication information is mrdc-MN Measurement field information. The receiving unit is configured to receive a QoE measurement report from the terminal; the QoE measurement report is carried in a Measurement Report App Layer message, the Measurement Report App Layer message includes mrdc-MN Measurement field information, the mrdc-MN Measurement field information is used to indicate the target base station associated with the QoE measurement report.

11. An electronic device, characterized in that, include: A processor and a communication interface; the communication interface is coupled to the processor, the processor being configured to run computer programs or instructions to implement the QoE measurement configuration method as claimed in any one of claims 1-4 or 5.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed by a computer, perform the QoE measurement configuration method as described in any one of claims 1-4 or 5.

Images