QOE measurement collection in disconnected state

Abstract

An exemplary embodiment of the present disclosure relates to QoE measurement collection in a disconnected state. In an exemplary method, a terminal device receives, from an access network device, a quality of experience (QoE) measurement collection (QMC) procedure configuration that indicates whether the QMC procedure is to be continued when the terminal device transitions to the disconnected state. Then, based on determining that the QMC procedure configuration indicates that the QMC procedure is to be continued when the terminal device transitions to the disconnected state, the terminal device records QMC logging data of the QMC procedure performed by the terminal device in the disconnected state in a logging buffer. In this manner, storing the QMC data collected in the disconnected state in the logging buffer allows necessary QMC data collected in the disconnected state to be retained.

Description

[Technical Field]

[0001] Various exemplary embodiments relate to the field of telecommunications, and in particular to terminal equipment, access network equipment, core network equipment, methods, apparatuses, and computer-readable storage media for QoE measurement collection in a disconnected state of the terminal equipment. [Background technology]

[0002] One of the main motivations for the evolution of mobile networks is to improve user experience. Therefore, evaluating the user experience at the user equipment (UE) side is extremely important for network operators, especially when operators offer real-time services such as streaming services (typical video services). For such services, even intermittent quality degradation can be very unpleasant. Many of these streaming services are contributing significantly to the growth rate of commercial traffic. Therefore, the end user experience is of paramount importance.

[0003] In this regard, quality of experience (QoE) information collection provides detailed call-level information for a large number of UEs. The function of recording information in the UE, particularly the QoE of end-user services, is initiated by the operator and provides the operator with QoE information. The collected information cannot be inferred from mobile network performance measurements. QoE information is measured by the end-user application layer in the UE. The measured QoE information is collected by a management system for analysis and / or KPI calculation. Furthermore, in Rel-17, 3GPP initiated a study on NR QoE management and optimization for various services to identify a framework for collecting and reporting NR QoE measurements and to investigate the potential impact on the associated RAN interface. Summary of the Invention

[0004] Generally, the exemplary embodiments of the present disclosure provide a solution for QoE measurement collection in a disconnected state of a UE.

[0005] In a first aspect, a terminal device is provided, the terminal device comprising: at least one processor; and at least one memory that stores instructions that, when executed by the at least one processor, cause the terminal device to at least: receive, from an access network device, a quality of experience (QoE) measurement collection (QMC) procedure setting that indicates whether a QMC procedure is to be continued when the terminal device transitions to an unconnected state; and, based on determining that the QMC procedure setting indicates that the QMC procedure is to be continued when the terminal device transitions to an unconnected state, record QMC logging data of the QMC procedure performed in the unconnected state in a logging buffer.

[0006] In a second aspect, an access network device is provided, the access network device comprising: at least one processor; and at least one memory that stores instructions that, when executed by the at least one processor, cause the access network device to at least receive a Quality of Experience (QoE) Measurement Collection (QMC) procedure request from a core network device, determine whether the QMC procedure request includes an indication of whether the QMC procedure is to be continued when the terminal device transitions to an unconnected state, determine a QMC procedure setting that indicates whether the QMC procedure is to be continued when the terminal device transitions to an unconnected state based on determining that the QMC procedure request includes the indication, and send the QMC procedure setting to the terminal device.

[0007] In a third aspect, a core network device is provided, the core network device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the core network device to at least determine whether a Quality of Experience (QoE) Measurement Collection (QMC) procedure is to continue when a terminal device transitions to an unconnected state; and send a QMC procedure request to an access network device when the terminal device transitions to an unconnected state, the QMC procedure request including an indication of whether the QMC procedure is to continue.

[0008] In a fourth aspect, there is provided a method performed by a terminal device, the method including: receiving, from an access network device, a Quality of Experience (QoE) Measurement Collection (QMC) procedure setting that indicates whether a QMC procedure is to be continued when the terminal device transitions to an unconnected state; and, based on determining that the QMC procedure setting indicates that the QMC procedure is to be continued when the terminal device transitions to the unconnected state, recording QMC logging data of the QMC procedure performed in the unconnected state in a logging buffer.

[0009] In a fifth aspect, there is provided a method performed by an access network device, the method including: receiving a Quality of Experience (QoE) Measurement Collection (QMC) procedure request from a core network device; determining whether the QMC procedure request includes an indication of whether the QMC procedure is to be continued when a terminal device transitions to an unconnected state; based on determining that the QMC procedure request includes the indication, determining a QMC procedure setting that indicates whether the QMC procedure is to be continued when the terminal device transitions to an unconnected state; and sending the QMC procedure setting to the terminal device.

[0010] In a sixth aspect, there is provided a method performed by a core network device, the method including: determining whether a Quality of Experience (QoE) Measurement Collection (QMC) procedure is to continue when a terminal device transitions to an unconnected state; and sending a QMC procedure request to an access network device when the terminal device transitions to the unconnected state, the QMC procedure request including an indication of whether the QMC procedure is to continue.

[0011] In a seventh aspect, a first device is provided, the first device comprising: means for receiving, from an access network device, a Quality of Experience (QoE) Measurement Collection (QMC) procedure setting that indicates whether a QMC procedure is to be continued when the first device transitions to an unconnected state; and means for recording QMC logging data of the QMC procedure performed by the first device in the unconnected state in a logging buffer based on determining that the QMC procedure setting indicates that the QMC procedure is to be continued when the first device transitions to the unconnected state.

[0012] In an eighth aspect, a second device is provided, the second device comprising: means for receiving a quality of experience (QoE) measurement collection (QMC) procedure request from a core network device, means for determining whether the QMC procedure request includes an instruction on whether the QMC procedure is to be continued when the terminal device transitions to an unconnected state, means for determining a QMC procedure setting that indicates whether the QMC procedure is to be continued when the terminal device transitions to an unconnected state based on determining that the QMC procedure request includes the instruction, and means for transmitting the QMC procedure setting to the terminal device.

[0013] In a ninth aspect, a third apparatus is provided, the third apparatus comprising: means for determining whether a Quality of Experience (QoE) Measurement Collection (QMC) procedure is to be continued when a terminal device transitions to an unconnected state; and means for sending a QMC procedure request to an access network device when the terminal device transitions to an unconnected state, the QMC procedure request including an indication of whether the QMC procedure is to be continued.

