QOE measurement data acquisition 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 more particularly to terminal devices, access network devices, core network devices, methods, apparatuses, and computer-readable storage media for collecting QoE measurement values in a non-connected state of a terminal device.

Background Art

[0002] One of the main motivations for the evolution of mobile networks is to improve the user experience. For this reason, the evaluation of the user experience on the user equipment (UE) side is extremely important for network operators, especially when the operator provides real-time services such as streaming services (typical video services). In such services, even intermittent quality degradation is very unpleasant. Many of such streaming services are closely related to the increasing rate of commercial traffic. Therefore, the end-user experience is emphasized.

[0003] In this regard, the collection of perceived quality (QoE) information provides detailed information at the call level for a large number of UEs. The function of recording information in the UE, especially the QoE of end-user services, is initiated by the operator and provides QoE information to the operator. The collected information cannot be inferred from the performance measurement values of the mobile network. QoE information is the information measured by the end-user application layer in the UE. The measured QoE information is collected by the management system for analysis and / or KPI calculation. Furthermore, in Rel-17, 3GPP (registered trademark) has started an investigation on NR QoE management and optimization for various services in order to specify the framework for collecting and reporting NR QoE measurement values and investigate the potential impact on related RAN interfaces.

Summary of the Invention

[0004] In general, exemplary embodiments of this disclosure provide solutions for acquiring QoE measurements in the disconnected state of a UE.

[0005] In a first embodiment, a terminal device is provided. The terminal device comprises at least one processor and at least one memory for storing instructions. When an instruction is executed by at least one processor, the terminal device is caused to perform at least: receive from an access network device a Quality of Experience (QoE) measurement acquisition (QMC) procedure setting indicating whether the QMC procedure should be continued when the terminal device transitions to a disconnected state; and, based on the determination that the QMC procedure setting indicates that the QMC procedure should be continued when the terminal device transitions to a disconnected state, record QMC logging data of the QMC procedure performed on the disconnected terminal device into a logging buffer.

[0006] In a second embodiment, an access network device is provided. The access network device comprises at least one processor and at least one memory for storing instructions. When an instruction is executed by at least one processor, it causes the access network device to perform 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 instruction on whether the QMC procedure should be continued when a terminal device transitions to a disconnected state; determine a QMC procedure setting that indicates whether the QMC procedure should be continued when a terminal device transitions to a disconnected state, based on the determination that the QMC procedure request includes an instruction; and transmit the QMC procedure setting to the terminal device.

[0007] In a third embodiment, a core network device is provided. The core network device comprises at least one processor and at least one memory for storing instructions. When executed by the at least one processor, the instructions cause the core network device to perform at least: determine whether the Quality of Experience (QoE) Measurement Collection (QMC) procedure continues when a terminal device transitions to a disconnected state; and send a QMC procedure request to an access network device, which includes an instruction on whether the QMC procedure continues when a terminal device transitions to a disconnected state.

[0008] In a fourth embodiment, a method is provided that is performed by a terminal device. This method includes receiving a QMC procedure setting from an access network device that indicates whether the Quality of Experience (QoE) measurement collection (QMC) procedure should be continued when the terminal device transitions to a disconnected state, and, based on the determination that the QMC procedure setting indicates that the QMC procedure should be continued when the terminal device transitions to a disconnected state, recording QMC logging data of the QMC procedure performed by the disconnected terminal device in a logging buffer.

[0009] In a fifth embodiment, a method is provided that is performed by an access network device. This method includes receiving a Quality of Experience (QoE) Measurement Collection (QMC) procedure request from a core network device; determining whether the QMC procedure request includes an instruction on whether the QMC procedure should continue when a terminal device transitions to a disconnected state; determining a QMC procedure setting that indicates whether the QMC procedure should continue when a terminal device transitions to a disconnected state, based on the determination that the QMC procedure request includes an instruction; and transmitting the QMC procedure setting to the terminal device.

[0010] In a sixth embodiment, a method is provided that is performed by core network equipment. This method includes determining whether the Quality of Experience (QoE) Measurement Collection (QMC) procedure is to continue when a terminal device transitions to a disconnected state, and sending a QMC procedure request to access network equipment, which includes an instruction on whether the QMC procedure is to continue when the terminal device transitions to a disconnected state.

[0011] In a seventh embodiment, a first device is provided. The first device includes means for receiving a QMC procedure setting from an access network device indicating whether or not the perceived quality (QoE) measurement acquisition (QMC) procedure is to be continued when the first device transitions to a disconnected state, and means for recording QMC logging data of the QMC procedure performed by the first device in the disconnected state in a logging buffer, based on the determination that the QMC procedure setting indicates that the QMC procedure is to be continued when the first device transitions to a disconnected state.

[0012] In an eighth embodiment, a second device is provided. The second device includes 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 continued when a terminal device transitions to a disconnected state; means for determining a QMC procedure setting that indicates whether the QMC procedure is continued when a terminal device transitions to a disconnected state, based on the determination that the QMC procedure request includes an instruction; and means for transmitting the QMC procedure setting to a terminal device.

[0013] In a ninth embodiment, a third device is provided. The third device includes means for determining whether the Quality of Experience (QoE) measurement acquisition (QMC) procedure is to be continued when a terminal device transitions to a disconnected state, and means for transmitting a QMC procedure request to an access network device, including an instruction on whether the QMC procedure is to be continued when a terminal device transitions to a disconnected state.