[0014] In a tenth aspect, a terminal device is provided, the terminal device comprising: a receiving circuit configured to receive, from an access network device, a quality of experience (QoE) measurement collection (QMC) procedure setting that indicates whether a QMC procedure is to be continued when the terminal device transitions to an unconnected state; and a logging circuit configured to record QMC logging data of the QMC procedure performed in the unconnected state in a logging buffer based on determining that the QMC procedure setting indicates that the QMC procedure is to be continued when the terminal device transitions to the unconnected state.

[0015] In an eleventh aspect, an access network device is provided, the access network device comprising: a receiving circuit configured to receive a quality of experience (QoE) measurement collection (QMC) procedure request from a core network device, a first deciding circuit configured to determine whether the QMC procedure request includes an instruction on whether the QMC procedure is to be continued when a terminal device transitions to an unconnected state, a second deciding circuit configured to determine a QMC procedure setting that indicates whether the QMC procedure is to be continued when the terminal device transitions to an unconnected state based on determining that the QMC procedure request includes the instruction, and a transmitting circuit configured to transmit the QMC procedure setting to the terminal device.

[0016] In a twelfth aspect, a core network device is provided, the core network device comprising: a decision circuit configured to determine whether a Quality of Experience (QoE) Measurement Collection (QMC) procedure is to be continued when a terminal device transitions to an unconnected state; and a transmission circuit configured to transmit a QMC procedure request to an access network device when the terminal device transitions to the unconnected state, the QMC procedure request including an indication of whether the QMC procedure is to be continued.

[0017] In a thirteenth aspect, there is provided a terminal device, the terminal device comprising at least one processor and at least one memory storing computer program code, the at least one memory and the computer program code being configured by the at least one processor to cause the terminal device to perform the method of the fourth aspect.

[0018] In a fourteenth aspect, there is provided an access network equipment, comprising at least one processor and at least one memory storing computer program code, the at least one memory and the computer program code being configured by the at least one processor to cause the access network equipment to perform the method of the fifth aspect.

[0019] In a fifteenth aspect, there is provided a core network device comprising at least one processor and at least one memory storing computer program code, the at least one memory and the computer program code being configured by the at least one processor to cause the core network device to perform the method of the sixth aspect.

[0020] In a sixteenth aspect, there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform the methods of at least the fourth, fifth and sixth aspects.

[0021] In a seventeenth aspect, there is provided a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform at least the methods of the fourth, fifth and sixth aspects.

[0022] In an eighteenth aspect, there is provided a computer program comprising instructions for carrying out at least the methods of the fourth, fifth and sixth aspects.

[0023] It should be understood that the Summary is not intended to identify key features or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily apparent through the following description. [Brief explanation of the drawings]

[0024] Some exemplary embodiments will now be described with reference to the accompanying drawings. [Figure 1A] FIG. 1A illustrates an example of a network environment in which some exemplary embodiments of the present disclosure may be implemented. [Figure 1B] FIG. 1B illustrates an example process flow of a QMC procedure in a connected state of a UE, with which some example embodiments of the present disclosure may be implemented. [Figure 2] FIG. 2 illustrates an example process flow for a UE to perform a QMC procedure in a non-connected state in accordance with some exemplary embodiments of the present disclosure. [Figure 3A] FIG. 3A illustrates an example process flow for a specific implementation of logging buffer allocation in accordance with some exemplary embodiments of the present disclosure. [Figure 3B] FIG. 3B illustrates an exemplary process flow for a specific implementation of performing a QMC procedure in a non-connected state of a UE in some exemplary embodiments of the present disclosure. [Figure 4] FIG. 4 illustrates a flowchart of an exemplary method implemented by a terminal device in some exemplary embodiments of the present disclosure. [Figure 5] FIG. 5 illustrates a flowchart of an example method implemented by access network equipment in accordance with some example embodiments of the present disclosure. [Figure 6] FIG. 6 illustrates a flowchart of an example method implemented by core network equipment in accordance with some example embodiments of the present disclosure. [Figure 7]FIG. 7 shows a simplified block diagram of a device suitable for practicing some exemplary embodiments of the present disclosure. [Figure 8] 8 illustrates a block diagram of an example of a computer-readable medium in accordance with some exemplary embodiments of the present disclosure. Throughout the drawings, identical or similar reference numerals represent identical or similar elements. DETAILED DESCRIPTION OF THE INVENTION

[0025] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are provided for illustrative purposes to help those skilled in the art understand and practice the present disclosure, and are not intended to imply any limitations on the scope of the present disclosure. The disclosure described herein may be implemented in various forms other than those described below.

[0026] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0027] References in this disclosure to "one embodiment," "embodiment," "exemplary embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not all embodiments need include the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is understood that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly stated.

[0028] Although terms such as "first" and "second" may be used herein to describe various elements, it should be understood that these elements are not limited by these terms. These terms are merely used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes one or more, any, and all combinations of the listed terms.

[0029] The terminology in the examples is for the purpose of describing particular embodiments and is not intended to limit the exemplary embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that as used herein, the terms "comprises," "comprising," "has," "having," "includes," and / or "including" specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0030] As used in this application, the term "circuit" means (a) hardware-only circuit implementations (e.g., analog and / or digital-only implementations); (b) a combination of hardware circuitry and software (if applicable); (i) a combination of analog and / or digital hardware circuitry and software / firmware; (ii) software (including digital signal processors), software, and hardware processor portions with memory that work together to cause a device, such as a mobile phone or server, to perform various functions; (c) Hardware circuits and processors, such as microprocessors or portions of microprocessors, that require software (e.g., firmware) to operate, but that may be absent when not necessary for operation; It may refer to one or more or all of the following:

[0031] This definition of circuit applies to all uses of the term in this application, including any claims. As a further example, as used herein, the term circuit also covers simply a hardware circuit or processor (or processors) or part of a hardware circuit or processor and its (or their) accompanying software and / or firmware implementation. The term circuit also covers, for example, a baseband or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network equipment, or other computing device or network equipment, if applicable to particular claim elements.

[0032] As used herein, the term "communication network" refers to a network conforming to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), or Narrowband Internet of Things (NB-IoT). Furthermore, communications between terminal devices and network devices in a communication network may be performed according to any suitable generation of communication protocols, including, but not limited to, fourth-generation (4G), 4.5G, future fifth-generation (5G) communication protocols, and / or other protocols currently known or developed in the future. Embodiments of the present disclosure may be applied to various communication systems. Of course, given the rapid development of communications, there will likely be future communication technologies and systems in which the present disclosure may be embodied. The scope of the present disclosure should not be considered limited to only the above-mentioned systems.

[0033] As used herein, the term "network equipment" refers to a node of a communication network through which terminal equipment accesses the network and receives services therefrom. Depending on the terminology and technology applied, network equipment may refer to a base station (BS) or access point (AP), e.g., a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also referred to as gNB), a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, a low-power node such as a femto, or a pico, etc.

[0034] The term "terminal equipment" refers to any terminal equipment capable of wireless communication. By way of example and not limitation, a terminal equipment may also be referred to as a communication device, a user equipment (UE), a subscriber station (SS), a mobile subscriber station, a mobile station (MS), or an access terminal (AT). Terminal equipment includes, but is not limited to, mobile phones, cellular phones, smartphones, voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal equipment, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal equipment such as digital cameras, gaming terminal equipment, music storage and playback appliances, in-vehicle wireless terminal equipment, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearables, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain contexts), consumer electronics devices, devices operating in commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal equipment," "communications equipment," "terminal," "user equipment," and "UE" may be used interchangeably.

[0035] Rel-17 defines multicast broadcast services (MBS). MBS (called (e)MBMS in previous releases) has been considered to enable resource-efficient transmission to multiple end users who need to receive the same content. Because broadcasting spreads information only in the downlink (DL), it can be used even in idle mode (when all UEs within the broadcast service area are authorized to receive data). As mentioned above, QoE measurement data is important for end users to measure the quality of experience of the service. For example, in the case of TV broadcasting over MBS in NR, QoE reflects the subjective perception and acceptance level of TV quality.

[0036] Traditionally, QoE measurements are specific to RRC connected UEs, and a subset of QoE metrics collected from the UE are used by the RAN for further optimization. In the RRC connected state, QoE metrics can be transmitted in time. However, as long as the UE is in an RRC idle / inactive state, the collected QoE metrics are not reported. Traditionally, QoE metrics, i.e., QMC data, could be stored in the UE and reported to the network (e.g., MCE, measurement collection entity) when the UE returns to an RRC connected state.

[0037] For MBS services, while QoE measurement collection (QMC) is active, the MBS service may be used by a UE in RRC idle / inactive state. Since there is no specific measurement reporting at the application layer, the QMC data is directly mapped to the measReportAppLayerContainer in the RRC layer for measurement reporting to the network side. The measReportAppLayerContainer is then initially stored in the UE and reported when the RRC connection is resumed or re-established. However, while QMC is active, the UE may remain in an RRC disconnected state for a long time. Due to size limitations, the contents of the measReportAppLayerContainer may be overwritten multiple times until the RRC connection is resumed or re-established, resulting in the loss of necessary QMC data.

[0038]

[0013] Exemplary embodiments of the present disclosure provide a mechanism for solving the above-mentioned problems, in particular a method for enabling a terminal device to record reports of QMC procedures performed in a non-connected state in a logging buffer. The exemplary embodiments of the present disclosure enable a UE to store QMC data collected in a non-connected state, so that necessary QMC data collected in a non-connected state can be transmitted to a network side.

[0014] The principles and exemplary embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

[0039] 1A illustrates an example of a network environment 101 in which some example embodiments of the present disclosure may be implemented. In describing example embodiments of the present disclosure, the network environment 101 may also be referred to as a communications system 101 (e.g., a portion of a communications network). For illustrative purposes only, various aspects of the example embodiments are described in the context of one or more core network equipment, access network equipment, and terminal equipment communicating with each other. However, it should be understood that the description herein is also applicable to other types of devices, or other similar devices referred to using other terminology.

[0040] The communications system 101 includes terminal devices 110-1, 110-2, 110-3, and 110-4 (collectively referred to as terminal devices 110), access network devices 120-1 and 120-2 (collectively referred to as access network devices 120), and core network devices 130. The access network devices 120 in the communications system 101 provide one or more services (e.g., connectivity services) to one or more terminal devices 110. Communications between one of the terminal devices 110 and the core network devices 130 may be performed via one or more of the access network devices 120.

[0041] 1 illustrates only a portion of terminal equipment 110, it should be noted that any number of terminal equipment or devices considered to be user equipment may be in communication with any number of access network equipment or devices considered to be access network equipment. Furthermore, while terminal equipment 110-1, 110-2, 110-3, and 110-4 are depicted as mobile devices in FIG. 1, terminal equipment 110 may be any type of user equipment. Furthermore, terminal equipment 110-1, 110-2, 110-3 are within the scope of cell 140-1 hosted by access network equipment 120-1, and / or terminal equipment 110-4 is within the scope of cell 140-2 hosted by access network equipment 120-2.

[0042] The access network equipment 120 can communicate with the core network equipment 130, and the core network equipment 130 can provide various services to the terminal equipment 110 via the access network equipment 120. As shown in FIG. 1 , a television broadcast service 150 of a soccer match is running on the terminal equipment 110-1. To determine the subjective perception and acceptance level of the television quality, the Quality of Experience (QoE), i.e., application layer (AL) measurements of the end user's quality of experience of the service, can be measured, and the corresponding measurement data can be collected for subsequent analysis. It should be noted that in various exemplary embodiments of the present disclosure, the terminal equipments 110-2, 110-3, and 110-4, and the access network equipment 120-2 are optional.

[0043] The core network equipment 130 may include several suitable network entities to facilitate QoE measurements, such as the core network entities described in various exemplary embodiments of the present disclosure, such as a Measurement Collection Entity (MCE) 131, a Network Manager (NM) 133, a Domain Manager / Element Manager (DM / EM) 135, etc. Previous solutions have only contemplated operations related to performing and collecting QoE measurements and reporting them on the RRC connection state. Figure 1B illustrates the described management-based process.

[0044] FIG. 1B illustrates an example of a process flow 103 with which some exemplary embodiments of the present disclosure may be implemented. Specifically, FIG. 1B illustrates the initiation of a measurement collection job in NR and the reporting of collected information. In general, a QMC procedure may include the activation of a network request session, a terminal device request session, and a logging session, as well as the reporting of logged measurement data. As shown in FIG. 1B, the core network equipment 130 includes three network entities: an MCE 131, an NM 133, and a DM / EM 135. The terminal equipment 110 includes an access layer (AS) 111 and an application layer (AL) 113. It should be understood that the AS 111 may include a radio resource control (RRC) layer. The terms "AS 111" and "RRC 111" may be used interchangeably hereinafter.