[0014] In a tenth embodiment, a terminal device is provided. The terminal device includes a receiving circuit configured to receive a QMC procedure setting from an access network device indicating whether the Quality of Experience (QoE) measurement acquisition (QMC) procedure is to continue when the terminal device transitions to a disconnected state, and a logging circuit configured to record QMC logging data of the QMC procedure performed on the disconnected terminal device in a logging buffer, based on the determination that the QMC procedure setting indicates that the QMC procedure is to continue when the terminal device transitions to a disconnected state.

[0015] In an eleventh embodiment, an access network device is provided. The access network device includes: a receiving circuit configured to receive a Quality of Experience (QoE) Measurement Collection (QMC) procedure request from a core network device; a first decision circuit configured to determine whether the QMC procedure request includes an instruction on whether the QMC procedure should be continued when a terminal device transitions to a disconnected state; a second decision circuit configured to determine a QMC procedure setting that indicates whether the QMC procedure should be continued when a terminal device transitions to a disconnected state, based on the determination that the QMC procedure request includes an instruction; and a transmitting circuit configured to transmit the QMC procedure setting to a terminal device.

[0016] In a twelfth embodiment, a core network device is provided. The core network device comprises a decision circuit configured to determine whether the Quality of Experience (QoE) Measurement Acquisition (QMC) procedure is to continue when a terminal device transitions to a disconnected state, and a transmit circuit configured to transmit a QMC procedure request to an access network device, including an instruction on whether the QMC procedure is to continue when a terminal device transitions to a disconnected state.

[0017] In a thirteenth embodiment, a terminal device is provided. The terminal device comprises at least one processor and at least one memory for storing computer program code. The at least one memory and the computer program code are configured by the at least one processor to cause the terminal device to perform the method of the fourth embodiment.

[0018] In a fourteenth embodiment, an access network device is provided. The access network device comprises at least one processor and at least one memory for storing computer program code. The at least one memory and the computer program code are configured by the at least one processor to cause the access network device to perform the method of the fifth embodiment.

[0019] In a fifteenth embodiment, a core network device is provided. The core network device comprises at least one processor and at least one memory for storing computer program code. The at least one memory and the computer program code are configured by at least one processor to cause the core network device to perform the method of the sixth embodiment.

[0020] In a sixteenth embodiment, a non-temporary computer-readable medium is provided which includes program instructions for causing an apparatus to perform at least the methods of the fourth, fifth, and sixth embodiments.

[0021] In the seventeenth embodiment, a computer program is provided which, when executed by a device, causes the device to perform at least the methods of the fourth, fifth, and sixth embodiments.

[0022] In the eighteenth embodiment, a computer program is provided which includes instructions for performing at least the methods of the fourth, fifth, and sixth embodiments.

[0023] It should be understood that the summary section is not intended to identify important or essential features of 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 Description of the Drawings

[0024] Next, some exemplary embodiments will be described with reference to the accompanying drawings. [Figure 1A] FIG. 1A shows an example of a network environment in which some exemplary embodiments of the present disclosure can be implemented. [Figure 1B] FIG. 1B shows an example of a process flow of a QMC procedure in the connection state of a UE, in which some exemplary embodiments of the present disclosure can be implemented together. [Figure 2] FIG. 2 is a diagram showing an example of a process flow for a UE to execute a QMC procedure in a non-connected state in some exemplary embodiments of the present disclosure. [Figure 3A] FIG. 3A shows an exemplary process flow for a specific implementation of the allocation of a logging buffer in some exemplary embodiments of the present disclosure. [Figure 3B] FIG. 3B shows an exemplary process flow for a specific implementation of the execution of a QMC procedure in the non-connected state of a UE in some exemplary embodiments of the present disclosure. [Figure 4] FIG. 4 shows a flowchart of an exemplary method implemented by a terminal device in some exemplary embodiments of the present disclosure. [Figure 5] FIG. 5 shows a flowchart of an exemplary method implemented by an access network device in some exemplary embodiments of the present disclosure. [Figure 6] FIG. 6 shows a flowchart of an exemplary method implemented by a core network device in some exemplary embodiments of the present disclosure. [Figure 7]Figure 7 shows a simplified block diagram of a device suitable for carrying out some exemplary embodiments of the present disclosure. [Figure 8] Figure 8 shows a block diagram of an example of a computer-readable medium in some exemplary embodiments of the present disclosure. Throughout the drawings, the same or similar reference figures represent the same or similar elements. [Modes for carrying out the invention]

[0025] Next, the principles of this disclosure will be described with reference to several exemplary embodiments. These embodiments are provided for illustrative purposes only and are intended to help those skilled in the art understand and implement this disclosure, and should not be considered to imply any limitation on the scope of this disclosure. The disclosures described herein may be implemented in various other ways 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 they would be generally understood by an ordinary person skilled in the art to which this disclosure belongs.

[0027] References in this disclosure to “one embodiment,” “embodiment,” “exemplary embodiment,” etc., indicate that the described embodiments may include certain features, structures, or characteristics, but not all embodiments are required to include such features, structures, or characteristics. Furthermore, such expressions do not necessarily refer to the same embodiment. In addition, if certain features, structures, or characteristics are described in relation to an embodiment, it is within the knowledge of those skilled in the art that such features, structures, or characteristics will be affected in relation to other embodiments, whether or not they are explicitly stated.

[0028] In this specification, terms such as “first” and “second” may be used to describe various elements, but it should be understood that these elements should not be limited by these terms. These terms are used merely to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, the first element may be referred to as the second element, and similarly, the second element may be referred to as the first element. As used herein, the terms “and / or” include any one or more, and all combinations of the enumerated terms.

[0029] The terms used herein are for the purpose of describing specific embodiments and are not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural form unless the context clearly indicates otherwise. As used herein, the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including” identify the presence of the described 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 implementation (such as implementation of analog and / or digital circuits only), (b) combination of hardware circuitry and software (if applicable), (i) combination of analog and / or digital hardware circuits and software / firmware, (ii) A part(s) of a hardware processor, including software (including a digital signal processor), software, and memory, that works together to perform various functions on a device such as a mobile phone or a server. (c) Hardware circuits and processors such as microprocessors or parts of microprocessors that require software (e.g., firmware) for operation, but may not be present when not required for operation. This may refer to one or more of these, or all of them.

[0031] This definition of circuit applies to all use of the term in this application, including in all claims. As a further example, in the use of this embodiment, the term circuit also includes not only a hardware circuit or processor (or more processors) or a part of a hardware circuit or processor and the implementation of software and / or firmware associated with it (or them). The term circuit also includes, for example, a baseband integrated circuit or processor integrated circuit for a portable device, or a similar integrated circuit in a server, cellular network equipment, or other computing or network equipment, where applicable to the elements of a particular claim.

[0032] As used herein, the term “communication network” refers to a network conforming to any appropriate communication standard, such as New Radio (NR), Long-Term Evolution (LTE), LTE-Advanced (LTE-A), Broadband Code Division Multiple Access (WCDMA®), High-Speed ​​Packet Access (HSPA), and Narrowband Internet of Things (NB-IoT). Furthermore, communication between terminal equipment and network equipment in a communication network may be carried out in accordance with any appropriate generation of communication protocol, including but not limited to fourth-generation (4G), 4.5G, future fifth-generation (5G) communication protocols, and / or other protocols currently known or to be developed in the future. Embodiments of this disclosure may be applied to a variety of communication systems. Of course, given the rapid development of communications, there will also be future communication technologies and systems to which this disclosure may be embodied. The scope of this disclosure should not be considered to be limited to the systems described above.

[0033] As used herein, the term “network equipment” refers to a node in a communications network from which terminal devices access and receive services. Depending on the terminology and technology applied, network equipment may also refer to base stations (BS) or access points (APs), such as Node B (NodeB, or NB), evolved Node B (eNodeB, or eNB), NR NB (also known as gNB), remote radio units (RRU), radio headers (RH), remote radio heads (RRH), relays, femto, pico, and other low-power nodes.

[0034] The term "terminal equipment" refers to any terminal equipment capable of wireless communication. Rather than being limited, examples of terminal equipment may also be called communication equipment, user equipment (UE), subscriber station (SS), mobile subscriber station, mobile station (MS), or access terminal (AT). Terminal devices include, but are not limited to, mobile phones, cellular phones, smartphones, voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture devices such as digital cameras, game devices, music storage and playback appliances, in-vehicle wireless terminal devices, 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 the context of industrial and / or automated processing chains), consumer electronics devices, and devices operating on commercial and / or industrial wireless networks. In the following description, the terms “terminal devices,” “communication devices,” “terminals,” “user devices,” and “UE” may be used interchangeably.

[0035] Rel-17 defines Multicast Broadcast Service (MBS). MBS (previously called (e)MBMS in earlier releases) has been considered to enable resource-efficient transmission to multiple end users who need to receive the same content. Because broadcasts spread information only downlink (DL), they can also be used in idle mode (where all UEs within the broadcast service area are permitted to receive data). As mentioned above, QoE measurement data is important for end users to measure the perceived quality of service. For example, in the case of TV broadcasting via MBS in NR, QoE reflects subjective perception and the level of acceptance of TV quality.

[0036] Traditionally, QoE measurements were specific to RRC-connected UEs, and a subset of QoE metrics collected from the UE was used for further optimization by the RAN. While RRC-connected, QoE metrics could be transmitted in a timely manner. However, as long as the UE was in an RRC idle / inactive state, the collected QoE metrics were not reported. Traditionally, QoE metrics, i.e., QMC data, could be stored in the UE and reported to the network (MCE, measurement collection entities, etc.) when the UE returned to an RRC-connected state.

[0037] In the case of the MBS service, while QoE measurement collection (QMC) is active, the MBS service may be used on a UE that is in an RRC idle / inactive state, and since there is no specific measurement reporting at the application layer, the QMC data is directly mapped to the measReportAppLayerContainer in the RRC layer to report the measurement to the network side. The measReportAppLayerContainer is then initially stored on the UE and reported when the RRC connection is resumed or re-established. However, while QMC is enabled, 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] Exemplary embodiments of this disclosure provide a mechanism for solving the aforementioned problems, in particular, a method for enabling terminal equipment to record reports of QMC procedures performed in a disconnected state in a logging buffer. Exemplary embodiments of this disclosure enable a UE to store QMC data collected in a disconnected state, and to transmit the necessary QMC data collected in a disconnected state to the network side. The principles of this disclosure and some exemplary embodiments will be described in detail below with reference to the accompanying drawings.