[0045] Figure 1B specifically illustrates the signal exchange during the QMC procedure in the connected state. In this procedure, the UE internal AT commands for application level measurement configuration (+CAPPLEVMCNR) and application level measurement reporting (+CAPPLEVMRNR) are used. +CAPPLEVMR consists of the following elements as shown in Table 1: [Table 1]

[0046] Furthermore, normative QMC functions are defined specific to AL services, e.g., streaming services over HTTP. QoE metrics collected in AL are stored in compressed mode in an 8-bit container with a maximum length of 8000 bytes. This container is delivered to the gNB via RRC together with the "measReportApplicationLayer". Furthermore, an AT command exists and is used to share RRC state information with the AL. The corresponding AT command is called +CSCON.

[0047] As shown in FIG. 1B, once the QMC procedure is completed, the terminal device 110 is RRC connected to the access network device 120-1, where uplink transmission is available, so that the QMC report can be sent to the MCE 131 in time. As mentioned above, some services may be performed in a non-connected mode, i.e., an RRC idle / inactive mode, in which uplink transmission may not be available. If the QMC procedure is disabled in the RRC non-connected state, important QMC data may not be collected. In this regard, the QMC procedure in the non-connected mode is performed in some example embodiments of the present disclosure. The QMC procedure in the non-connected mode will now be described in detail with reference to FIG. 2, as a supplement to the QMC procedure in the connected state as shown in FIG. 1B.

[0048] 2 illustrates an example process flow 200 for performing a QMC procedure in a disconnected state in some exemplary embodiments of the present disclosure. For purposes of explanation, the process flow 201 is described with reference to FIGS. 1A-1B. It should be noted that although the process flow 200 has been described with reference to the network environment 100 of FIG. 1A, the process flow 200 may be applied to other similar communication scenarios as well.

[0049] In process flow 201, before initiating the QMC procedure, core network device 130 determines whether the QMC procedure should continue in an unconnected state (202). Next, core network device 130 transmits a QMC procedure request 205 to access network device 120-1 (204). Upon receiving the QMC procedure request 205 (206), access network device 120-1 determines whether the QMC procedure request 205 includes an instruction on whether the QMC procedure should continue when terminal device 110-1 is in an unconnected state (208). If access network device 120-1 determines that the QMC procedure request 205 does include an instruction, access network device 120-1 determines a QMC procedure setting 210 in accordance with the instruction received from core network device 130, which indicates whether the QMC procedure should continue when the terminal device transitions to an unconnected state (212). In some alternative embodiments, if the access network device 120-1 determines that the QMC procedure request 205 does not include an instruction, the access network device 120-1 determines the QMC procedure configuration 210 according to the service associated with the QMC procedure request. For example, if the access network 120-1 does not receive an instruction, the access network 120-1 can determine whether the QMC procedure continues when the terminal device transitions to a disconnected state based on the type or attribute of the service indicated by the QMC procedure request 205.

[0050] After determining the QMC procedure setting 210, the access network device 120-1 transmits the QMC procedure setting 210 to the terminal device 110-1 (214). As a result, the terminal device 110-1 receives the QMC procedure setting 210 from the access network device 120-1 (216). If the QMC procedure setting 210 indicates that the QMC procedure is to be continued when the terminal device 110-1 transitions to the unconnected state, the terminal device 110-1 records QMC logging data of the QMC procedure executed by the terminal device 110-1 in the unconnected state in a logging buffer (222). On the other hand, if the QMC procedure setting 210 indicates that the QMC procedure is to be stopped when the terminal device 110-1 transitions to the unconnected state, the terminal device 110-1 can stop the QMC procedure in the unconnected state. In this way, by recording the QMC data collected in the unconnected state in the logging buffer, the necessary QMC data collected in the unconnected state can be retained without loss.

[0051] In some exemplary embodiments, the logging buffer may be pre-allocated by the terminal device 110-1 to recode the QMC logging data of the QMC procedure. In some other exemplary embodiments, the logging buffer may be allocated by the terminal device 110-1 when it receives (216) the QMC procedure setting 210. For example, as shown in FIG. 2, when the terminal device 110-1 receives (216) the QMC procedure setting 210, the terminal device 110-1 may allocate (218) a logging buffer based on the QMC procedure setting 210. A logging buffer may be allocated for each service associated with the QMC procedure request 205. Alternatively, a logging buffer may be allocated for all services associated with all QMC procedure requests 205. In some exemplary embodiments, the terminal device 110-1 may allocate multiple logging buffers corresponding to multiple QMC procedure requests, and a QMC procedure setting is received for each of the multiple QMC procedures. In other words, multiple logging buffers may exist simultaneously in the terminal device 110-1, and the logging buffers may be configured independently of each other.

[0052] To allocate the logging buffer, some additional parameters for the logging buffer may be required. Therefore, the QMC procedure configuration 210 may include additional instructions to facilitate the allocation of the logging buffer. In some exemplary embodiments, the additional instructions may include an indication of a buffer size of the logging buffer. The buffer size of the logging buffer may be determined by the access network device 120-1 based on storage capability information previously received from the terminal device 110-1.

[0053] In some exemplary embodiments, the further instructions may include an indication of a size threshold for the logging buffer. The size threshold may be an absolute threshold or a relative threshold. For example, the size threshold may be a specific amount of data or a percentage of the buffer size of the logging buffer.

[0054] In some exemplary embodiments, the further indication may include an indication of the location of a logging buffer, for example, the logging buffer may be allocated at the RRC layer or at the application layer.

[0055] In some exemplary embodiments, the further indication may include an indication of the application state of the logging buffer. The disconnected state may include an RRC idle state and an RRC inactive state. The QMC procedure configuration 210 may indicate in which state the logging buffer is used. The logging buffer associated with one service may be configured differently for different states.