[0039] Figure 1A shows an example of a network environment 101 in which several exemplary embodiments of this disclosure may be implemented. In describing the exemplary embodiments of this disclosure, the network environment 101 may also be referred to as a communication system 101 (e.g., part of a communication network). For illustrative purposes only, various aspects of the exemplary embodiments are described in the context of one or more core network devices, access network devices, and terminal devices communicating with one another. However, it should be understood that the descriptions herein are also applicable to other types of devices or other similar devices referred to using other terms.

[0040] The communication system 101 includes terminal devices 110-1, 110-2, 110-3, and 110-4 (collectively referred to as terminal device 110), access network devices 120-1 and 120-2 (collectively referred to as access network device 120), and core network device 130. The access network device 120 in the communication system 101 provides one or more services (e.g., connection services) to one or more terminal devices 110. Communication between one of the terminal devices 110 and the core network device 130 can be performed via one or more of the access network devices 120.

[0041] Although only a portion of terminal equipment 110 is illustrated in Figure 1, it should be noted that any number of terminal equipment or devices considered to be user equipment may communicate with any number of access network equipment or devices considered to be access network equipment. Furthermore, although terminal equipment 110-1, 110-2, 110-3, and 110-4 are depicted as mobile devices in Figure 1, terminal equipment 110 may be any type of user equipment. In addition, terminal equipment 110-1, 110-2, and 110-3 are located in the area of ​​cell 140-1 hosted by access network equipment 120-1, and / or terminal equipment 110-4 is located in the area of ​​cell 140-2 hosted by access network equipment 120-2.

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

[0043] The core network device 130 may include several appropriate network entities, such as the core network entities described in various exemplary embodiments of this disclosure, including, for example, a measurement acquisition entity (MCE) 131, a network manager (NM) 133, and a domain manager / element manager (DM / EM) 135, in order to facilitate QoE measurements. Conventional solutions have only envisioned operations relating to performing and collecting QoE measurements and reporting them for RRC connectivity status. Figure 1B illustrates the management-based process described.

[0044] Figure 1B shows an example of a process flow 103 in which several exemplary embodiments of this disclosure may be carried out together. Specifically, Figure 1B shows the initiation of a measurement data collection job in NR and the reporting of collected information. Generally, the 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 Figure 1B, the core network device 130 includes three network entities, namely MCE 131, NM 133, and DM / EM 135. The terminal device 110 includes an access layer (AS) 111 and an application layer (AL) 113. It should be understood that AS 111 may include a radio resource control (RRC) layer. The terms "AS 111" and "RRC 111" can be used interchangeably below.

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

[0046] Furthermore, the standard QMC function is defined specifically for the AL service, such as a streaming service over HTTP. QoE metrics collected by the 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 along with the "measReportApplicationLayer". In addition, there is an AT command that is used to share RRC status information with the AL. The corresponding AT command is called +CSCON.

[0047] As shown in Figure 1B, once the QMC procedure is complete, the terminal device 110 is connected via RRC to the access network device 120-1, which has uplink transmission available, allowing the QMC report to be sent to the MCE 131 in a timely manner. As described above, some services may run in disconnected mode, i.e., RRC idle / inactive mode, in which uplink transmission may not be available. If the QMC procedure is disabled in an RRC disconnected state, important QMC data may not be collected. In this regard, the QMC procedure in disconnected mode is performed in some exemplary embodiments of this disclosure. The QMC procedure in disconnected mode will be described in detail below with reference to Figure 2, as a supplement to the QMC procedure in connected state as shown in Figure 1B.

[0048] Figure 2 shows an example of a process flow 200 for performing a QMC procedure in a disconnected state in some exemplary embodiments of this disclosure. For illustrative purposes, process flow 201 is described with reference to Figures 1A-1B. Although process flow 200 has been described with reference to the network environment 100 in Figure 1A, it should be noted that this process flow 200 may be similarly applicable to other similar communication scenarios.

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

[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 will continue when the terminal device 110-1 transitions to a disconnected state, the terminal device 110-1 records the QMC logging data of the QMC procedure performed on the disconnected terminal device 110-1 in the logging buffer (222). On the other hand, if the QMC procedure setting 210 indicates that the QMC procedure will stop when the terminal device 110-1 transitions to a disconnected state, the terminal device 110-1 can stop the QMC procedure in the disconnected state. In this way, by recording the QMC data collected in the disconnected state in the logging buffer, the necessary QMC data collected in the disconnected state can be retained without loss.

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

[0052] In order to allocate the logging buffer, several additional parameters for the logging buffer may be required. Therefore, the QMC procedure setting 210 may include additional instructions to facilitate the allocation of the logging buffer. In some exemplary embodiments, the additional instructions may include instructions for the 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 capacity information previously received from the terminal device 110-1.

[0053] In some exemplary embodiments, further instructions may include instructions for a size threshold for the logging buffer. The size threshold may be an absolute or 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, further instructions may include instructions for the location of the logging buffer. For example, the logging buffer may be allocated at the RRC layer or at the application layer.

[0055] In some exemplary embodiments, further instructions may include instructions on the application state of the logging buffer. The disconnected state may include the RRC idle state and the RRC inactive state. The QMC procedure setting 210 may indicate under which state the logging buffer is used. A logging buffer associated with a single service may be configured differently for different states.

[0056] In some exemplary embodiments, further instructions may include instructions on how the QMC procedure is controlled when a size threshold or buffer size is exceeded. The actions that terminal device 110-1 should take when a size threshold or buffer size is exceeded can be defined in the QMC procedure setting 210. For example, if the size of the QMC logging data recorded in the logging buffer exceeds a predetermined size threshold or buffer size, terminal device 110-1, which is in an RRC inactive state, can resume its connection with access network device 120-1. If terminal device 110-1 is in an RRC idle state, terminal device 110-1 can initiate a connection with access network device 120-1. After the connection is established, terminal device can send a report of QMC logging data to 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 the 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., QMC data newly collected after the size threshold or buffer size was exceeded.

[0058] Figures 3A-3B illustrate specific implementations of the QMC procedure in disconnected mode in some exemplary embodiments of the present disclosure. The QMC procedure comprises two stages: a setup and logging buffer allocation stage, and a QMC procedure execution stage. For illustrative purposes, process flow 301, as illustrated in Figure 3A, and process flow 303, as illustrated in Figure 3B, are described with reference to Figures 1A-1B. Although process flows 301 and 303 have been described with reference to the network environment 101 in Figure 1, it will be understood that process flows 301 and 303 can be similarly applied to other similar communication scenarios.

[0059] Figure 3A shows an exemplary process flow 301 for a specific implementation of logging buffer allocation in some exemplary embodiments of the present disclosure. The process flow 301 includes the NM133 of the core network device 130, the RRC layer 111 of the access network device 120-1, the terminal device 110-1, and the application layer 113 of the terminal device 110-1.

[0060] In process flow 301, terminal device 110-1 is connected to access network device 120-1 via RRC at 302. Memory capacity information 305 is sent from RRC layer 111 to access network device 120-1 (304). After access network device 120-1 receives memory capacity information 305 (306), access network device 120-1 recognizes the memory capacity of terminal device 110-1. NM133 sends message activeQMCJob310 to access network device 120-1 (308). For example, along with the "activateQMCJob" configuration message, NM133 specifies whether the QMC procedure should continue when the UE leaves the RRC connection state and transitions to the RRC idle / inactive state. That is, activeQMCJob310 may include the QMC configuration file and an instruction on whether the QMC procedure should continue in the idle / inactive state. Aside from this display, the rest of activeQMCJob310 may be the same as activeQMCJob105, as shown in Figure 1B. In an exemplary embodiment, the indicator may be a CONTINUE_FLAG of a Boolean data type, where TRUE indicates that the QMC procedure will continue and FALSE indicates that the QMC procedure will terminate (or vice versa). If the indicator is FALSE, or if there is no indicator, the QMC procedure will be executed according to the current state of affairs.

[0061] Returning to Figure 3A, upon receiving activeQMCJob310 (312), the access network device 120-1 determines the RRCReconfiguration message 315 at 314. The access network device 120-1 creates the RRCReconfiguration message 315 based on the CONTINUE_FLAG of activeQMCJob310. The RRCReconfiguration message 315 may contain 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 how the UE should behave when the buffers become full during idle and inactive states, and a buffer fill threshold. A logging buffer can be created for each ApplMeasID.

[0062] After the RRCReconfiguration message 315 is identified, the access network device 120-1 sends the RRCReconfiguration message 315 to the terminal device 110-1 (316). Upon receiving the RRCReconfiguration message 315 (318), the terminal device 110-1 allocates a logging buffer and sets its parameters 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] Since the QoE measurement is performed at AL113, the RRC layer 111 sends the AT command +CAPPLEVMCNR320 containing CONTINUE_FLAG to AL113 to instruct AL113 to continue QMC when terminal device 110-1 transitions to a disconnected state (324). In the illustrated embodiment, the logging procedure is performed at the RRC layer 111 of the AS domain, i.e., terminal device 110-1. Once the QoE measurement data is collected, AL113 sends the data to the RRC layer 111 to record the data in the logging buffer allocated to the RRC layer 111. Therefore, it is not necessary to send parameters for the allocation of the logging buffer to AL113. Only CONTINUE_FLAG is forwarded to AL113 as a modification of the existing AT command +CAPPLEVMCNR. In some alternative embodiments, the logging buffer may be allocated to AL113. In this case, all parameters for the allocation of the logging buffer are forwarded to AL113.

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

[0065] Typical reasons for terminal devices to extend unicast connections are energy saving and resource efficiency. This changes the current state of the access layer. However, services operating at the application layer are not affected when the AS changes. As shown in Figure 3B, terminal device 110-1 changes its state to RRC idle at 328. Access network device 120-1 then sends an RRC connection release message 325 to RRC layer 111 (332). After terminal device 110-1 receives the RRC connection release message 325 (334), the unicast connection between terminal device 110-1 and access network device 120-1 is released. Meanwhile, terminal device 110-1 changes from connected state to RRC idle state and sends AT command +CSON 330 to terminal device 110-1's AL113 (336).

[0066] When AL113 receives +CSON330, AL113 recognizes that the RRC connection has been released. According to the BOOLEAN variable CONTINUE_FLAG previously received by AL113, AL113 recognizes whether the QMC procedure should be terminated (e.g., CONTINUE_FLAG=FALSE) or continued (e.g., CONTINUE_FLAG=TRUE). In this embodiment, based on CONTINUE_FLAG, AL113 decides in 342 that the QMC procedure will continue. AL113 periodically sends the AT command +CAPPLAYMRNR335 to the RRC layer 111 (shown in multiple lines in Figure 3B) (344), which includes a report of the traversed QMC data. That is, AL periodically sends QMC reports for the corresponding AppLayerMeasID to bufferable AS domains as long as the fill threshold is not exceeded. Upon receiving +CAPPLAYMRNR335 (346), the RRC layer 111 records the report in the logging buffer in 348.