[0056] In some exemplary embodiments, the further instructions may include instructions on how to control the QMC procedure when a size threshold or buffer size is exceeded. The action to be taken by the terminal device 110-1 when the size threshold or buffer size is exceeded may be defined in the QMC procedure configuration 210. For example, when the size of the QMC logging data recorded in the logging buffer exceeds a predetermined size threshold or buffer size, the terminal device 110-1 in the RRC inactive state may resume a connection with the access network device 120-1. When the terminal device 110-1 is in the RRC idle state, the terminal device 110-1 may initiate a connection with the access network device 120-1. After the connection is established, the terminal device may send a report of the QMC logging data to the access network device 120-1 and clear the logging buffer.

[0057] In some alternative embodiments, if the size of the QMC logging data exceeds a predetermined size threshold or buffer size, the terminal device 110-1 may stop logging the QMC logging data and discard new QMC logging data. In some further alternative embodiments, if the size of the QMC logging data exceeds a predetermined size threshold or buffer size, the terminal device 110-1 may overwrite the logged QMC logging data (e.g., the oldest QMC logging data) with new QMC logging data, i.e., the QMC data newly collected after the size threshold or buffer size is exceeded.

[0058] 3A-3B illustrate a specific implementation of a QMC procedure in disconnected mode in some exemplary embodiments of the present disclosure. The QMC procedure includes two phases: a configuration and logging buffer allocation phase and a QMC procedure execution phase. For illustrative purposes, process flow 301 as illustrated in FIG. 3A and process flow 303 as illustrated in FIG. 3B will be described with reference to FIGS. 1A-1B. While process flows 301 and 303 have been described with reference to network environment 101 of FIG. 1, it will be understood that process flows 301 and 303 may be similarly applied to other similar communication scenarios.

[0059] 3A illustrates an example process flow 301 for a specific implementation of allocating a logging buffer in some example embodiments of the present disclosure. The process flow 301 includes the NM 133 of the core network equipment 130, the access network equipment 120-1, the RRC layer 111 of the terminal equipment 110-1, and the application layer 113 of the terminal equipment 110-1.

[0060] In process flow 301, terminal device 110-1 is RRC connected with access network device 120-1 in 302. Storage capability information 305 is sent from RRC layer 111 to access network device 120-1 (304). After access network device 120-1 receives storage capability information 305 (306), access network device 120-1 becomes aware of the storage capability of terminal device 110-1. NM 133 sends message activeQMCJob 310 to access network device 120-1 (308). For example, NM 133 may specify, along with an "activateQMCJob" configuration message, whether the QMC procedure should continue when the UE leaves the RRC connected state and transitions to an RRC idle / inactive state. That is, activeQMCJob 310 may include a QMC configuration file and an indication of whether the QMC procedure should continue when in the idle / inactive state. Besides this indication, the rest of the activeQMCJob 310 may be the same as the activeQMCJob 105, as shown in Figure 1B. In an exemplary embodiment, the indicator may be a BOOLEAN data type CONTINUE_FLAG, where TRUE indicates that the QMC procedure should continue and FALSE indicates that the QMC procedure should terminate (or vice versa). If the indicator is FALSE or there is no indicator, the QMC procedure is performed according to the current state of the art.

[0061] Returning to FIG. 3A, upon receiving 312 the activeQMCJob 310, the access network device 120-1 determines 314 an RRCReconfiguration message 315. The access network device 120-1 creates the RRCReconfiguration message 315 based on the CONTINUE_FLAG in the activeQMCJob 310. The RRCReconfiguration message 315 may include AppLayerMeasConfig information. If the FLAG is TRUE, the appLayerMeasConfig information in the RRCReconfiguration message 315 is modified with configuration data for one or more new buffers for QMC data logging, instructions on UE behavior when the buffers become full during idle and inactive states, and buffer fill thresholds. A logging buffer may be created per ApplMeasID.

[0062] After the RRCReconfiguration message 315 is identified, the access network device 120-1 transmits (316) the RRCReconfiguration message 315 to the terminal device 110-1. Upon receiving (318) the RRCReconfiguration message 315, the terminal device 110-1 allocates a logging buffer and configures parameters of the logging buffer based on the RRCReconfiguration message 315 in 322. In other words, the configuration data of the RRCReconfiguration message 315 triggers the setting of the logging buffer according to the number of AppLayerMeasIds on the terminal device side. Alternatively, the configuration data of the RRCReconfiguration message 315 is stored on the terminal device side and triggers the setting of the logging buffer when idle / inactive.

[0063] Because the QoE measurements are performed in the AL 113, the RRC layer 111 sends an AT command +CAPPLEVMCNR 320 including a CONTINUE_FLAG to the AL 113 to instruct the AL 113 that QMC should continue when the terminal device 110-1 transitions to a disconnected state (324). In the illustrated embodiment, the logging procedure is performed in the AS domain, i.e., in the RRC layer 111 of the terminal device 110-1. Once the QoE measurement data is collected, the AL 113 sends the data to the RRC layer 111, which logs the data in a logging buffer allocated by the RRC layer 111. Therefore, there is no need to send parameters for allocating the logging buffer to the AL 113. Only the CONTINUE_FLAG is forwarded to the AL 113 as a modification of the existing AT command +CAPPLEVMCNR. In some alternative embodiments, the logging buffer may be allocated to the AL 113. In this case, all parameters for allocating the logging buffer are forwarded to the AL 113.

[0064] 3B illustrates an example process flow 303 for a specific embodiment of performing a QMC procedure in an unconnected state in accordance with some example embodiments of the present disclosure. The execution of a QMC procedure in an unconnected state begins when the terminal device 110-1 changes its RRC state from an RRC connected state to an RRC idle / inactive state while the QMC procedure is active.

[0065] A typical reason for a terminal device to extend a unicast connection is to conserve energy and improve resource efficiency. This changes the current state of the access layer. However, services operating at the application layer are not informed of the AS change. As shown in FIG. 3B, the terminal device 110-1 changes its state to RRC idle in 328. The access network device 120-1 then sends an RRC connection release message 325 to the RRC layer 111 (332). After the terminal device 110-1 receives the RRC connection release message 325 (334), the unicast connection between the terminal device 110-1 and the access network device 120-1 is released. Meanwhile, the terminal device 110-1 changes from the connected state to the RRC idle state and sends an AT command +CSON 330 to the AL 113 of the terminal device 110-1 (336).