[0067] If, at some point, RRC layer 111 determines at 352 that the size of the report recorded in the logging buffer exceeds the buffer size threshold, terminal device 110-1 initiates the connection procedure with access network device 120-1 via Random Access Channel (RACH) at 354. Exceeding the size threshold triggers RRC reactivation, i.e., restarting inactive RRCs that are synchronized with the network via RACH and reconnecting idle RRCs, respectively, to restart or set up an RRC connection.

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

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

[0070] Figure 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 in view of terminal device 110-1 with reference to Figure 1.

[0071] In block 402, terminal device 110-1 receives a Quality of Experience (QoE) measurement acquisition (QMC) procedure setting from access network device 120-1 that indicates whether the QMC procedure should be continued when the terminal device transitions to a disconnected state. In block 404, terminal device 110-1 determines that the QMC procedure setting indicates that the QMC procedure should be continued when the terminal device transitions to a disconnected state, and records the QMC logging data of the QMC procedure performed on the disconnected terminal device in the logging buffer.

[0072] In some exemplary embodiments, the QMC procedure configuration further specifies at least one of the following: the buffer size of the logging buffer, the size threshold of the logging buffer, the location of the logging buffer, the application state of the logging buffer, and instructions on how the QMC procedure is controlled if the size threshold or buffer size is exceeded.

[0073] In some exemplary embodiments, instructions indicate one of the following: resuming or initiating a connection with an access network device to send a report of QMC logging data, then clearing the logging buffer, stopping the logging of QMC logging data and discarding new QMC logging data, or overwriting logged QMC logging data with new QMC logging data.

[0074] In some exemplary embodiments, terminal device 110-1 further resumes the disconnected state based on its determination that a report has been sent. In some exemplary embodiments, the size threshold is either an absolute threshold or a relative threshold. In some exemplary embodiments, the terminal device further allocates multiple logging buffers to store multiple reports of multiple QMC procedures performed on the terminal device during the disconnected state. In this case, the logging buffer is one of the multiple logging buffers.

[0075] In some exemplary embodiments, QMC procedure settings are received for each of a plurality of QMC procedures. In some exemplary embodiments, the terminal device further causes the terminal device's radio resource control (RRC) layer to send an instruction to the terminal device's application layer indicating whether the QMC procedure should continue when the terminal device transitions to a disconnected state.

[0076] In some exemplary embodiments, the buffer size is determined based on the memory capacity information of the terminal device. In some exemplary embodiments, the disconnected state includes a Radio Resource Control (RRC) idle state or an RRC inactive state. In some exemplary embodiments, the QMC procedure setting 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] Figure 5 shows a flowchart 500 of a method implemented in an access network device according to some other embodiments of the present disclosure. For illustrative purposes, the method 500 will be described in terms of an access network device 120-1 with reference to Figure 1.

[0078] In block 502, access network device 120-1 receives a Quality of Experience (QoE) measurement data 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 instruction on whether the QMC procedure should continue when the terminal device transitions to a disconnected state. In block 506, based on the determination that the QMC procedure request includes an instruction, access network device 120-1 determines a QMC procedure setting that instructs whether the QMC procedure should 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 exemplary embodiments, in order to determine the QMC procedure settings, the access network device 120-1 may determine at least one of the following from the QMC procedure settings: the buffer size of the logging buffer, the size threshold of the logging buffer, the location of the logging buffer, the application state of the logging buffer, and instructions on how the QMC procedure is controlled if the size threshold or buffer size is exceeded.

[0080] In some exemplary embodiments, instructions may indicate one of the following: reactivate or initiate a connection with an access network device to send a report of QMC logging data, followed by clearing the logging buffer; stop logging the QMC logging buffer and discard new QMC logging data; or overwrite 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, in order to determine the QMC procedure settings, the access network device 120-1 may receive memory capacity information from the terminal device and determine the buffer size of the logging buffer based on the memory capacity information.

[0082] In some exemplary embodiments, to transmit QMC procedure settings, access network device 120-1 may send a radio resource control (RRC) message or broadcast message containing the QMC procedure settings to terminal devices. In some exemplary embodiments, the RRC message may include an RRC reset message or an RRC connection release message. In some exemplary embodiments, the disconnected state may include a radio resource control (RRC) idle state or an RRC inactive state.

[0083] In some exemplary embodiments, the access network device may, based on its determination that the QMC procedure request does not contain any instructions, further determine a QMC procedure setting that indicates whether the QMC procedure should continue when the terminal device transitions to a disconnected state in accordance with the service associated with the QMC procedure request.

[0084] Figure 6 shows a flowchart 600 of a method implemented in a core network device according to some other embodiments of this disclosure. For illustrative purposes, the method 600 will be described in terms of a core network device 130 with reference to Figure 1.

[0085] In block 602, the core network device 130 determines whether the Quality of Experience (QoE) measurement collection (QMC) procedure should continue 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, which includes an instruction on whether the QMC procedure should continue when the terminal device transitions to a disconnected state. In some exemplary embodiments, the core network device 130 may further receive and store reports of QMC logging data for the QMC procedure from the terminal device.

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

[0087] The communication module 740 is for bidirectional communication. The communication module 740 has at least one antenna to facilitate communication. The communication interface may mean any interface necessary for communication with other network elements.

[0088] The processor 710 may be of any type suitable for a local technology network and, in non-limiting examples, may include one or more of general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. The device 800 may have multiple processors, such as special-purpose integrated circuit chips, which are time-slave to a clock that synchronizes the main processor.

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

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