[0066] When the AL 113 receives the +CSON 330, the AL 113 recognizes the release of the RRC connection. According to the BOOLEAN variable of the CONTINUE_FLAG that the AL 113 previously received, the AL 113 recognizes whether to terminate the QMC procedure (e.g., CONTINUE_FLAG=FALSE) or continue (e.g., CONTINUE_FLAG=TRUE). In this embodiment, the AL 113 continues the QMC procedure at 342 based on the CONTINUE_FLAG. The AL 113 periodically (shown by multiple lines in FIG. 3B ) sends the AT command +CAPPLAYMRNR 335 containing a report of transit QMC data to the RRC layer 111 (344). That is, the AL periodically sends the QMC report of the corresponding AppLayerMeasID to the AS domain where buffering is possible, as long as the filling threshold is not exceeded. Upon receiving the +CAPPLAYMRNR 335 (346), the RRC layer 111 records the report in the logging buffer at 348.

[0067] If at some point the RRC layer 111 determines at 352 that the size of the reports recorded in the logging buffer exceeds a size threshold of the buffer size, the terminal device 110-1 initiates an attachment procedure with the access network device 120-1 via a random access channel (RACH) at 354. Exceeding the size threshold triggers an RRC reactivation, i.e., a resumption of an inactive RRC synchronized with the network via the RACH and an RRC idle reconnection, respectively, to restart or set up the RRC connection.

[0068] After the connection is re-established, the terminal device 110-1 sends (356) an AT command +CSON 340 to the AL 113 to instruct the re-establishment of the connection. Meanwhile, the RRC layer 111 sends (362) an RRC measurement report list 345 containing all reports recorded in the logging buffer to the access network device 120-1. Upon receiving (364) the RRC measurement report list 345, the access network device 120-1 forwards (366) the report list in a measurement report 350 to the MCE 133 of the core network device 130. The MCE 133 receives (368) the measurement report 350 and stores it for subsequent analysis.

[0069] In an alternative embodiment of the allocation of the logging buffer in the AL 113, the AL 113 can store the QMC data in the logging buffer, and if the AL 113 determines that the size of the QMC data exceeds a size threshold or a buffer size, the AL 113 can instruct the RRC layer 111 to initiate a connection with the access network device 120-1. The AL 113 then sends a report of the QMC data to the MCE 133 via the RRC layer 111.

[0070] 4 shows a flowchart 400 of a method implemented in a terminal device according to some other embodiments of the present disclosure. For illustrative purposes, the method 400 will be described from the perspective of the terminal device 110-1 with reference to FIG.

[0071] In block 402, the terminal device 110-1 receives, from the access network device 120-1, a quality of experience (QoE) measurement collection (QMC) procedure setting that indicates whether the QMC procedure is to be continued when the terminal device transitions to an unconnected state. In block 404, the terminal device 110-1 records QMC logging data of the QMC procedure performed in the unconnected terminal device in a logging buffer based on determining that the QMC procedure setting indicates that the QMC procedure is to be continued when the terminal device transitions to an unconnected state.

[0072] In some exemplary embodiments, the QMC procedure settings further indicate at least one of a buffer size for the logging buffer, a size threshold for the logging buffer, a location for the logging buffer, an application status for the logging buffer, and an indication of how the QMC procedure is controlled if the size threshold or buffer size is exceeded.

[0073] In some exemplary embodiments, the instructions indicate either to resume or initiate a connection with the access network device to send a report of the QMC logging data, and then to clear the logging buffer, stop logging the QMC logging data and discard new QMC logging data, or overwrite the logged QMC logging data with new QMC logging data.

[0074] In some exemplary embodiments, terminal device 110-1 further resumes the unconnected state based on determining that the report has been sent. In some exemplary embodiments, the size threshold is an absolute threshold or a relative threshold. In some exemplary embodiments, the terminal device further allocates, in the unconnected state, multiple logging buffers for storing multiple reports of multiple QMC procedures performed at the terminal device. In this case, the logging buffer is one of the multiple logging buffers.

[0075] In some exemplary embodiments, the QMC procedure configuration is received for each of a plurality of QMC procedures. In some exemplary embodiments, the terminal device further causes a radio resource control (RRC) layer of the terminal device to send an indication of whether the QMC procedure will continue when the terminal device transitions to a disconnected state to an application layer of the terminal device.

[0076] In some exemplary embodiments, the buffer size is determined based on storage capability information of the terminal device. In some exemplary embodiments, the non-connected state includes a Radio Resource Control (RRC) idle state or an RRC inactive state. In some exemplary embodiments, the QMC procedure configuration includes a Radio Resource Control (RRC) message or a broadcast message. In some exemplary embodiments, the RRC message includes an RRC disconnection message or an RRC reconfiguration message.

[0077] 5 shows a flowchart 500 of a method implemented in an access network device in accordance with some other embodiments of the present disclosure. For illustrative purposes, the method 500 will be described from the perspective of the access network device 120-1 with reference to FIG.

[0078] In block 502, access network device 120-1 receives a quality of experience (QoE) measurements collection (QMC) procedure request from core network device 130. In block 504, access network device 120-1 determines whether the QMC procedure request includes an indication of whether the QMC procedure is to continue when the terminal device transitions to a disconnected state. In block 506, based on determining that the QMC procedure request includes the indication, access network device 120-1 determines a QMC procedure setting that indicates whether the QMC procedure is to continue when the terminal device transitions to a disconnected state. In block 508, access network device 120-1 transmits the QMC procedure setting to terminal device 110-1.

[0079] In some example embodiments, to determine the QMC procedure settings, the access network device 120-1 may determine at least one of the following QMC procedure settings: a buffer size of the logging buffer, a size threshold of the logging buffer, a location of the logging buffer, an application state of the logging buffer, and an instruction on how the QMC procedure is controlled if the size threshold or the buffer size is exceeded.

[0080] In some example embodiments, the instructions may indicate either to resume or initiate a connection with the access network device to send a report of the QMC logging data and then clear the logging buffer, to stop logging to the QMC logging buffer and discard new QMC logging data, or to overwrite the logged QMC logging data with new QMC logging data.

[0081] In some exemplary embodiments, the size threshold may be an absolute threshold or a relative threshold. In some exemplary embodiments, to determine the QMC procedure configuration, the access network device 120-1 may receive storage capability information of the terminal device and determine a buffer size of the logging buffer based on the storage capability information.