[0091] Embodiments of the present disclosure may be implemented by program 730 so that device 700 can perform any process of the present disclosure, as described with reference to Figures 2 to 3B. Embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0092] In some exemplary embodiments, the program 730 may be tangibly contained in a computer-readable medium that may be contained in device 700 (such as in memory 720) or in other storage devices accessible by device 700. The arithmetic unit 800 may load the program 730 from the computer-readable medium into RAM 722 and execute it. The computer-readable medium may include any type of tangible non-volatile storage device, such as ROM, EPROM, flash® memory, hard disk, CD, DVD, etc.

[0093] Figure 8 shows a block diagram of an example of a computer-readable medium 800 in some exemplary embodiments of the present disclosure. The computer-readable medium 800 has a program 730 stored therein. Although the computer-readable medium 800 is depicted in the form of a CD or DVD in Figure 8, it should be noted that the computer-readable medium 800 may be in other forms suitable for transporting or holding the program 730.

[0094] In general, various embodiments of this disclosure may be implemented in hardware or special-purpose circuits, software, logic, or any combination thereof. In one embodiment, it may be implemented in hardware, while in another embodiment, it may be implemented in firmware or software that can be executed by a controller, microprocessor, or other processing unit. While some embodiments of this disclosure are illustrated and described using block diagrams, flowcharts, or any other graphic representation, it should be understood that any blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, special-purpose circuits or logic, general-purpose hardware or controllers or other processing units, or any combination thereof, in non-limiting examples.

[0095] This disclosure also provides at least one computer program product tangibly stored in a non-temporary computer-readable storage medium. The computer program product includes computer-executable instructions, such as those contained in a program module, which are executed on a device on a target real or virtual processor to perform the methods 400, 500, or 600 described above with reference to Figures 4, 5, or 6. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a specific task or implement a specific abstract data type. The functions of a program module can be combined or divided among program modules as desired in various embodiments. The machine-executable instructions of a program module can be executed in a local or distributed device. In a distributed device, the program module can be located on both local and remote storage media.

[0096] Program code for carrying out the methods of this 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 device, so that when the program code is executed by the processor or controller, specific functions / operations are performed on flowcharts and / or block diagrams. The program code may run entirely on the machine, partially on the machine, as a standalone software package, partially on the machine, partially on a remote machine, or entirely on a remote machine or server.

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

[0098] Computer-readable media may be computer-readable signal media or computer-readable storage media. 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 electrical connections with one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM, or flash® memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0099] Furthermore, although the operations are described in a specific order, this should not be understood as requiring that such operations be performed in a specific order or sequentially, or that all illustrated operations be performed, in order to achieve the desired result. In certain circumstances, multitasking and parallel processing may be preferable. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of this disclosure, but rather as descriptions of features specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented separately or in any suitable subcombination in multiple embodiments.

[0100] While this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the attached claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for carrying out the claims.

Claims

1. Terminal device, At least one processor, When executed by the at least one processor, the terminal device receives at least, The access network device receives a QMC procedure setting that instructs whether or not the Quality of Experience (QoE) measurement data collection (QMC) procedure should continue when the terminal device transitions to a disconnected state. When the terminal device transitions to the disconnected state, based on the determination that the QMC procedure setting instructs the QMC procedure to continue, the QMC logging data of the QMC procedure executed by the terminal device in the disconnected state is recorded in the logging buffer. At least one memory that stores instructions to execute, Equipped with, The aforementioned QMC procedure settings further include: The buffer size of the aforementioned logging buffer, The size threshold of the logging buffer, Check the logging buffer mentioned above. The application status of the logging buffer, and Instructions on how the QMC procedure will be controlled if the size threshold or buffer size is exceeded, Showing at least one of the following: Terminal equipment.

2. The above instructions are, To transmit the QMC logging data report, the connection to the access network device is restarted or started, and then the logging buffer is cleared. 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 1, which indicates one of the following.

3. The aforementioned terminal device further, Based on the determination that the aforementioned report has been sent, the disconnected state will be resumed. The terminal device according to claim 2, which is configured to perform the following.

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

5. The aforementioned terminal device further, In the disconnected state, the allocation of multiple logging buffers for storing multiple reports of multiple QMC procedures performed on the terminal device, wherein the logging buffer is one of the multiple logging buffers, A terminal device according to any one of claims 1 to 4, which is configured to perform the following:

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

7. The aforementioned terminal device further, When the terminal device transitions to the disconnected state, the Radio Resource Control (RRC) layer of the terminal device is instructed to send an instruction to the application layer of the terminal device indicating whether or not the QMC procedure should be continued. A terminal device according to any one of claims 1 to 4, which is configured to perform the following:

8. The terminal device according to claim 1, wherein the buffer size is determined based on the memory capacity information of the terminal device.

9. The terminal device according to any one of claims 1 to 4, wherein the disconnected state is a wireless resource control (RRC) idle state or an RRC inactive state.

10. The terminal device according to any one of claims 1 to 4, wherein the QMC procedure setting is included in a radio resource control (RRC) message or a broadcast message.

11. The aforementioned RRC message is, RRC connection release message or RRC reconfiguration message, The terminal device according to claim 10.

12. Access network equipment, At least one processor, When executed by the at least one processor, the access network device will have at least: Receiving a request for the QoE (Quality of Experience) measurement data collection (QMC) procedure from the core network equipment, The determination of whether the aforementioned QMC procedure request includes an instruction on whether or not the QMC procedure should continue when the terminal device transitions to a disconnected state, Based on the determination that the QMC procedure request includes the instruction, a QMC procedure setting is determined that indicates whether or not the QMC procedure is continued when the terminal device transitions to the disconnected state. The QMC procedure settings are transmitted to the terminal device, At least one memory that stores instructions to execute, Equipped with, The aforementioned access network equipment is The above QMC procedure setting Logging buffer size, The size threshold of the logging buffer, Check the logging buffer mentioned above. The application status of the logging buffer, and Instructions on how the QMC procedure will be controlled if the size threshold or buffer size is exceeded, To decide at least one of the following: The QMC procedure settings are determined by the above. Access network equipment.

13. The above instructions are, To transmit the QMC logging data report, the connection to the access network device is restarted or started, and then the logging buffer is cleared. This involves stopping the logging of the QMC logging buffer and discarding new QMC logging data. Overwriting recorded QMC logging data with new QMC logging data, The access network device according to claim 12, which indicates one of the following.

14. The access network device according to claim 12, wherein the size threshold is an absolute threshold or a relative threshold.

15. The aforementioned access network equipment is Receiving information on the memory capacity of the aforementioned terminal device, Based on the memory capacity information, the buffer size of the logging buffer is determined, The access network device according to claim 12, wherein the QMC procedure setting is determined by the above.

16. The aforementioned access network equipment is To transmit a radio resource control (RRC) message or broadcast message, including the QMC procedure setting, to the terminal device. The access network device according to any one of claims 12 to 15, wherein the QMC procedure settings are transmitted accordingly.

17. The access network device according to claim 16, wherein the RRC message includes an RRC reset message or an RRC disconnection message.

18. The aforementioned disconnected state includes a Radio Resource Control (RRC) idle state or an RRC inactive state. An access network device according to any one of claims 12 to 15.

19. The aforementioned access network equipment is Based on the determination that the QMC procedure request does not include the instruction, determine the QMC procedure setting that indicates whether the QMC procedure is continued when the terminal device transitions to the disconnected state, in accordance with the service associated with the QMC procedure request. An access network device according to any one of claims 12 to 15, which is configured to perform the following:

20. When an access network device transitions to a disconnected state, the terminal device receives a QMC procedure setting that instructs whether or not the Quality of Experience (QoE) measurement value collection (QMC) procedure should continue. Based on the determination that the QMC procedure setting instructs the terminal device to continue the QMC procedure when the terminal device transitions to the disconnected state, the terminal device records the QMC logging data of the QMC procedure performed on the terminal device in the disconnected state into a logging buffer, The aforementioned QMC procedure settings further include: The buffer size of the aforementioned logging buffer, The size threshold of the logging buffer, Check the logging buffer mentioned above. The application status of the logging buffer, and Instructions on how the QMC procedure will be controlled if the size threshold or buffer size is exceeded, Showing at least one of the following: method.

21. An access network device receives a request for a Quality of Experience (QoE) measurement value collection (QMC) procedure from a core network device, When a terminal device transitions to a disconnected state, the access network device determines whether the QMC procedure request includes an instruction on whether or not the QMC procedure should be continued. Based on the determination that the QMC procedure request includes the instruction, when the terminal device transitions to the disconnected state, the access network device determines a QMC procedure setting that indicates whether or not the QMC procedure is continued. The QMC procedure settings are transmitted to the terminal device, The above QMC procedure setting Logging buffer size, The size threshold of the logging buffer, Check the logging buffer mentioned above. The application status of the logging buffer, and Instructions on how the QMC procedure will be controlled if the size threshold or buffer size is exceeded, The QMC procedure setting is determined by determining at least one of the following: Methods that include...

22. The first device, When the first device transitions to a disconnected state, means for receiving a QMC procedure setting from an access network device that instructs whether or not the perceived quality (QoE) measurement value collection (QMC) procedure should be continued, When the first device transitions to the disconnected state, based on the determination that the QMC procedure setting instructs the QMC procedure to continue, means for recording the QMC logging data of the QMC procedure executed in the first device in the disconnected state into a logging buffer, Equipped with, The aforementioned QMC procedure settings further include: The buffer size of the aforementioned logging buffer, The size threshold of the logging buffer, Check the logging buffer mentioned above. The application status of the logging buffer, and Instructions on how the QMC procedure will be controlled if the size threshold or buffer size is exceeded, Showing at least one of the following: First device.

23. A means for receiving a request for a QoE (Quality of Experience) measurement data collection (QMC) procedure from core network equipment, Means for determining whether the QMC procedure request includes an instruction on whether or not the QMC procedure continues when the terminal device transitions to a disconnected state, A means for determining a QMC procedure setting that indicates whether the QMC procedure is continued when the terminal device transitions to the disconnected state, based on the determination that the QMC procedure request includes the instruction, Means for transmitting the QMC procedure settings to the terminal device, The above QMC procedure setting Logging buffer size, The size threshold of the logging buffer, Check the logging buffer mentioned above. The application status of the logging buffer, and Instructions on how the QMC procedure will be controlled if the size threshold or buffer size is exceeded, A means for determining the QMC procedure setting by determining at least one of the following: A second device comprising the following:

24. A non-temporary computer-readable medium containing program instructions that, when executed by the device, cause the device to perform at least the method according to claim 20 or 21.

Images