[0082] In some exemplary embodiments, to transmit the QMC procedure configuration, the access network device 120-1 may transmit a radio resource control (RRC) message or a broadcast message including the QMC procedure configuration to the terminal device. In some exemplary embodiments, the RRC message may include an RRC reconfiguration message or an RRC connection release message. In some exemplary embodiments, the non-connected state may include a radio resource control (RRC) idle state or an RRC inactive state.

[0083] In some exemplary embodiments, based on determining that the QMC procedure request does not include an instruction, the access network device may further determine a QMC procedure setting that indicates whether the QMC procedure is to continue when the terminal device transitions to a disconnected state in accordance with the service associated with the QMC procedure request.

[0084] 6 shows a flowchart 600 of a method implemented in core network equipment according to some other embodiments of the present disclosure. For illustrative purposes, the method 600 will be described from the perspective of core network equipment 130 with reference to FIG.

[0085] In block 602, the core network device 130 determines whether a Quality of Experience (QoE) Measurement Collection (QMC) procedure is to be continued when the terminal device transitions to a disconnected state. In block 604, the core network device 130 sends a QMC procedure request to the access network device, the QMC procedure request including an indication of whether the QMC procedure is to be continued when the terminal device transitions to a disconnected state. In some exemplary embodiments, the core network device 130 may further receive a report of QMC logging data of the QMC procedure from the terminal device and store the report.

[0086] 7 shows a simplified block diagram of a device 700 suitable for implementing some example embodiments of the present disclosure. The device 700 may be provided to implement a communication device such as the terminal equipment 110, the access network equipment 120, or the core network equipment 130 shown in FIG. 1. As shown, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processors 710, and one or more communication modules 740 coupled to the processors 710.

[0087] The communication module 740 is for two-way communication. The communication module 740 has at least one antenna to facilitate communication. The communication interface may refer to any interface required for communication with other network elements.

[0088] The processor 710 may be of any type suitable for a local technology network and may include, by way of non-limiting example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 800 may have multiple processors, such as application-specific integrated circuit chips that are time-slaved to a clock that synchronizes a main processor.

[0089] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memory include, but are not limited to, read-only memory (ROM) 724, electronically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic and / or optical storage devices. Examples of volatile memory include, but are not limited to, random access memory (RAM) 722 and other volatile memories that do not persist through power-down periods.

[0090] The computer program 730 includes computer-executable instructions that are executed by the associated processor 710. The program 730 may be stored in the ROM 724. The processor 710 can load the program 730 into the RAM 722 to perform any suitable operations and processes.

[0091] 2 to 3B, the device 700 may be implemented by a program 730 such that the device 700 can execute any process of the present disclosure. The embodiment of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0092] In some demonstrative embodiments, the program 730 may be tangibly contained in a computer-readable medium, which may be included in the device 700 (such as in memory 720) or other storage accessible by the device 700. The computing device 800 may load the program 730 from the computer-readable medium into RAM 722 for execution. The computer-readable medium may include any type of tangible non-volatile storage device, such as a ROM, an EPROM, a flash memory, a hard disk, a CD, a DVD, etc.

[0093] 8 illustrates a block diagram of an example of a computer-readable medium 800 according to some exemplary embodiments of the present disclosure. The computer-readable medium 800 has stored thereon a program 730. While the computer-readable medium 800 is depicted in FIG. 8 in the form of a CD or DVD, it should be noted that the computer-readable medium 800 may be in any other form suitable for carrying or retaining the program 730.

[0094] In general, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. In one aspect, they may be implemented in hardware, while in another aspect, they may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although aspects of embodiments of the present disclosure are shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or some combination thereof, in non-limiting examples.

[0095] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, that execute on a target real or virtual processor to perform the methods 400, 500, or 600 described above with reference to FIG. 4, FIG. 5, or FIG. 6. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split among program modules as desired in various embodiments. The machine-executable instructions of the program modules may be executed in local or distributed devices. In distributed devices, the program modules may be located in both local and remote storage media.

[0096] Program code for implementing the methods of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, and when executed by the processor or controller, cause the specific functions / operations shown in the flowcharts and / or block diagrams to be performed. The program code can run entirely on the machine, partially on the machine, as a standalone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0097] In the context of the present disclosure, computer program code or associated data may be carried by any suitable carrier to enable a device, computing device, or processor to perform the various processes and operations as described above. Examples of carriers include signals, computer-readable media, etc.

[0098] The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. Computer-readable media include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0099] Furthermore, although operations are depicted in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown, or sequentially, or to perform all of the operations shown, to achieve desirable results. In certain situations, multitasking and parallel processing may be preferred. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the disclosure, but rather as descriptions of features that are specific to particular embodiments. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

[0100] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the present disclosure, as defined by the appended claims, is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A terminal device, at least one processor; When executed by the at least one processor, the terminal device is configured to: receiving a Quality of Experience (QoE) Measurement Collection (QMC) procedure configuration from an access network device, the QMC procedure indicating whether a Quality of Experience (QoE) Measurement Collection (QMC) procedure will continue when the terminal device transitions to a disconnected state; When the terminal device transitions to the unconnected state, based on determining that the QMC procedure setting indicates that the QMC procedure is to be continued, recording QMC logging data of the QMC procedure executed in the terminal device in the unconnected state in a logging buffer; at least one memory storing instructions for executing the A terminal device comprising:

2. The QMC procedure setting further comprises: a buffer size of the logging buffer; the size threshold of the logging buffer; the location of the logging buffer; The application status of the logging buffer; and instructions on how the QMC procedure is controlled if the size threshold or the buffer size is exceeded; The terminal device according to claim 1 , wherein the terminal device exhibits at least one of the following:

3. The instructions are: re-opening or initiating a connection with the access network device to transmit the QMC logging data report, and then clearing the logging buffer; Stop logging QMC logging data and discard new QMC logging data, or Overwriting recorded QMC logging data with new QMC logging data; The terminal device according to claim 2, wherein the terminal device indicates any one of the following:

4. The terminal device further resuming the disconnected state based on determining that the report has been sent; 4. The terminal device according to claim 3, adapted to execute the following:

5. The terminal device according to claim 2 , wherein the size threshold is an absolute threshold or a relative threshold.

6. The terminal device further allocating, in the disconnected state, a plurality of logging buffers for storing a plurality of reports of a plurality of QMC procedures executed in the terminal device, the logging buffer being one of the plurality of logging buffers; 6. A terminal device according to claim 1, adapted to execute the following:

7. The terminal device according to claim 6 , wherein the QMC procedure configuration is received for each of the plurality of QMC procedures.

8. The terminal device further When the terminal device transitions to the disconnected state, causing a radio resource control (RRC) layer of the terminal device to send an indication of whether the QMC procedure is to be continued to an application layer of the terminal device; 8. A terminal device according to any one of claims 1 to 7, adapted to execute the following:

9. The terminal device according to claim 2 , wherein the buffer size is determined based on storage capacity information of the terminal device.

10. The terminal device according to claim 1 , wherein the non-connected state is a radio resource control (RRC) idle state or an RRC inactive state.

11. The terminal device according to claim 1 , wherein the QMC procedure configuration is included in a radio resource control (RRC) message or a broadcast message.

12. The RRC message Including an RRC connection release message or an RRC reconfiguration message; The terminal device according to claim 11.

13. An access network device, at least one processor; When executed by the at least one processor, the access network equipment is configured to: receiving a Quality of Experience (QoE) Measurement Collection (QMC) procedure request from a core network device; determining whether the QMC procedure request includes an indication of whether the QMC procedure is to be continued when the terminal device transitions to a disconnected state; determining a QMC procedure setting that indicates whether the QMC procedure is to be continued when the terminal device transitions to the unconnected state based on determining that the QMC procedure request includes the instruction; Sending the QMC procedure configuration to the terminal device; at least one memory storing instructions for executing the An access network device comprising:

14. The access network equipment includes: The QMC procedure setting The buffer size of the logging buffer, the size threshold of the logging buffer; the location of the logging buffer; The application status of the logging buffer; and instructions on how the QMC procedure is controlled if the size threshold or the buffer size is exceeded; determining at least one of: The access network equipment of claim 13 , adapted to determine the QMC procedure configuration by

15. The instructions are: restarting or initiating a connection with the access network device to transmit the QMC logging data report, and then clearing the logging buffer; Stopping logging to the QMC logging buffer and discarding new QMC logging data; Overwriting the recorded QMC logging data with new QMC logging data; The access network equipment of claim 14, wherein the access network equipment indicates any of the following:

16. The access network equipment of claim 14 , wherein the size threshold is an absolute threshold or a relative threshold.

17. The access network equipment includes: receiving storage capability information of the terminal device; determining the buffer size of the logging buffer based on the storage capacity information; The access network equipment of claim 14 , adapted to determine the QMC procedure configuration by:

18. The access network equipment includes: sending a radio resource control (RRC) message or a broadcast message to the terminal device, the message including the QMC procedure configuration; 18. The access network equipment according to claim 13, wherein the access network equipment is adapted to transmit the QMC procedure configuration by

19. The access network equipment of claim 18 , wherein the RRC message comprises an RRC reconfiguration message or an RRC disconnect message.

20. The non-connected state includes a radio resource control (RRC) idle state or an RRC inactive state.

20. An access network equipment according to any one of claims 13 to 19.

21. The access network equipment includes: determining, based on determining that the QMC procedure request does not include the instruction, the QMC procedure setting that indicates whether the QMC procedure is to be continued when the terminal device transitions to the unconnected state according to a service associated with the QMC procedure request; 21. An access network equipment according to any of claims 13 to 20, adapted to execute:

22. A core network device, at least one processor; When executed by the at least one processor, the method causes the core network equipment to determining whether a Quality of Experience (QoE) Measurement Collection (QMC) procedure continues when the terminal device transitions to a disconnected state; When the terminal device transitions to the disconnected state, sending a QMC procedure request to an access network device, the QMC procedure including an indication as to whether the QMC procedure should be continued; at least one memory storing instructions for executing the A core network device comprising:

23. The core network device further receiving a report of QMC logging data of the QMC procedure from the terminal device; storing the report; and 23. The core network equipment of claim 22, adapted to execute:

24. receiving, from the access network device, a Quality of Experience (QoE) Measurement Collection (QMC) procedure configuration indicating whether a QMC procedure is to be continued when the terminal device transitions to a disconnected state; Recording QMC logging data of the QMC procedure executed in the terminal device in the non-connected state in a logging buffer based on determining that the QMC procedure setting indicates that the QMC procedure is to be continued when the terminal device transitions to the non-connected state; A method comprising:

25. receiving a Quality of Experience (QoE) Measurement Collection (QMC) procedure request from a core network device; When the terminal device transitions to a disconnected state, determining whether the QMC procedure request includes an indication of whether the QMC procedure is to be continued; determining a QMC procedure setting that indicates whether the QMC procedure is to be continued when the terminal device transitions to the unconnected state based on determining that the QMC procedure request includes the instruction; Sending the QMC procedure configuration to the terminal device; A method comprising:

26. determining whether a Quality of Experience (QoE) Measurement Collection (QMC) procedure continues when the terminal device transitions to a disconnected state; When the terminal device transitions to the disconnected state, sending a QMC procedure request to an access network device, the QMC procedure including an indication of whether the QMC procedure is to be continued; A method comprising:

27. 1. A first device, comprising: means for receiving a Quality of Experience (QoE) Measurement Collection (QMC) procedure configuration from an access network device when the first device transitions to an unconnected state, the QMC procedure indicating whether a Quality of Experience (QoE) Measurement Collection (QMC) procedure should continue; means for recording QMC logging data of the QMC procedure executed in the first device in the unconnected state in a logging buffer based on determining that the QMC procedure setting indicates that the QMC procedure is to be continued when the first device transitions to the unconnected state; A first device comprising:

28. means for receiving a Quality of Experience (QoE) Measurement Collection (QMC) procedure request from a core network device; means for determining whether the QMC procedure request includes an indication of whether the QMC procedure is to be continued when the terminal device transitions to a non-connected state; means for determining a QMC procedure setting that indicates whether the QMC procedure is to be continued when the terminal device transitions to the non-connected state based on determining that the QMC procedure request includes the instruction; means for transmitting the QMC procedure configuration to the terminal device; A second device comprising:

29. means for determining whether a Quality of Experience (QoE) Measurement Collection (QMC) procedure continues when the terminal device transitions to a disconnected state; means for transmitting a QMC procedure request to an access network device when the terminal device transitions to the disconnected state, the QMC procedure including an indication of whether the QMC procedure is to be continued; A third device comprising:

30. 27. A non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the method of claim 24, 25, or 26.

Images