System and method for recorded quality of experience measurements

Abstract

Systems and methods for logged Quality of Experience (QoE) measurements are presented. A wireless communication device (e.g., a UE) may store measurements of QoE as QoE buffer data. The wireless communication device may send a first message to a wireless communication node (e.g., a BS), the first message including the QoE buffered data.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications, including but not limited to systems and methods for recorded quality of experience (QoE) measurements. Background Art

[0002] The third generation partnership project (3GPP), a standardization organization, is currently developing a new radio interface called 5G New Radio (5G NR) and the next generation packet core network (NG-CN or NGC). 5G NR will have three main components: 5G access network (5G-AN), 5G core network (5GC) and user terminal (UE). In order to facilitate the implementation of different data services and requirements, the elements of 5GC (also known as network functions) have been simplified, some of which are software-based and some are hardware-based so that they can be adjusted according to requirements. Summary of the invention

[0003] The example embodiments disclosed herein are intended to solve problems related to one or more of the problems arising in the prior art, and are intended to provide additional functionality, which will become apparent when combined with the accompanying drawings by reference to the following specific embodiments. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example rather than by way of limitation, and it will be apparent to those of ordinary skill in the art who read this disclosure that various modifications may be made to the disclosed embodiments while remaining within the scope of this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium. A wireless communication device (e.g., UE) may store a measurement of quality of experience (QoE) as QoE buffered data. The wireless communication device may send a first message to a wireless communication node (e.g., BS), the first message including the QoE buffered data.

[0005] In some embodiments, when the wireless communication device is not in the RRC_CONNECTED state, the wireless communication device may store the QoE buffered data. The wireless communication device may send the first message before the wireless communication device switches back to the RRC_CONNECTED state.

[0006] In some embodiments, the wireless communication device may receive a second message (e.g., an RRC release message) from the wireless communication node, causing the wireless communication device to switch from the RRC_CONNECTED state to the RRC_INACTIVE state or the RRC_IDLE state. Before receiving the second message, the wireless communication device may receive a third message indicating that the wireless communication device can trigger the measurement of QoE in any one of the RRC_CONNECTED state, the RRC_INACTIVE state, or the RRC_IDLE state. After switching to the RRC_INACTIVE state or the RRC_IDLE state, the wireless communication device may continue to store the measurement of QoE as the QoE buffered data. In some embodiments, before receiving the second message, the wireless communication device may receive a fourth message indicating that the wireless communication device can only trigger the measurement of QoE in the RRC_INACTIVE state or the RRC_IDLE state. After switching to the RRC_INACTIVE state or the RRC_IDLE state, the wireless communication device may store the measurement of QoE as the QoE buffered data.

[0007] In some embodiments, the wireless communication device may receive a fifth message (e.g., an RRC recovery message, an RRC setup message) from the wireless communication node, causing the wireless communication device to switch back to the RRC_CONNECTED state. In response to receiving the fifth message, the wireless communication device may send a sixth message (e.g., an RRC recovery complete message, an RRC setup complete message) to the wireless communication node, the sixth message including QoE buffer information. The QoE buffer information of the sixth message may include at least one of the following: a 1-bit indicator indicating that the buffer of the wireless communication device may not be empty; QoE session information; the number of QoE reports; the QoE report size for one QoE session; data about other QoE parameter related data; or the size of the buffer.

[0008] In some embodiments, after sending the sixth message, the wireless communication device may switch itself to the RRC_CONNECTED state. The wireless communication device may receive a seventh message (e.g., RRC message 2, RRC reconfiguration message) from the wireless communication node, the seventh message including QoE requirement information. The QoE requirement information may include at least one of the following: an application (APP) layer identifier (ID); QoE buffer information; or a QoE reference ID. In response to receiving the seventh message, the wireless communication device may send an eighth message (e.g., RRC message 3) to the wireless communication node, the eighth message including confirmation information.

[0009] In some embodiments, the wireless communication node (eg, BS) may receive a first message from a wireless communication device (eg, UE), the first message including QoE buffered data. The QoE buffered data may be stored by the wireless communication device. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Various example embodiments of the present technical solution will be described in detail below with reference to the following drawings. The drawings are provided for illustrative purposes only and only depict example embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be regarded as limiting the breadth, scope or applicability of the present technical solution. It should be noted that for clarity and ease of description, these drawings are not necessarily drawn to scale.

[0011] Figure 1 An exemplary cellular communication network is shown in which the techniques disclosed herein may be implemented according to an embodiment of the present disclosure.

[0012] Figure 2 A block diagram of an example base station and user terminal equipment according to some embodiments of the present disclosure is shown.

[0013] Figure 3 is a sequence diagram showing recorded QoE measurements according to an embodiment of the present disclosure.

[0014] Figure 4 is a sequence diagram showing recorded QoE measurements according to an embodiment of the present disclosure.

[0015] Figure 5 is a sequence diagram showing recorded QoE measurements according to an embodiment of the present disclosure.

[0016] Figure 6 is a sequence diagram showing recorded QoE measurements according to an embodiment of the present disclosure.

[0017] Figure 7 is a sequence diagram showing recorded QoE measurements according to an embodiment of the present disclosure.

[0018] Figure 8 is a sequence diagram showing recorded QoE measurements according to an embodiment of the present disclosure.

[0019] Fig. 9 is a sequence diagram showing recorded QoE measurements according to an embodiment of the present disclosure.

[0020] Fig.10 is a sequence diagram showing recorded QoE measurements according to an embodiment of the present disclosure.

[0021] Fig.11 is a sequence diagram showing recorded QoE measurements according to an embodiment of the present disclosure.

[0022] Fig.12 is a sequence diagram showing recorded QoE measurements according to an embodiment of the present disclosure.

[0023] Fig.13 is a sequence diagram showing recorded QoE measurements according to an embodiment of the present disclosure.

[0024] Fig.14 is a sequence diagram showing recorded QoE measurements according to an embodiment of the present disclosure.

[0025] Fig.15 is a sequence diagram showing recorded QoE measurements according to an embodiment of the present disclosure.

[0026] Fig.16 is a sequence diagram showing recorded QoE measurements according to an embodiment of the present disclosure.

[0027] Fig.17 is a sequence diagram showing recorded QoE measurements according to an embodiment of the present disclosure.

[0028] Fig.18 is a sequence diagram showing recorded QoE measurements according to an embodiment of the present disclosure.

[0029] Fig.19 A flow chart of an example method for recorded QoE measurements according to an embodiment of the present disclosure is presented. DETAILED DESCRIPTION

[0030] 1. Mobile Communication Technology and Environment

[0031] Figure 1 An example wireless communication network and / or system 100 is shown in which the techniques disclosed herein may be implemented according to an embodiment of the present disclosure. In the following discussion, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as "network 100". Such an example network 100 includes a base station 102 (hereinafter referred to as "BS 102"; also referred to as a wireless communication node) and a user terminal device 104 (hereinafter referred to as "UE 104"; also referred to as a wireless communication device), which may communicate with each other via a communication link 110 (e.g., a wireless communication channel) and a cluster of cells 126, 130, 132, 134, 136, 138 and 140 covering a geographic area 101. In Figure 11, BS 102 and UE 104 are contained within respective geographic boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating with its allocated bandwidth to provide adequate wireless coverage to its intended users.

[0032] For example, BS 102 may operate under an allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 may communicate via downlink radio frames 118 and uplink radio frames 124, respectively. Each radio frame 118 / 124 may be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In the present disclosure, BS 102 and UE 104 are described herein as non-limiting examples of "communication nodes", and generally, they may practice the methods disclosed herein. According to various embodiments of the present technical solution, such communication nodes may be capable of wireless and / or wired communication.

[0033] Figure 2 A block diagram of an exemplary wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) according to some embodiments of the present technology is shown. The system 200 may include components and elements configured to support known or conventional operating features, which need not be described in detail herein. In an illustrative embodiment, as described above, the system 200 may be used in applications such as Figure 1 Data symbols are communicated (eg, transmitted and received) in the wireless communication environment 100 of the wireless communication environment.

[0034] The system 200 generally includes a base station 202 (hereinafter referred to as "BS 202") and a user terminal device 204 (hereinafter referred to as "UE 204"). BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each of which is coupled to and interconnected with each other via a data communication bus 220 as needed. UE 204 includes a UE (user terminal) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each of which is coupled to and interconnected with each other via a data communication bus 240 as needed. BS 202 communicates with UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for transmitting the data herein.

[0035] As will be appreciated by those skilled in the art, the system 200 may also include Figure 2Any number of modules outside the modules shown. It will be appreciated by those skilled in the art that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented with hardware, computer-readable software, firmware, or any actual combination thereof. In order to clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described according to their functions. This functionality is implemented in the form of hardware, firmware, or software, depending on the specific application and design constraints imposed on the entire system. People familiar with this concept can implement such functionality in an appropriate manner for each specific application, but such implementation decisions should not be interpreted as limiting the scope of this disclosure.

[0036] According to some embodiments, the UE transceiver 230 may be referred to herein as an "uplink" transceiver 230, which includes a radio frequency (RF) transmitter and an RF receiver, each of which includes a circuit system coupled to an antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or uplink receiver to the uplink antenna in a time division duplex manner. Similarly, according to some embodiments, the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210, which includes an RF transmitter and an RF receiver, each of which includes a circuit system coupled to an antenna 212. The downlink duplex switch may alternately couple the downlink transmitter or receiver to the downlink antenna 212 in a time division duplex manner. The operation of the two transceiver modules 210 and 230 may be coordinated in time so that the uplink receiver circuit system is coupled to the uplink antenna 232 so as to receive transmissions on the wireless transmission link 250 while the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operation of the two transceivers 210 and 230 can be coordinated in time such that a downlink receiver coupled to the downlink antenna 212 receives transmissions on the wireless transmission link 250 at the same time as an uplink transmitter coupled to the uplink antenna 232. In some embodiments, there is closed time synchronization with a minimum guard time between changes in duplex direction.

[0037] The UE transceiver 230 and the base station transceiver 210 are configured to communicate via a wireless data communication link 250 and cooperate with an appropriately configured RF antenna arrangement 212 / 232 capable of supporting a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as long-term evolution (LTE) and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to specific standards and associated protocols in application. Instead, the UE transceiver 230 and the base station transceiver 210 can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0038] According to various embodiments, BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femtocell or a microbase station. In some embodiments, UE 204 may be embodied in various types of user equipment, such as a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, a wearable computing device, etc. Processor modules 214 and 236 may be implemented or realized with the following designed to perform the functions described herein: a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, a discrete gate or transistor logic, a discrete hardware component or any combination thereof. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of computing devices, for example, a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a digital signal processor core, or any other such configuration.

[0039] In addition, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be implemented directly in hardware, firmware, software modules executed by processor modules 214 and 236, respectively, or in any practical combination thereof. Memory modules 216 and 234 may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 may be coupled to processor modules 210 and 230, respectively, so that processor modules 210 and 230 may read information from and write information to memory modules 216 and 234, respectively. Memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0040] The network communication module 218 generally represents the hardware, software, firmware, processing logic and / or other components of the base station 202, which can perform two-way communication between the base station transceiver 210 and other network components and communication nodes configured to communicate with the base station 202. For example, the network communication module 218 can be configured to support Internet or WiMAX traffic. In a typical deployment, but not limited to, the network communication module 218 provides an 802.3 Ethernet interface so that the base station transceiver 210 can communicate with a traditional Ethernet-based computer network. In this way, the network communication module 218 may include a physical interface (e.g., a mobile switching center (MSC)) for connecting to a computer network. The terms "configured for", "configured to" and their variations as used herein with respect to a specified operation or function refer to a device, component, circuit, structure, machine, signal, etc. that is physically constructed, programmed, formatted and / or arranged to perform a specified operation or function.

[0041] The Open Systems Interconnection (OSI) model (referred to herein as the "Open Systems Interconnection Model") is a concept and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) that are open to interconnection and communication with other systems. The model is divided into seven subcomponents or layers, each of which represents a conceptual set of services provided to its upper and lower layers. The OSI model also defines a logical network and effectively describes computer packet transmission using different layer protocols. The OSI model may also be referred to as a seven-layer OSI model or a seven-layer model. In some embodiments, the first layer may be a physical layer. In some embodiments, the second layer may be a medium access control (MAC) layer. In some embodiments, the third layer may be a radio link control (RLC) layer. In some embodiments, the fourth layer may be a packet data convergence protocol (PDCP) layer. In some embodiments, the fifth layer may be a radio resource control (RRC) layer. In some embodiments, the sixth layer may be a non-access stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer is another layer.

[0042] Various example embodiments of the present technical solution are described below with reference to the accompanying drawings so that those of ordinary skill in the art can make and use the present technical solution. It is obvious to those of ordinary skill in the art that, after reading this disclosure, various changes or modifications can be made to the examples described herein without departing from the scope of the present technical solution. Therefore, the present technical solution is not limited to the exemplary embodiments and applications described and shown herein. In addition, the specific order or hierarchy of the steps in the method disclosed herein is merely an exemplary manner. Based on design preferences, the specific order or hierarchy of the steps of the disclosed method or process can be rearranged while still within the scope of the present technical solution. Therefore, it will be understood by those of ordinary skill in the art that the methods and techniques disclosed herein present various steps or actions in an example order, and unless otherwise expressly stated, the present technical solution is not limited to the specific order or hierarchy presented.

[0043] 2. System and method for recorded QoE measurements

[0044] INACTIVE / IDLE recorded QoE can be supported. When the UE is in the RRC_CONNECTED state, QoE can be activated and data can be collected. Due to the support of new QoE service types (e.g., multicast and broadcast service (MBS)), enterprises can believe that in some cases, it is necessary to perform QoE in any RRC state (e.g., RRC_IDLE, RRC_CONNECTED, or RRC_INACTIVE). In the present disclosure, a new QoE (e.g., recorded QoE) is introduced. In some cases, the recorded QoE can be performed in a non-CONNECTED state. The configuration and reporting of the recorded QoE are discussed as follows. Based on Rel-17, multicast services can only be performed in the RRC_CONNECTED state. However, the UE can use broadcast services in any RRC state. In Rel-18, multicast and broadcast services (MBS) can be introduced as a new service type in QoE. New air interface (NR) QoE is also introduced in Rel-17. NR QoE can only perform QoE measurements when the UE is in RRC_CONNECTED. When the UE is in RRC_CONNECTED, the network (NW) can configure QoE for a specific application for the UE. When the UE starts the application, the QoE can be activated and start measuring QoE data.

[0045] In some of the following implementation examples, the recorded QoE may be performed in a CONNECTED state (e.g., RRC_CONNECTED) or a non-CONNECTED state (e.g., RRC_INACTIVE, RRC_IDLE). The network may use one of the following combinations (e.g., service type, state indicator, or sub-service type) to distinguish between non-CONNECTED recorded QoE and CONNECTED recorded QoE.

[0046] In some embodiments, the service type may be MBS, broadcast, or multicast. The state indicator may be the QoE recorded in a non-CONNECTED mode (e.g., non-CONNECTED). When the recorded QoE configuration indicates that the service type is MBS and the state indicator is non-CONNECTED, the recorded QoE can only be performed in the non-CONNECTED state. When the recorded QoE configuration only indicates that the service type is MBS, the recorded QoE can only be performed in the CONNECTED state.

[0047] In some embodiments, the service type may be MBS, broadcast, or multicast. The state indicator may be the QoE recorded in a CONNECTED mode (e.g., CONNECTED). When the recorded QoE configuration indicates that the service type is MBS and the state indicator is CONNECTED, the recorded QoE may be performed in the CONNECTED state. When the recorded QoE configuration only indicates that the service type is MBS, the recorded QoE may only be performed in a non-CONNECTED state. A service type (e.g., MBS, broadcast, or multicast) with a non-CONNECTED indicator may indicate that the UE may perform / trigger the recorded QoE measurement in a non-CONNECTED state. A service type (e.g., MBS, broadcast, or multicast) without a non-CONNECTED indicator may indicate that the UE cannot perform the recorded QoE in a non-CONNECTED state. A service type (e.g., MBS, broadcast, or multicast) with a CONNECTED indicator may indicate that the UE may perform QoE measurements and may trigger QoE reporting in a CONNECTED state. A service type (e.g., MBS, broadcast, or multicast) without a CONNECTED indicator may indicate that the UE may perform QoE measurements and may trigger QoE reporting in a non-CONNECTED state. A service type (e.g., MBS, broadcast, or multicast) with / without any RRC state indicator may indicate that the UE may perform QoE measurements and may trigger QoE reporting regardless of the RRC state. If the network does not configure the service type (e.g., broadcast) with an indicator, QoE may perform QoE measurements and may trigger QoE reporting in a non-CONNECTED state. If the network configures the service type (e.g., broadcast) with an indicator that allows a non-CONNECTED state QoE flag, QoE may perform QoE measurements and may trigger QoE reporting in a non-CONNECTED state. If the indicator does not allow a CONNECTED state QoE flag, QoE with a service type such as broadcast may perform QoE measurements and may trigger QoE reporting in a CONNECTED state.

[0048] The subservice type can be broadcast (BC) or multicast (MC). In this alternative, the network can use different subservice types to distinguish the appropriate operating state instead of using service type and state indicators. Broadcast recorded QoE can be performed in any RRC state. Multicast recorded QoE can be performed in the CONNECTED state. A subservice type without an indicator (e.g., broadcast or multicast) can indicate that the UE can perform multicast-related recorded QoE measurements in the CONNECTED state and can trigger QoE reporting. A subservice type without an indicator (e.g., broadcast or multicast) can indicate that the UE can perform broadcast-related recorded QoE measurements and can trigger QoE reporting in any RRC state.

[0049] The terms used above (e.g., MBS and status indicator) may not indicate that the protocol needs to use exactly the same words. For example, the protocol may use multicast and broadcast services instead of MBS, or use indicators instead of status indicators. The following implementation examples may use service type (MBS) and status indicator (non-CONNECTED indicator) to show how to configure QoE recorded by CONNECTED or how to configure QoE recorded by non-CONNECTED. Other alternatives shown above may use similar configuration processes.

[0050] For the QoE recorded by non-CONNECTED, execution in a non-CONNECTED state (e.g., RRC_INACTIVE or RRC_IDLE) can be explained as follows. The recorded QoE can be activated in a non-CONNECTED state. In some embodiments, when the UE switches to RRC_CONNECTED, all non-CONNECTED recorded QoE can be stopped. In some embodiments, when the UE switches to RRC_CONNECTED, the non-deactivated QoE may no longer be activated. Nevertheless, the ongoing non-CONNECTED recorded QoE may continue until the session ends or is modified by the network (e.g., rewritten, fully configured). In some embodiments, the UE can trigger a QoE report in the RRC_INACTIVE state or the RRC_IDLE state. When the UE is in the RRC_CONNECTED state, real QoE reporting can be performed. In certain embodiments, when the UE remains in the RRC_INACTIVE state or the RRC_IDLE state, the UE may not upload a QoE report to the network.

[0051] In addition, the definition of short IP information can also be used in several implementation examples of the present disclosure. Short IP information can be a tag that can be used to let the UE know / be notified of the destination of the generated recorded QoE report. Short IP information can be a bit string or a number. Before the recorded QoE is configured, information about the mapping relationship between the short IP information and the real IP address can be configured to the relevant NG-RAN node through operation management and maintenance (OAM). The NG-RAN node can maintain the mapping relationship locally. More vivid examples can be used to explain short IP information, real IP addresses, and information about the mapping relationship.

[0052] Table 1 shows an example mapping relationship between short IP information and real IP addresses (bit strings).

[0053] Short IP information IP address "...01” 192.168.0.1 "...10” 192.168.0.2 ... ...

[0054] Table 1 Table 1 shows an example mapping relationship between short IP information and real IP addresses (numbers).

[0055] Short IP information IP address Integer: 1 192.168.1.1 Floating point number: 123 192.168.1.2 ... ...

[0056] Table 2

[0057] Implementation Example 1 - Recorded QoE configured with non-CONNECTED indicator (non-CONNECTED recorded QoE)

[0058] Figure 3 is a sequence diagram showing a process for recorded QoE according to some embodiments. The process may be performed by the UEAPP layer, the UE access layer (AS), the next generation radio access network (NG-RAN) node, the core network (CN), and the operation and maintenance (OAM). Note that the process is only an example and is not intended to limit the present disclosure. Therefore, it should be understood that the process may be performed in Figure 3 Additional operations (eg, blocks) may be provided before, during, and after the processes of the present invention, some operations may be omitted, some operations may be performed simultaneously with other operations, and some other operations may be briefly described herein.

[0059] In step 1, before the recorded QoE configuration, the UE may be in RRC_CONNECTED state. The recorded QoE configuration may trigger QoE reporting behavior in any RRC condition / state. When the UE enters the RRC_CONNECTED state, the UE may send a QoE report to the network.

[0060] In step 2, the OAM may send the recorded QoE configuration to the CN via a non-standardized message.

[0061] In step 3, the CN may send an NG Application Protocol (AP) message 1 to the NG-RAN node within the recorded QoE configuration message. The NGAP message 1 may include at least one of the following information: a QoE reference; a service type; a status indicator (non-CONNECTED indicator); a measurement collection entity (MCE) IP address; or a QoE configuration container. The QoE reference ID may be configured by OAM. In some steps, the recorded QoE may be marked with / utilized / applied using the QoE reference ID. The service type may be MBS, broadcast, or multicast. In this implementation example, the service type may be MBS. In some alternative examples, the service type may also be broadcast or multicast. The status indicator may be a non-CONNECTED indicator. The non-CONNECTED indicator may indicate that the recorded QoE measurement may be performed / triggered when the UE is in the RRC_IDLE state and the RRC_INACTIVE state. In some embodiments, when the recorded QoE generates QoE measurement data, the data may be forwarded to the MCE IP address. The QoE configuration container may contain / include the fully documented QoE configuration. Other QoE configuration parameters contained / included in step 3 of the procedure / call flow may be discussed in other implementation examples.

[0062] In step 4, after the NG-RAN node receives the recorded QoE configuration from the CN, the NG-RAN may send an RRC message 1 to the UE. The RRC message 1 may include at least one of the following information: an APP layer ID; a service type; a status indicator (non-CONNECTED indicator); a QoE configuration container; or a short IP information. The recorded QoE may be marked using / utilizing / applying an RRC layer ID. In this implementation example, the service type may be MBS. In some alternative examples, the service type may also be broadcast or multicast. The status indicator may be a non-CONNECTED indicator. The non-CONNECTED indicator may indicate that the recorded QoE measurement may be performed / triggered when the UE is in the RRC_IDLE state and the RRC_INACTIVE state. The NG-RAN may use / utilize / apply the short IP information to retrieve the real IP address of the MCE. In some embodiments, the short IP information may also be used as a status indicator (non-CONNECTED indicator). When the UE receives the service type and the short IP information, the UE may know / notice / realize that the recorded QoE can only be performed in the non-CONNECTED state. In this case, the status indicator (non-CONNECTED indicator) may be omitted in the RRC configuration message. The QoE configuration container may contain / include the fully recorded QoE configuration. For the short IP information used as a status indicator, the QoE configuration in step 4 may contain / include at least one of the following information: QoE reference, service type, short IP information, or QoE configuration container.

[0063] In step 5, the UE may receive the QoE configuration. The UE AS layer may send the received QoE configuration to the UE APP layer via an ATtention (AT) command. The AT command may be used to control the mobile terminal (MT) function and the global system for mobile (GSM) network service / universal mobile telecommunications system (UMTS) network service from the terminal equipment (TE) through the terminal adapter (TA).

[0064] In step 6, the UE may maintain the QoE configuration in the RRC_IDLE state or the RRC_INACTIVE state and may start the recorded QoE measurement when the multicast and broadcast service (MBS) is initiated.

[0065] In step 7, the UE APP layer may reply to the AT command with a message (e.g., AT command 2). In step 8, the UE AS layer may reply to the RRC message with a message (e.g., RRC message 2). In step 9, the NG-RAN node may reply to the NGAP message with a message (e.g., NGAP message 2). In some embodiments, an ACK message may be used to indicate that a previous message was successfully received. The ACK message may be included in the message. The ACK message may be empty (e.g., no relevant information) or an indicator (e.g., indicating that everything is working properly).

[0066] Table 3 shows the key points of step 3, including the service type and the non-CONNECTED indicator.

[0067]

[0068]

[0069] Table 3

[0070] Implementation Example 2 - Recorded QoE without non-CONNECTED indicator configured (CONNECTED recorded QoE)

[0071] Figure 4 is a sequence diagram showing a process for recorded QoE according to some embodiments. The process may be performed by the UEAPP layer, UE AS, NG-RAN node, CN, and OAM. Note that the process is merely an example and is not intended to limit the present disclosure. Therefore, it should be understood that the process may be performed in Figure 4 Additional operations (e.g., blocks) are provided before, during, and after the process, some operations may be omitted, some operations may be performed simultaneously with other operations, and some other operations may be briefly described herein. In the absence of a non-CONNECTED indicator, the recorded QoE can only be performed when the UE is in the RRC_CONNECTED state.

[0072] In step 1, before the recorded QoE configuration, the UE may be in RRC_CONNECTED state. The recorded QoE configuration may trigger QoE reporting behavior in any RRC condition / state. When the UE enters the RRC_CONNECTED state, the UE may send a QoE report to the network.

[0073] In step 2, the OAM may send the recorded QoE configuration to the CN via a non-standardized message.

[0074] In step 3, the CN may send an NG Application Protocol (AP) message 1 to the NG-RAN node within the recorded QoE configuration message. The NGAP message 1 may include at least one of the following information: a QoE reference; a service type; an MCE IP address; or a QoE configuration container. The QoE reference ID may be configured by OAM. In some steps, the recorded QoE may be marked with / utilized / applied using the QoE reference ID. The service type may be MBS, broadcast, or multicast. In this implementation example, the service type may be MBS. In some alternative examples, the service type may also be broadcast or multicast. In some embodiments, when the recorded QoE generates QoE measurement data, the data may be forwarded to the MCE IP address. The QoE configuration container may contain / include the fully recorded QoE configuration. Other QoE configuration parameters included / included in step 3 of the process / call flow may be discussed in other implementation examples. In some embodiments, the QoE configuration in step 3 may include at least one of the following information: QoE reference; subservice type (e.g., broadcast or multicast); MCE IP address; or QoE configuration container. In some embodiments, when the state indicator is missing in the configuration, the UE can only trigger / perform QoE measurement in the RRC_CONNECTED state.

[0075] In step 4, after the NG-RAN node receives the recorded QoE configuration from the CN, the NG-RAN may send an RRC message 1 to the UE. The RRC message 1 may include at least one of the following information: an APP layer ID; a service type; or a QoE configuration container. The recorded QoE may be marked using / utilizing / applying an RRC layer ID. In this implementation example, the service type may be MBS. In some alternative examples, the service type may also be broadcast or multicast. The QoE configuration container may contain / include the complete recorded QoE configuration. In some embodiments, the QoE configuration in step 4 may include at least one of the following information: an APP layer ID; a sub-service type (e.g., multicast); or a QoE configuration container. In some embodiments, if short IP information is used as an indicator, the QoE configuration in step 4 may contain / include at least one of the following information: an APP layer ID; a service type; or a QoE configuration container. If short IP information is not present in the QoE configuration message, the recorded QoE can only be performed in the RRC_CONNECTED state.

[0076] In step 5, the UE may receive the QoE configuration. The UE AS layer may send the received QoE configuration to the UE APP layer via an AT command. The AT command may be used to control the MT function and GSM network service / UMTS network service from the TE through the TA.

[0077] In step 6, the UE may maintain the QoE configuration in the RRC_CONNECTED state and may start the recorded QoE measurements when the multicast and broadcast service (MBS) is initiated.

[0078] In step 7, the UE APP layer may reply to the AT command with a message (e.g., AT command 2). In step 8, the UE AS layer may reply to the RRC message with a message (e.g., RRC message 2). In step 9, the NG-RAN node may reply to the NGAP message with a message (e.g., NGAP message 2). In some embodiments, ACK information may be used to indicate that the previous message was successfully received. ACK information may be included in the message. ACK information may be empty (e.g., no relevant information) or an indicator (e.g., indicating that everything is working properly).

[0079] Table 4 shows the key points of step 3, with the service type and non-CONNECTED indicator.

[0080]

[0081] Table 4

[0082] In addition to the above two implementation examples, there may be another way to define the indicator. The indicator can be used to indicate / specify whether the recorded QoE can be performed in the following two situations: (i) the recorded QoE can be performed in RRC_CONNECTED, RRC_INACTIVE, or RRC_IDLE; (ii) the recorded QoE can be performed in RRC_CONNECTED. With the indicator, the recorded QoE can be performed in any RRC state (e.g., RRC_CONNECTED, RRC_INACTIVE, or RRC_IDLE). In the absence of the indicator, the recorded QoE can only be performed in RRC_CONNECTED. In some embodiments, with the indicator, the recorded QoE can be performed in RRC_CONNECTED. In the absence of the indicator, the recorded QoE can be performed in any RRC state. "Performed in any RRC state" can indicate / mean that the recorded QoE can be activated in any RRC state and the recorded QoE data can be kept measured. In addition to the indicator, the sub-service type (e.g., broadcast or multicast) can also be used here. For the QoE recorded for "broadcast", it can be performed in any RRC state. For the QoE recorded for "multicast", it can only be performed in the CONNECTED state. In some embodiments, the short IP information can also be used as an all RRC state indicator in certain messages.

[0083] Implementation Example 3 - Recorded QoE with any status indicator configured (Recorded QoE for any RRC state)

[0084] Figure 5 is a sequence diagram showing a process for recorded QoE according to some embodiments. The process may be performed by the UEAPP layer, UE AS, NG-RAN node, CN, and OAM. Note that the process is merely an example and is not intended to limit the present disclosure. Therefore, it should be understood that the process may be performed in Figure 5 Additional operations (eg, blocks) may be provided before, during, and after the processes of the present invention, some operations may be omitted, some operations may be performed simultaneously with other operations, and some other operations may be briefly described herein.

[0085] In step 1, before the recorded QoE configuration, the UE may be in RRC_CONNECTED state. The recorded QoE configuration may trigger QoE reporting behavior in any RRC condition / state. When the UE enters the RRC_CONNECTED state, the UE may send a QoE report to the network.

[0086] In step 2, the OAM may send the recorded QoE configuration to the CN via a non-standardized message.

[0087] In step 3, the CN may send an NG Application Protocol (AP) message 1 to the NG-RAN node within the recorded QoE configuration message. The NGAP message 1 may include at least one of the following information: a QoE reference; a service type; a status indicator (any status indicator); an MCE IP address; or a QoE configuration container. The QoE reference ID may be configured by OAM. In some steps, the recorded QoE may be marked with / utilized / applied using the QoE reference ID. The service type may be MBS, broadcast, or multicast. In this implementation example, the service type may be MBS. In some alternative examples, the service type may also be broadcast or multicast. The status indicator may be any status indicator. Any status indicator may indicate that the recorded QoE measurement may be performed / triggered in any RRC state (e.g., RRC_CONNECTED state, RRC_INACTIVE state, or RRC_IDLE state). In some embodiments, when the recorded QoE generates QoE measurement data, the data may be forwarded to the MCE IP address. The QoE configuration container may contain / include a fully documented QoE configuration. Other QoE configuration parameters contained / included in step 3 of the process / call flow may be discussed in other implementation examples. In some embodiments, the QoE configuration in step 3 may include at least one of the following information: a QoE reference; a subservice type (e.g., broadcast); an MCE IP address; or a QoE configuration container.

[0088] In step 4, after the NG-RAN node receives the recorded QoE configuration from the CN, the NG-RAN may send an RRC message 1 to the UE. The RRC message 1 may include at least one of the following information: an APP layer ID; a service type; a status indicator (any status indicator); a short IP information; or a QoE configuration container. The recorded QoE may be marked using / utilizing / applying an RRC layer ID. In this implementation example, the service type may be MBS. In some alternative examples, the service type may also be broadcast or multicast. The status indicator may be any status indicator. Any status indicator may indicate that the recorded QoE may be performed when the UE is in the RRC_IDLE state and the RRC_INACTIVE state. The NG-RAN may use / utilize / apply the short IP information to retrieve the real IP address of the MCE. The QoE configuration container may contain / include the complete recorded QoE configuration. In some embodiments, the QoE configuration in step 4 may include at least one of the following information: an APP layer ID; a subservice type (e.g., broadcast); a short IP information; or a QoE configuration container. In some embodiments, if the short IP information is used as an indicator, the QoE configuration in step 4 may contain / include at least one of the following information: APP layer ID; service type; short IP information; or QoE configuration container.

[0089] In step 5, the UE may receive the QoE configuration. The UE AS layer may send the received QoE configuration to the UE APP layer via an AT command. The AT command may be used to control the MT function and GSM network service / UMTS network service from the TE through the TA.

[0090] In step 6, the UE may maintain the QoE configuration and may start the recorded QoE measurements when the Multicast and Broadcast Service (MBS) starts the indicated state.

[0091] In step 7, the UE APP layer may reply to the AT command with a message (e.g., AT command 2). In step 8, the UE AS layer may reply to the RRC message with a message (e.g., RRC message 2). In step 9, the NG-RAN node may reply to the NGAP message with a message (e.g., NGAP message 2). In some embodiments, ACK information may be used to indicate that the previous message was successfully received. ACK information may be included in the message. ACK information may be empty (e.g., no relevant information) or an indicator (e.g., indicating that everything is working properly).

[0092] Table 5 shows the key points of step 3, with the service type and any status indicators.

[0093]

[0094]

[0095] Table 5

[0096] Table 6 shows the key points of step 3, with the service type and CONNECTED indicator. With the indicator, the recorded QoE can only be performed under RRC_CONNECTED. In this case, the QoE configuration may not contain the indicator.

[0097]

[0098]

[0099] Table 6

[0100] Implementation Example 4 - Recorded QoE with New Radio (NR) QoE Flow

[0101] Figure 6 is a sequence diagram showing a process for recorded QoE according to some embodiments. The process may be performed by the UEAPP layer, UE AS, NG-RAN node, CN, and OAM. Note that the process is merely an example and is not intended to limit the present disclosure. Therefore, it should be understood that the process may be performed in Figure 6 Additional operations (eg, blocks) are provided before, during, and after the process, some operations may be omitted, some operations may be performed simultaneously with other operations, and some other operations may be briefly described herein. The recorded QoE can only be performed in the RRC_CONNECTED state.

[0102] In step 1, the UE may be in RRC_CONNECTED state.

[0103] In step 2, OAM may send the recorded QoE configuration to CN. The recorded QoE configuration may trigger QoE reporting behavior in any RRC condition / state. When the UE enters the RRC_CONNECTED state, the UE may send a QoE report to the network.

[0104] In step 3, the CN may send an NG Application Protocol (AP) message 1 to the NG-RAN node. In addition to the service type being MBS, multicast or broadcast, the New Radio (NR) QoE Configuration IE may be reused for the recorded QoE configuration.

[0105] In step 4, the NG-RAN may send an RRC message 1 to the UE. In addition to the service type being MBS, multicast or broadcast, the New Radio (NR) QoE Configuration IE may be reused for the recorded QoE configuration.

[0106] In step 5 and step 6, the UE AS layer and the UE APP layer may exchange information on the recorded QoE via an AT command.

[0107] In step 7, the UE AS layer may reply with a message (e.g., RRC message 2) for RRC message 1. In step 8, the NG-RAN node may reply with a message (e.g., NGAP message 2) for NGAP message 1. In some embodiments, ACK information may be used to indicate that the previous message was successfully received. ACK information may be included in the message. ACK information may be empty (e.g., no relevant information) or an indicator (e.g., indicating that everything is working properly).

[0108] Table 7 shows the key points of step 3, with sub-service type (eg, broadcast).

[0109]

[0110] Table 7

[0111] Table 8 shows the key points of step 3, with sub-service type (eg, multicast).

[0112]

[0113]

[0114] Table 8 and Table 9 show the key points of step 3, with sub-service type (e.g., MBS).

[0115]

[0116] Table 9

[0117] Implementation Example 5—Recorded QoE with CONNECTED Indicator (CONNECTED Recorded QoE)

[0118] Figure 7 is a sequence diagram showing a process for recorded QoE according to some embodiments. The process may be performed by the UEAPP layer, UE AS, NG-RAN node, CN, and OAM. Note that the process is merely an example and is not intended to limit the present disclosure. Therefore, it should be understood that the process may be performed in Figure 7 Additional operations (e.g., blocks) are provided before, during, and after the process of , some operations may be omitted, some operations may be performed simultaneously with other operations, and some other operations may be briefly described herein. This implementation example shares a similar process as described in implementation example 1 (e.g., service type with indicator).

[0119] In step 1, before the recorded QoE configuration, the UE may be in RRC_CONNECTED state.

[0120] In step 2, OAM may send the recorded QoE configuration to CN via a non-standardized message. The recorded QoE configuration may trigger QoE reporting behavior in any RRC condition / state. When the UE enters the RRC_CONNECTED state, the UE may send a QoE report to the network.

[0121] In step 3, the CN may send an NG Application Protocol (AP) message 1 to the NG-RAN node within the recorded QoE configuration message. The NGAP message 1 may include at least one of the following information: QoE reference; service type; status indicator (CONNECTED indicator); MCE IP address; or QoE configuration container. The QoE reference ID may be configured by OAM. In some steps, the QoE reference ID may be used / utilized / applied to mark the recorded QoE. The service type may be MBS, broadcast, or multicast. In this implementation example, the service type may be MBS. In some alternative examples, the service type may also be broadcast or multicast. The status indicator may be a CONNECTED indicator. The CONNECTED indicator may indicate that the recorded QoE may be executed / triggered when the UE is in the RRC_CONNECTED state. In some embodiments, if the CONNECTED indicator is used without the status indicator, the recorded QoE may be performed / triggered when the UE is in a non-CONNECTED state (e.g., RRC_IDLE or RRC_INACTIVE). In some embodiments, when the recorded QoE generates QoE measurement data, the data may be forwarded to the MCE IP address. The QoE configuration container may contain / include the complete recorded QoE configuration. Other QoE configuration parameters included / included in step 3 of the process / call flow may be discussed in other implementation examples.

[0122] In step 4, after the NG-RAN node receives the recorded QoE configuration from the CN, the NG-RAN may send an RRC message 1 to the UE. The RRC message 1 may include at least one of the following information: an APP layer ID; a service type; a status indicator (CONNECTED indicator); a short IP information; or a QoE configuration container. The recorded QoE may be marked using / utilizing / applying an RRC layer ID. In this implementation example, the service type may be MBS. In some alternative examples, the service type may also be broadcast or multicast. The status indicator may be a CONNECTED indicator. The CONNECTED indicator may indicate that the recorded QoE may be executed when the UE is in the RRC_CONNECTED state. In some embodiments, if the CONNECTED indicator is used without the status indicator, the recorded QoE may be executed / triggered when the UE is in a non-CONNECTED state (e.g., RRC_IDLE or RRC_INACTIVE). The NG-RAN may use / utilize / apply the short IP information to retrieve the real IP address of the MCE. In some embodiments, the short IP information may also be used as a status indicator (CONNECTED indicator). When the UE receives the service type and the short IP information, the UE may know / notice / realize that the recorded QoE can only be performed in the CONNECTED state. In this case, the status indicator (CONNECTED indicator) may be omitted in the RRC configuration message. The QoE configuration container may contain / include the fully recorded QoE configuration. For the short IP information used as a status indicator, the QoE configuration in step 4 may contain / include at least one of the following information: QoE reference, service type, short IP information, or QoE configuration container. In some embodiments, if the short IP information is used as a status indicator, the short IP information may not be forwarded to the UE.

[0123] In step 5, the UE may receive the QoE configuration. The UE AS layer may send the received QoE configuration to the UE APP layer via an AT command. The AT command may be used to control the MT function and GSM network service / UMTS network service from the TE through the TA.

[0124] In step 6, the UE may maintain the QoE configuration in the RRC_IDLE state or the RRC_INACTIVE state and may start the recorded QoE measurement when the multicast and broadcast service (MBS) is initiated.

[0125] In step 7, the UE APP layer may reply to the AT command with a message (e.g., AT command 2). In step 8, the UE AS layer may reply to the RRC message with a message (e.g., RRC message 2). In step 9, the NG-RAN node may reply to the NGAP message with a message (e.g., NGAP message 2). In some embodiments, ACK information may be used to indicate that the previous message was successfully received. ACK information may be included in the message. ACK information may be empty (e.g., no relevant information) or an indicator (e.g., indicating that everything is working properly).

[0126] Table 10 shows the key points of step 3.

[0127]

[0128]

[0129] Table 10

[0130] Implementation Example 6—Recorded QoE without CONNECTED indicator (non-CONNECTED recorded QoE)

[0131] Figure 8 is a sequence diagram showing a process for recorded QoE according to some embodiments. The process may be performed by the UEAPP layer, UE AS, NG-RAN node, CN, and OAM. Note that the process is merely an example and is not intended to limit the present disclosure. Therefore, it should be understood that the process may be performed in Figure 8 Additional operations (e.g., blocks) are provided before, during, and after the process, some operations may be omitted, some operations may be performed simultaneously with other operations, and some other operations may be briefly described herein. In the absence of a non-CONNECTED indicator, the recorded QoE can only be performed when the UE is in the RRC_CONNECTED state. This implementation example shares a similar process as described in implementation example 2 (e.g., service type without an indicator).

[0132] In step 1, before the recorded QoE configuration, the UE may be in RRC_CONNECTED state. The recorded QoE configuration may trigger QoE reporting behavior in any RRC condition / state. When the UE enters the RRC_CONNECTED state, the UE may send a QoE report to the network.

[0133] In step 2, the OAM may send the recorded QoE configuration to the CN via a non-standardized message.

[0134] In step 3, the CN may send an NG Application Protocol (AP) message 1 to the NG-RAN node within the recorded QoE configuration message. The NGAP message 1 may include at least one of the following information: a QoE reference; a service type; an MCE IP address; or a QoE configuration container. The QoE reference ID may be configured by OAM. In some steps, the recorded QoE may be marked with / utilized / applied using the QoE reference ID. The service type may be MBS, broadcast, or multicast. In this implementation example, the service type may be MBS. In some alternative examples, the service type may also be broadcast or multicast. In some embodiments, when the recorded QoE generates QoE measurement data, the data may be forwarded to the MCE IP address. The QoE configuration container may contain / include the fully recorded QoE configuration. Other QoE configuration parameters included / included in step 3 of the process / call flow may be discussed in other implementation examples. In some embodiments, the QoE configuration in step 3 may include at least one of the following information: a QoE reference; a sub-service type (eg, broadcast); an MCE IP address; or a QoE configuration container.

[0135] In step 4, after the NG-RAN node receives the recorded QoE configuration from the CN, the NG-RAN may send an RRC message 1 to the UE. The RRC message 1 may include at least one of the following information: an APP layer ID; a service type; a short IP information; or a QoE configuration container. The recorded QoE may be marked using / utilizing / applying an RRC layer ID. In this implementation example, the service type may be MBS. In some alternative examples, the service type may also be broadcast or multicast. The NG-RAN may use / utilize / apply the short IP information to retrieve the real IP address of the MCE. In some embodiments, the short IP information may also be used as a status indicator (non-CONNECTED indicator). When the UE receives the service type and the short IP information, the UE may know / notice / realize that the recorded QoE can only be performed in a non-CONNECTED state. In this case, the status indicator (non-CONNECTED indicator) may be omitted in the RRC configuration message. The QoE configuration container may contain / include the complete recorded QoE configuration. In some embodiments, the QoE configuration in step 4 may include at least one of the following information: APP layer ID; service type; short IP information; or QoE configuration container.

[0136] In step 5, the UE may receive the QoE configuration. The UE AS layer may send the received QoE configuration to the UE APP layer via an AT command. The AT command may be used to control the MT function and GSM network service / UMTS network service from the TE through the TA.

[0137] In step 6, the UE may maintain the QoE configuration in the RRC_CONNECTED state and may start the recorded QoE measurements when the multicast and broadcast service (MBS) is initiated.

[0138] In step 7, the UE APP layer may reply to the AT command with a message (e.g., AT command 2). In step 8, the UE AS layer may reply to the RRC message with a message (e.g., RRC message 2). In step 9, the NG-RAN node may reply to the NGAP message with a message (e.g., NGAP message 2). In some embodiments, ACK information may be used to indicate that the previous message was successfully received. ACK information may be included in the message. ACK information may be empty (e.g., no relevant information) or an indicator (e.g., indicating that everything is working properly).

[0139] Table 11 shows the key points of step 3.

[0140]

[0141] Table 11

[0142] Implementation Example 7—Recorded QoE with Sub-Service Type ("Multicast") configured (CONNECTED recorded QoE)

[0143] Fig. 9 is a sequence diagram showing a process for recorded QoE according to some embodiments. The process may be performed by the UEAPP layer, UE AS, NG-RAN node, CN, and OAM. Note that the process is merely an example and is not intended to limit the present disclosure. Therefore, it should be understood that the process may be performed in Fig. 9 Additional operations (eg, blocks) may be provided before, during, and after the processes of the present invention, some operations may be omitted, some operations may be performed simultaneously with other operations, and some other operations may be briefly described herein.

[0144] In step 1, before the recorded QoE configuration, the UE may be in RRC_CONNECTED state. The recorded QoE configuration may trigger QoE reporting behavior in any RRC condition / state. When the UE enters the RRC_CONNECTED state, the UE may send a QoE report to the network.

[0145] In step 2, the OAM may send the recorded QoE configuration to the CN via a non-standardized message.

[0146] In step 3, the CN may send an NG Application Protocol (AP) message 1 to the NG-RAN node within the recorded QoE configuration message. The NGAP message 1 may include at least one of the following information: a QoE reference; a subservice type; an MCE IP address; or a QoE configuration container. The QoE reference ID may be configured by OAM. In some steps, the recorded QoE may be marked with / utilized / applied using the QoE reference ID. The subservice type may be broadcast or multicast. In this implementation example, the subservice type may be multicast. In some embodiments, when the recorded QoE generates QoE measurement data, the data may be forwarded to the MCE IP address. The QoE configuration container may contain / include the complete recorded QoE configuration. Other QoE configuration parameters included / included in step 3 of the process / call flow may be discussed in other implementation examples.

[0147] In step 4, after the NG-RAN node receives the recorded QoE configuration from the CN, the NG-RAN may send an RRC message 1 to the UE. The RRC message 1 may include at least one of the following information: an APP layer ID; a sub-service type; or a QoE configuration container. The recorded QoE may be marked using / utilizing / applying an RRC layer ID. In this implementation example, the sub-service type may be multicast. The QoE configuration container may contain / include the complete recorded QoE configuration.

[0148] In step 5, the UE may receive the QoE configuration. The UE AS layer may send the received QoE configuration to the UE APP layer via an AT command. The AT command may be used to control the MT function and GSM network service / UMTS network service from the TE through the TA.

[0149] In step 6, the UE may maintain the QoE configuration in the RRC_CONNECTED state and may start the recorded QoE measurements when the multicast and broadcast service (MBS) is initiated.

[0150] In step 7, the UE APP layer may reply to the AT command with a message (e.g., AT command 2). In step 8, the UE AS layer may reply to the RRC message with a message (e.g., RRC message 2). In step 9, the NG-RAN node may reply to the NGAP message with a message (e.g., NGAP message 2). In some embodiments, ACK information may be used to indicate that the previous message was successfully received. ACK information may be included in the message. ACK information may be empty (e.g., no relevant information) or an indicator (e.g., indicating that everything is working properly).

[0151] Table 12 shows the key points of step 3.

[0152]

[0153]

[0154] Table 12

[0155] Implementation Example 8 - Recorded QoE configured with sub-service type ("broadcast") (recorded QoE in any state)

[0156] Fig.10 is a sequence diagram showing a process for recorded QoE according to some embodiments. The process may be performed by the UEAPP layer, UE AS, NG-RAN node, CN, and OAM. Note that the process is merely an example and is not intended to limit the present disclosure. Therefore, it should be understood that the process may be performed in Fig.10 Additional operations (eg, blocks) may be provided before, during, and after the processes of the present invention, some operations may be omitted, some operations may be performed simultaneously with other operations, and some other operations may be briefly described herein.

[0157] In step 1, before the recorded QoE configuration, the UE may be in RRC_CONNECTED state. The recorded QoE configuration may trigger QoE reporting behavior in any RRC condition / state. When the UE enters the RRC_CONNECTED state, the UE may send a QoE report to the network.

[0158] In step 2, the OAM may send the recorded QoE configuration to the CN via a non-standardized message.

[0159] In step 3, the CN may send an NG Application Protocol (AP) message 1 to the NG-RAN node within the recorded QoE configuration message. The NGAP message 1 may include at least one of the following information: QoE reference; subservice type; MCE IP address; or QoE configuration container. The QoE reference ID may be configured by OAM. In some steps, the recorded QoE may be marked with / utilized / applied using the QoE reference ID. The subservice type may be broadcast or multicast. In this implementation example, the subservice type may be broadcast. In some embodiments, when the recorded QoE generates QoE measurement data, the data may be forwarded to the MCE IP address. The QoE configuration container may contain / include the complete recorded QoE configuration. Other QoE configuration parameters included / included in step 3 of the process / call flow may be discussed in other implementation examples.

[0160] In step 4, after the NG-RAN node receives the recorded QoE configuration from the CN, the NG-RAN may send an RRC message 1 to the UE. The RRC message 1 may include at least one of the following information: an APP layer ID; a subservice type; a short IP information; or a QoE configuration container. The recorded QoE may be marked using / utilizing / applying an RRC layer ID. In this implementation example, the subservice type may be a broadcast. The NG-RAN may use / utilize / apply the short IP information to retrieve the real IP address of the MCE. The QoE configuration container may contain / include the complete recorded QoE configuration.

[0161] In step 5, the UE may receive the QoE configuration. The UE AS layer may send the received QoE configuration to the UE APP layer via an AT command. The AT command may be used to control the MT function and GSM network service / UMTS network service from the TE through the TA.

[0162] In step 6, the UE may maintain the QoE configuration in the indicated state and may start the recorded QoE measurements when the multicast and broadcast service (MBS) is initiated.

[0163] In step 7, the UE APP layer may reply to the AT command with a message (e.g., AT command 2). In step 8, the UE AS layer may reply to the RRC message with a message (e.g., RRC message 2). In step 9, the NG-RAN node may reply to the NGAP message with a message (e.g., NGAP message 2). In some embodiments, ACK information may be used to indicate that the previous message was successfully received. ACK information may be included in the message. ACK information may be empty (e.g., no relevant information) or an indicator (e.g., indicating that everything is working properly).

[0164] Table 13 shows the key points of step 3.

[0165]

[0166] Table 13

[0167] Based on the above implementation examples, the recorded QoE can be performed in three scenarios: CONNECTED state (e.g., only RRC_CONNECTED), non-CONNECTED state (e.g., RRC_INACTIVE or RRC_IDLE), and / or any RRC state (e.g., RRC_CONNECTED, RRC_IDLE and / or RRC_INACTIVE). This section only discusses other QoE parameters in the QoE configuration message. The combination of service type and state indicator (or service type and sub-service type) can be excluded.

[0168] Implementation Example 9 - Other QoE configuration parameters for QoE recorded only by CONNECTED

[0169] Fig.11 is a sequence diagram showing a process for recorded QoE according to some embodiments. The process may be performed by the UEAPP layer, UE AS, NG-RAN node, CN, and OAM. Note that the process is merely an example and is not intended to limit the present disclosure. Therefore, it should be understood that the process may be performed in Fig.11 Additional operations (e.g., blocks) are provided before, during, and after the process of the present invention, some operations may be omitted, some operations may be performed simultaneously with other operations, and some other operations may be briefly described herein. This implementation example includes the same process / steps as described in implementation example 2.

[0170] In step 3, the CN may send an NG Application Protocol (AP) message 1 to the NG-RAN node within the recorded QoE configuration message. The NGAP message 1 may include at least one of the following information: a QoE reference; a service type; a status indicator (any status indicator); an MCE IP address; or a QoE configuration container. In some embodiments, the NGAP message 1 may further include at least one of the following information: an area range associated with the QoE; NW slice information associated with the QoE; Minimization of Driving Test (MDT) calibration information associated with the QoE; or Radio Access Network Visible (RV) QoE. The area range may be an optional parameter. If the area range is configured, the value may be "empty" (e.g., indicating that the parameter is not configured with a value or is configured with an empty value), or a subset of the MBS service area (e.g., the area range of the recorded QoE may not be larger than the MBS service area). The NW slice information may be an optional parameter. The value of NW slice information may be empty (e.g., indicating that the parameter is not configured with a value or is configured with an empty value), the same as MBS NW slice information or NW slice information other than MBS. MDT calibration information may be optional. NW may only configure instant MDT. RVQoE may be optional. Parameters for RV QoE may be configured. RV QoE may be an abbreviation for RAN visible QoE. This is a sub-function.

[0171] Table 14 shows the key points of step 3.

[0172]

[0173]

[0174]

[0175] Table 14

[0176] Implementation Example 10 - Other QoE configuration parameters for QoE recorded only for non-CONNECTED

[0177] Fig.12 is a sequence diagram showing a process for recorded QoE according to some embodiments. The process may be performed by the UEAPP layer, UE AS, NG-RAN node, CN, and OAM. Note that the process is merely an example and is not intended to limit the present disclosure. Therefore, it should be understood that the process may be performed in Fig.12 Additional operations (eg, blocks) may be provided before, during, and after the processes of the present invention, some operations may be omitted, some operations may be performed simultaneously with other operations, and some other operations may be briefly described herein.

[0178] In step 3, the CN may send an NG application protocol (AP) message 1 to the NG-RAN node within the recorded QoE configuration message. The NGAP message 1 may include at least one of the following information: QoE reference; service type; status indicator (any status indicator); MCE IP address; or QoE configuration container. In some embodiments, the NGAP message 1 may further include at least one of the following information: an area range associated with QoE; NW slice information associated with QoE; MDT calibration information associated with QoE; or radio access network visible (RV) QoE. The area range may be an optional parameter. If the area range is configured, the value may be "null" (e.g., indicating that the parameter is not configured with a value or is configured with a null value), or a subset of the MBS service area (e.g., the area range of the recorded QoE may not be larger than the MBS service area). The NW slice information may be an optional parameter. The value of the NW slice information may be null (e.g., indicating that the parameter is not configured with a value or is configured with a null value), the same as the MBSNW slice information or the NW slice information other than MBS. MDT calibration information may be optional. NW may only configure the recorded MDT. RV QoE may be optional. In some embodiments, RV QoE may be performed in a non-CONNECTED state. Parameters of RV QoE may be configured.

[0179] Each QoE report may contain a timestamp. When the NW receives the logged QoE report and the logged MDT report, the NW may check the timestamp in the logged QoE report and may align the logged QoE report with the associated logged MDT report that may have the same or associated timestamp. The alignment may be done by the NG-RAN node, CN, OAM or Multimedia Broadcast Multicast Service Coordination Entity (MCE).

[0180] Table 15 shows the key points of step 3.

[0181]

[0182]

[0183] Implementation Example 11 - QoE other QoE configuration parameters recorded in any RRC state

[0184] Fig.13 is a sequence diagram showing a process for recorded QoE according to some embodiments. The process may be performed by the UEAPP layer, UE AS, NG-RAN node, CN, and OAM. Note that the process is merely an example and is not intended to limit the present disclosure. Therefore, it should be understood that the process may be performed in Fig.13 Additional operations (eg, blocks) may be provided before, during, and after the processes of the present invention, some operations may be omitted, some operations may be performed simultaneously with other operations, and some other operations may be briefly described herein.

[0185] In step 3, the CN may send an NG Application Protocol (AP) message 1 to the NG-RAN node within the recorded QoE configuration message. The NGAP message 1 may include at least one of the following information: QoE reference; service type; status indicator (any status indicator); MCE IP address; or QoE configuration container. In some embodiments, the NGAP message 1 may further include at least one of the following information: an area range associated with QoE; NW slice information associated with QoE; MDT calibration information associated with QoE; or RV QoE. The area range may be an optional parameter. If the area range is configured, the value may be "empty" (e.g., indicating that the parameter is not configured with a value or is configured with an empty value), or a subset of the MBS service area (e.g., the area range of the recorded QoE may not be larger than the MBS service area). The NW slice information may be an optional parameter. The value of the NW slice information may be empty (e.g., indicating that the parameter is not configured with a value or is configured with an empty value), the same as the MBS NW slice information or the NW slice information other than the MBS. The MDT calibration information may be optional. The logged MDT and / or immediate MDT may be configured. RVQoE may be optional. In some embodiments, RV QoE may be performed in a non-CONNECTED state. Parameters of RVQoE may be configured.

[0186] A timestamp may be included in each QoE report. When the NW receives the logged QoE report and the logged MDT report, the NW may check the timestamp in the logged QoE report and may align the logged QoE report with the related logged MDT report which may have the same or related timestamps.

[0187] Table 16 shows the key points of step 3.

[0188]

[0189]

[0190] Implementation Example 12 - QoE report recorded by CONNECTED

[0191] Fig.14 is a sequence diagram showing a process for recorded QoE according to some embodiments. The process may be performed by the UEAPP layer, UE AS, NG-RAN node, CN, and MCE. Note that the process is merely an example and is not intended to limit the present disclosure. Therefore, it should be understood that the process may be performed in Fig.14Additional operations (e.g., blocks) are provided before, during, and after the process, some operations may be omitted, some operations may be performed simultaneously with other operations, and some other operations may be briefly described herein. In this implementation example, the recorded QoE can only be executed / worked / triggered in the RRC_CONNECTED state.

[0192] Reference now Fig.14 , the process / call flow can only be used for the QoE report recorded by CONNECTED. The recorded QoE report can be the process of uploading the QoE report.

[0193] For implementation examples 13 to 15, the logged report may or may not be one of the reasons for triggering an RRC state change. Specifically, the UE may trigger an RRC state change (e.g., from RRC non-CONNECTED to CONNECTED) because the logged QoE may require reporting buffered data. In some embodiments, in any scenario, the logged QoE report may not be the only reason for triggering an RRC state change.

[0194] Implementation Example 13 - INACTIVE recorded QoE reporting (for non-CONNECTED and any RRC state recorded QoE)

[0195] Fig.15 is a sequence diagram showing a process for recorded QoE according to some embodiments. The process may be performed by the UEAPP layer, UE AS, NG-RAN node, CN, and MCE. Note that the process is merely an example and is not intended to limit the present disclosure. Therefore, it should be understood that the process may be performed in Fig.15 Additional operations (eg, blocks) may be provided before, during, and after the processes of the present invention, some operations may be omitted, some operations may be performed simultaneously with other operations, and some other operations may be briefly described herein.

[0196] In step 1, the UE may be in RRC_CONNECTED state. The UE may be configured as non-CONNECTED for the recorded QoE or any RRC state recorded QoE. The recorded QoE configuration may trigger QoE reporting behavior in any RRC condition / state. When the UE enters RRC_CONNECTED state, the UE may send a QoE report to the network.

[0197] In (conditional) step 2, if for any RRC state logged QoE, MBS originates when the UE is in RRC_CONNECTED, the logged QoE may be activated. The UE may start logging logged QoE data.

[0198] In (conditional) step 3, for any RRC state recorded QoE, the UE APP layer may upload a QoE report to the UE AS layer.

[0199] In (conditional) step 4, for any RRC state recorded QoE, the UE AS layer may send QoE report information to the NG-RAN node via an RRC message. The RRC message may include at least one of the following information: APP layer ID; QoE report container; or RV QoE measurement information. The APP layer ID may be used / utilized / applied between the UE and the NG-RAN node to mark the recorded QoE.

[0200] In (conditional) step 5, the NG-RAN node may send a QoE report to the MCE. This may not necessarily be standardized. Steps 2 to 5 may occur when the QoE recorded by any RRC state is configured to the UE.

[0201] In step 6, the NG-RAN may send an RRC release message (second message) to the UE.

[0202] In step 7, when the UE receives the RRC release message with the pause indicator, the UE may switch to the RRC_INACTIVE state. For any state recorded QoE, the UE may keep measuring and may keep the newly generated QoE data in the buffer on the UE side. For non-CONNECTED recorded QoE, the recorded QoE may not be activated when the UE is in the RRC_CONNECTED state. After the UE switches to the RRC_INACTIVE state, if MBS starts, the UE may perform the recorded QoE and may record the QoE data in the buffer on the UE side.

[0203] In step 8, when the UE remains / continues to be in the RRC_INACTIVE state, the UE may send an RRC resume request message to switch the UE to the RRC_CONNECTED state. Before the UE sends the RRC resume request message, the UE may have recorded some QoE reports in the local buffer. The recorded QoE buffer may not be empty, which may not be the reason (or the only reason) for the UE to switch to the RRC_CONNECTED state.

[0204] In step 9, when the NG-RAN node receives the RRC recovery request message, the NG-RAN may reply with an RRC recovery message (fifth message).

[0205] In step 10, when the UE receives the RRC recovery message, the UE may reply with an RRC recovery complete message (sixth message), and the RRC recovery process may be completed. In some embodiments, the RRC recovery message may cause the UE to switch back to the RRC_CONNECTED state. Information about the recorded QoE buffer data (e.g., QoE buffer information) may be added to the RRC recovery complete message. The QoE buffer information may indicate the properties of the QoE buffer. In some embodiments, the QoE buffer information may not include any measured data. After configuration, the QoE buffer information may be a constant value. For example, specific buffer information may include at least one of the following: buffer size, buffer period, QoE reference ID, or how to handle buffer overflow. The buffer size may indicate the location where the buffer can be accommodated. The RRC recovery complete message may include at least one of the following information: a 1-bit indicator; or detailed information about the recorded QoE and / or QoE buffer. The 1-bit indicator may show that the recorded QoE buffer may not be empty. For each recorded QoE involved, the 1-bit indicator may show that the recorded QoE buffer may not be empty. Detailed information about the recorded QoE may include QoE session information, the number of QoE reports, the size of the QoE report, or other data related to QoE parameters. Detailed information about the QoE buffer may include the buffer size, whether the buffer is full, or the UE buffer setting (e.g., an AS layer buffer or an APP layer buffer). In some embodiments, the RRC recovery completion message (sixth message) may not contain any QoE buffer data. The RRC recovery completion message may include information or a status description about the recorded QoE. In some embodiments, the QoE buffer data may be buffered data. The UE may store the data in the QoE buffer. The data in the QoE buffer may be generated by QoE measurement. All data may be monitoring / recording of configured QoE parameters (e.g., information about playlists, buffer levels, and / or video delays). In some embodiments, the UE may store QoE buffer data when it is not in the RRC_CONNECTED state.

[0206] In step 11, the UE may enter the RRC_CONNECTED state. For non-CONNECTED recorded QoE, the UE may stop the ongoing recorded QoE measurement. In some embodiments, the UE may not activate a new recorded QoE, but may continue the ongoing recorded QoE. For any state recorded QoE, the UE may keep measuring and reporting (e.g., steps 2 to 5).

[0207] In step 12 (alternative solution), after the NG-RAN node receives the recorded QoE buffer information from the UE, the NG-RAN node may send an RRC message with the recorded QoE reporting requirement information to the UE. The RRC message may include at least one of the following information: APP layer ID; QoE reference; or recorded QoE buffer information. The APP ID may be used / utilized / applied between the UE and the NG-RAN node to mark the recorded QoE.

[0208] In step 13 (alternative solution), the UE may reply to the RRC message 2 from the NG-RAN node with a message (e.g., RRC message 3). In some embodiments, the ACK information may be included in the reply message. If everything is OK, the reply message may not have any recorded QoE information. Steps 12 and 13 may be another alternative solution for the recorded QoE data reporting. At step 10, when the NG-RAN node receives the relevant information from the UE side, the NG-RAN node may request the UE to upload the buffered data. In some embodiments, the UE may directly send the buffered recorded QoE data without the NG-RAN node's requirement. In an alternative solution, steps 12 and 13 may not be required.

[0209] In step 14, an AT command may be sent between the UE AS layer and the UE APP layer for QoE reporting.

[0210] In step 15, the UE may send the QoE buffered data to the NG-RAN node via RRC message 2.

[0211] In step 16, the NG-RAN node may forward the received recorded QoE data to the MCE.

[0212] Implementation Example 14 - IDLE recorded QoE report without QoE configuration retrieval (for non-CONNECTED recorded QoE)

[0213] Fig.16 and Fig.17 A sequence diagram of a process for recorded QoE according to some embodiments is shown. The process may be performed by the UE APP layer, UE AS, NG-RAN node, CN, and MCE. Note that the process is merely an example and is not intended to limit the present disclosure. Therefore, it should be understood that the process may be performed in Fig.16 and Fig.17 Additional operations (eg, blocks) may be provided before, during, and after the processes of the present invention, some operations may be omitted, some operations may be performed simultaneously with other operations, and some other operations may be briefly described herein.

[0214] In step 1, the UE may be in RRC_CONNECTED state. For the recorded QoE, the UE may be configured as non-CONNECTED. The recorded QoE configuration may trigger QoE reporting behavior in any RRC condition / state. When the UE enters the RRC_CONNECTED state, the UE may send a QoE report to the network.

[0215] In (conditional) step 2, if for any RRC state logged QoE, MBS originates when the UE is in RRC_CONNECTED, the logged QoE may be activated. The UE may start logging logged QoE data.

[0216] In (conditional) step 3, for any RRC state recorded QoE, the UE APP layer may upload a QoE report to the UE AS layer.

[0217] In (conditional) step 4, for any RRC state recorded QoE, the UE AS layer may send QoE report information to the NG-RAN node via an RRC message. The RRC message may include at least one of the following information: APP layer ID; QoE report container; or RV QoE measurement information. The APP layer ID may be used / utilized / applied between the UE and the NG-RAN node to mark the recorded QoE.

[0218] In (conditional) step 5, the NG-RAN node may send a QoE report to the MCE. This may not necessarily be standardized. Steps 2 to 5 may occur when the QoE recorded by any RRC state is configured to the UE.

[0219] In steps 6, 7 and 8, the system may perform an RRC release procedure. The UE may switch to the RRC_IDLE state.

[0220] In step 9, the UE may keep the short IP information and configuration at the UE side before the UE releases all UE contexts and switches to the RRC IDLE state. When the UE enters the RRC_IDLE state, if MBS starts, the UE may perform the recorded QoE measurements.

[0221] In step 10, the UE may decide to switch to the RRC_CONNECTED state and may perform an initial access procedure. The recorded QoE buffer may not be empty, which may not be the reason (or the only reason) that the UE may switch to the RRC_CONNECTED state.

[0222] In step 11, the UE may send an RRC setup request message to the NG-RAN node.

[0223] In step 12, the NG-RAN node may send an RRC setup message to the UE.

[0224] In step 13, the UE may send an RRC setup complete message to the NG-RAN node. Information about the recorded QoE buffer data (e.g., QoE buffer information) may be added to the RRC setup complete message. The QoE buffer information may indicate the properties of the QoE buffer. In some embodiments, the QoE buffer information may not include any measured data. After configuration, the QoE buffer information may be a constant value. For example, specific buffer information may include at least one of the following: buffer size, buffer period, QoE reference ID, or how to handle buffer overflow. The buffer size may indicate the location where the buffer can be accommodated. The RRC recovery complete message may include at least one of the following information: a 1-bit indicator indicating that the UE's buffer may not be empty; QoE session information; the number of QoE reports; the QoE report size for one QoE session; data about other QoE parameter related data; the size of the buffer; the QoE reference ID for the recorded QoE; or detailed information about the recorded QoE and / or QoE buffer. For each recorded QoE session involved, detailed information about the recorded QoE may include QoE session information, the number of QoE reports, the size of the QoE report, or other QoE parameter-related data. Detailed information about the QoE buffer may include the buffer size, whether the buffer is full, or the UE buffer setting (e.g., an AS layer buffer or an APP layer buffer). The RRC recovery complete message may include information or a status description about the recorded QoE. In some embodiments, the RRC recovery message may cause the UE to switch back to the RRC_CONNECTED state. In some embodiments, the QoE buffered data may be buffered data. The UE may store the data in the QoE buffer. The data in the QoE buffer may be generated by QoE measurements. All data may be monitoring / recording of configured QoE parameters (e.g., information about playlists, buffer levels, and / or video delays). In some embodiments, the UE may store the QoE buffered data when it is not in the RRC_CONNECTED state.

[0225] In step 14, the NG-RAN node may send an NGAP Initial UE message to the CN.

[0226] In step 15, the UE may enter the RRC_CONNECTED state. The UE may select at least one of the following alternatives. The UE may stop all ongoing recorded QoE in the RRC_CONNECTED state and may not activate new non-CONNECTED recorded QoE. Alternatively, if the recorded QoE measurement is an ongoing QoE measurement and the UE may not activate new non-CONNECTED recorded QoE in the RRC_CONNECTED state, the UE may continue to perform the recorded QoE measurement.

[0227] In step 16 (alternative solution), after the NG-RAN node receives the recorded QoE buffer information from the UE, the NG-RAN node may send an RRC message with the recorded QoE reporting requirement information to the UE. The RRC message may include at least one of the following information: APP layer ID; QoE reference; or recorded QoE buffer information. The APP ID may be used / utilized / applied between the UE and the NG-RAN node to mark the recorded QoE.

[0228] In step 17 (alternative), the UE may reply to the RRC message 2 from the NG-RAN node with a message (e.g., RRC message 3). In some embodiments, the ACK information may be included in the reply message. If everything is OK, the reply message may not have any recorded QoE information. Steps 16 and 17 may be another alternative for the recorded QoE data report. At step 10, when the NG-RAN node receives relevant information from the UE side, the NG-RAN node may ask the UE to upload the buffered data. In some embodiments, the UE may directly send the buffered recorded QoE data without the NG-RAN node's requirement. In an alternative, steps 16 and 17 may not be required. In some embodiments, after the UE switches to the CONNECTED state, the UE may directly upload the QoE buffer report. Alternatively, the UE may wait for network requirements. This may be the reason why the network may provide the UE with QoE session information.

[0229] In step 18, an AT command may be sent between the UE AS layer and the UE APP layer for QoE reporting.

[0230] In step 19, the UE may send the QoE buffered data to the NG-RAN node via RRC message 2.

[0231] In step 20, the NG-RAN node may forward the received recorded QoE data to the MCE.

[0232] Implementation Example 15 - IDLE recorded QoE reporting without QoE configuration retrieval (for any RRC state and non-CONNECTED recorded QoE)

[0233] Fig.18 is a sequence diagram showing a process for recorded QoE according to some embodiments. The process may be performed by the UE APP layer, UE AS, NG-RAN node, CN, OAM, and MCE. Note that the process is merely an example and is not intended to limit the present disclosure. Therefore, it should be understood that the process may be performed in Fig.18 Additional operations (eg, blocks) may be provided before, during, and after the processes of the present invention, some operations may be omitted, some operations may be performed simultaneously with other operations, and some other operations may be briefly described herein.

[0234] In step 1, the UE may be in RRC_CONNECTED state. The UE may be configured as non-CONNECTED for the recorded QoE or any RRC state recorded QoE. The recorded QoE configuration may trigger QoE reporting behavior in any RRC condition / state. When the UE enters RRC_CONNECTED state, the UE may send a QoE report to the network.

[0235] In (conditional) step 2, if for any RRC state logged QoE, MBS originates when the UE is in RRC_CONNECTED, the logged QoE may be activated. The UE may start logging logged QoE data.

[0236] In (conditional) step 3, for any RRC state recorded QoE, the UE APP layer may upload a QoE report to the UE AS layer.

[0237] In (conditional) step 4, for any RRC state recorded QoE, the UE AS layer may send QoE report information to the NG-RAN node via an RRC message. The RRC message may include at least one of the following information: APP layer ID; QoE report container; or RV QoE measurement information. The APP layer ID may be used / utilized / applied between the UE and the NG-RAN node to mark the recorded QoE.

[0238] In (conditional) step 5, the NG-RAN node may send a QoE report to the MCE. Steps 2 to 5 may occur when the QoE recorded by any RRC state is configured to the UE.

[0239] In steps 6, 7 and 8, the system may perform an RRC release procedure. The UE may switch to the RRC_IDLE state.

[0240] In step 9, the UE may maintain the short IP information and configuration on the UE side before the UE releases all UE contexts and switches to the RRC IDLE state. When the UE enters the RRC_IDLE state, the UE may continue the ongoing recorded QoE and may activate a new recorded QoE for any RRC state recorded QoE. In some embodiments, when the UE enters the RRC_IDLE state, if MBS is started for a non-CONNECTED recorded QoE, the UE may activate the recorded QoE measurement. The newly generated recorded QoE data may be maintained in a buffer on the UE side. The recorded QoE buffer may not be empty, which may not be the reason (or the only reason) that the UE may switch to the RRC_CONNECTED state.

[0241] In step 10, the UE may decide / determine to switch to the RRC_CONNECTED state and may perform an initial access procedure.

[0242] In step 11, the UE may send an RRC setup request message to the NG-RAN node.

[0243] In step 12, the NG-RAN node may send an RRC setup message to the UE.

[0244] In step 13, the UE may send an RRC setup complete message to the NG-RAN node. Information about the recorded QoE buffer data (e.g., QoE buffer information) may be added to the RRC setup complete message. The QoE buffer information may indicate the properties of the QoE buffer. In some embodiments, the QoE buffer information may not include any measured data. After configuration, the QoE buffer information may be a constant value. For example, specific buffer information may include at least one of the following: buffer size, buffer period, QoE reference ID, or how to handle buffer overflow. The buffer size may indicate the location where the buffer can be accommodated. The RRC recovery complete message may include at least one of the following information: a 1-bit indicator; a QoE reference ID for the recorded QoE; or detailed information about the recorded QoE and / or QoE buffer. For each recorded QoE session involved, the detailed information about the recorded QoE may include QoE session information, the number of QoE reports, the QoE report size, or other QoE parameter-related data. Detailed information about the QoE buffer may include the buffer size, whether the buffer is full, or the UE buffer settings (e.g., AS layer buffer or APP layer buffer). The RRC recovery complete message may include information or status description about the recorded QoE. In some embodiments, the QoE buffer data may be buffered data. The UE may store the data in the QoE buffer. The data in the QoE buffer may be generated by QoE measurements. All data may be monitoring / recording of configured QoE parameters (e.g., information about playlists, buffer levels, and / or video delays). In some embodiments, the UE may store the QoE buffer data when it is not in the RRC_CONNECTED state.

[0245] In step 14, the NG-RAN node may send an NGAP message (e.g., an initial UE message) to the CN using the received recorded QoE information. The NGAP message may include at least one of the following information: a QoE reference; MCE information; a 1-bit indicator; or detailed information about the recorded QoE and / or QoE buffer. The NG-RAN node may obtain the IP address by receiving a short IP message. The 1-bit indicator may show that the recorded QoE may not be empty. For each recorded QoE session involved, the detailed information about the recorded QoE may include QoE session information, the number of QoE reports, the QoE report size, or other QoE parameter-related data. Detailed information about the QoE buffer may include the buffer size, whether the buffer is full, or the UE buffer settings (e.g., an AS layer buffer or an APP layer buffer).

[0246] In step 15, the UE may enter the RRC_CONNECTED state. The UE may remain operational and may be activated for any RRC state recorded QoE. The UE may select at least one of the following alternatives for non-CONNECTED recorded QoE. The UE may stop all ongoing recorded QoE in the RRC_CONNECTED state and may not activate new non-CONNECTED recorded QoE. Alternatively, if the recorded QoE measurement is an ongoing QoE measurement and the UE may not activate new non-CONNECTED recorded QoE in the RRC_CONNECTED state, the UE may continue to perform the recorded QoE measurement.

[0247] The CN may exchange the received recorded QoE information with the OAM in step 16. The OAM may send the retrieved recorded QoE configuration to the CN.

[0248] In step 17, the CN may send an NGAP message (e.g., UE context modification request) to the NG-RAN node using the retrieved recorded QoE configuration. The information contained in the NGAP message may depend on the selected system and other QoE parameter configurations described in the previous implementation examples.

[0249] In step 18, the NG-RAN node may send an RRC message (eg, RRC reconfiguration) to the UE AS layer. The RRC message may include at least one of the following information: an APP layer ID; a retrieved recorded QoE configuration; or a QoE reference ID.

[0250] In step 19, the UE AS layer may exchange messages with the UE APP layer based on the received recorded QoE configuration.

[0251] In step 20, the UE may reply an RRC message (e.g., RRC reconfiguration) to the NG-RAN node.

[0252] In step 21, the NG-RAN node may send an NGAP message (e.g., NGAP Initial Context Setup Response) to the CN.

[0253] In step 22 (alternative solution), after the NG-RAN node receives the recorded QoE buffer information, the NG-RAN node may send an RRC message using the recorded QoE reporting requirement information. The RRC message may include at least one of the following information: APP layer ID; QoE reference; or recorded QoE buffer information. The APP ID may be used / utilized / applied between the UE and the NG-RAN node to mark the recorded QoE.

[0254] In step 23 (alternative solution), the UE may reply to the RRC message 2 from the NG-RAN node with a message (e.g., RRC message 3). In some embodiments, the ACK information may be included in the reply message. If everything is OK, the reply message may not have any recorded QoE information. Steps 22 and 23 may be another alternative solution for the recorded QoE data reporting. At step 10, when the NG-RAN node receives relevant information from the UE side, the NG-RAN node may require the UE to upload the buffered data. In some embodiments, the UE may directly send the buffered recorded QoE data without the NG-RAN node's requirement. Steps 22 and 23 may be another way for the recorded QoE data reporting. At step 10, when the UE receives relevant information from the UE side, the NG-RAN node may require the UE to upload the buffered data. The UE may also directly send the buffered recorded QoE data without the need for the NG-RAN node. In an alternative solution, steps 22 and 23 may not be required. In some embodiments, after the UE switches to the CONNECTED state, the UE may directly upload the QoE buffer report. Alternatively, the UE may wait for network demand. This may be the reason why the network may provide the UE with QoE session information.

[0255] Step 24, step 25 and / or step 26 may be (one or more) QoE reporting procedures.

[0256] Table 17 shows the key points of step 14, with one indicator for all recorded QoE sessions.

[0257]

[0258]

[0259] Table 17 and Table 18 show the key points when each recorded QoE has indicators and information.

[0260]

[0261]

[0262] Table 18

[0263] Fig.19 A flow chart of a method 1900 for recording QoE measurements is shown. The method 1900 may be used in conjunction with the present invention. Figure 1 to Figure 2In some embodiments, the method 1900 may be implemented by a wireless communication device (e.g., a UE) and / or a wireless communication node (e.g., a BS / RAN node). Depending on the embodiment, additional, fewer, or different operations may be performed in the method 1900. At least one aspect of the operation relates to a system, method, apparatus, or computer-readable medium.

[0264] The wireless communication device (eg, UE) may store the measurement of QoE as QoE buffered data. The wireless communication device may send a first message to a wireless communication node (eg, BS), the first message including the QoE buffered data.

[0265] In some embodiments, when the wireless communication device is not in the RRC_CONNECTED state, the wireless communication device may store the QoE buffered data. The wireless communication device may send the first message before the wireless communication device switches back to the RRC_CONNECTED state.

[0266] In some embodiments, the wireless communication device may receive a second message (e.g., an RRC release message) from the wireless communication node, causing the wireless communication device to switch from the RRC_CONNECTED state to the RRC_INACTIVE state or the RRC_IDLE state. Before receiving the second message, the wireless communication device may receive a third message indicating that the wireless communication device can trigger the measurement of QoE in any one of the RRC_CONNECTED state, the RRC_INACTIVE state, or the RRC_IDLE state. After switching to the RRC_INACTIVE state or the RRC_IDLE state, the wireless communication device may continue to store the measurement of QoE as the QoE buffered data. In some embodiments, before receiving the second message, the wireless communication device may receive a fourth message indicating that the wireless communication device can only trigger the measurement of QoE in the RRC_INACTIVE state or the RRC_IDLE state. After switching to the RRC_INACTIVE state or the RRC_IDLE state, the wireless communication device may store the measurement of QoE as the QoE buffered data.

[0267] In some embodiments, the wireless communication device may receive a fifth message (e.g., an RRC recovery message, an RRC setup message) from the wireless communication node, causing the wireless communication device to switch back to the RRC_CONNECTED state. In response to receiving the fifth message, the wireless communication device may send a sixth message (e.g., an RRC recovery complete message, an RRC setup complete message) to the wireless communication node, the sixth message including QoE buffer information. The QoE buffer information of the sixth message may include at least one of the following: a 1-bit indicator indicating that the buffer of the wireless communication device may not be empty; QoE session information; the number of QoE reports; the QoE report size for one QoE session; data about other QoE parameter related data; or the size of the buffer.

[0268] In some embodiments, after sending the sixth message, the wireless communication device may switch itself to the RRC_CONNECTED state. The wireless communication device may receive a seventh message (e.g., RRC message 2, RRC reconfiguration message) from the wireless communication node, the seventh message including QoE requirement information. The QoE requirement information may include at least one of the following: APP layer ID; QoE buffer information; or QoE reference ID. In response to receiving the seventh message, the wireless communication device may send an eighth message (e.g., RRC message 3) to the wireless communication node, the eighth message including confirmation information.

[0269] In some embodiments, a wireless communication node (eg, a BS) may receive a first message from a wireless communication device (eg, a UE), the first message including QoE buffered data. The QoE buffered data may be stored by the wireless communication device.

[0270] Although various embodiments of the present technical solution have been described above, it should be understood that they are presented only as examples rather than as limitations. Similarly, various figures may depict exemplary architectures or configurations, which are provided to enable those of ordinary skill in the art to understand the exemplary features and functions of the present technical solution. However, these technicians will understand that the present solution is not limited to the example architectures or configurations shown, but can be implemented using various alternative architectures and configurations. In addition, as will be appreciated by those of ordinary skill in the art, one or more features of an embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above-mentioned illustrative embodiments.

[0271] It should also be understood that any reference to an element using designations such as "first", "second", etc. herein does not generally limit the number or order of these elements. Rather, these designations may be used herein as a convenient means of distinguishing between two or more elements or multiple instances of an element. Therefore, reference to a first and a second element does not mean that only two elements may be used or that the first element must precede the second element in some manner.

[0272] In addition, those skilled in the art will appreciate that any of a variety of different technical means may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced in the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0273] Those of ordinary skill in the art will further understand that any of the various illustrative logic blocks, modules, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of programs or design codes incorporating instructions (for convenience, referred to herein as "software" or "software modules"), or any combination of these technologies. In order to clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functions. Whether such functionality is implemented as hardware, firmware, or software, or as a combination of these technologies, depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each specific application, but such implementation decisions will not result in a departure from the scope of the present disclosure.

[0274] In addition, it will be understood by those of ordinary skill in the art that the various illustrative logic blocks, units, devices, components, and circuits described herein may be implemented or performed within an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, or any combination thereof. The logic blocks, modules, and circuits may also include antennas and / or transceivers to communicate with various components within a network or within a device. The general-purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other suitable configuration to perform the functions described herein.

[0275] If implemented in software, these functions can be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, which include any media that can transfer a computer program or code from one place to another. The storage medium can be any available medium that can be accessed by a computer. As an example and not a limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage device, magnetic disk storage device or other magnetic storage device, or any other medium that can be used to store the required program code in the form of instructions or data structures and can be accessed by a computer.

[0276] In this document, the term "module" used herein refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. In addition, for the purpose of discussion, various modules are described as discrete modules; however, as is apparent to those of ordinary skill in the art, according to an embodiment of the present technical solution, two or more modules can be combined to form a single module that performs the associated functions.

[0277] In addition, memory or other storage devices and communication components can be used in the embodiments of the present technical solution. It should be understood that, for the sake of clarity, the above description describes the embodiments of the present technical solution with reference to different functional units and processors. However, it is obvious that, without departing from the present technical solution, any appropriate functional distribution can be applied between different functional units, processing logic elements or domains. For example, the function shown as being performed by a separate processing logic element or controller can be performed by the same processing logic element or controller. Therefore, a reference to a specific functional unit is merely a reference to an appropriate means for providing the function, rather than representing a strict logical or physical structure or organization.

[0278] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the embodiments shown herein, but is to be accorded the broadest scope consistent with the novel features and principles disclosed herein as described in the following claims.

Claims

1. A wireless communication method, include: storing, by the wireless communication device, a measurement of the quality of experience (QoE) as QoE buffer data; as well as A first message is sent by the wireless communication device to a wireless communication node, where the first message includes the QoE buffer data.

2. The wireless communication method according to claim 1, further comprising: include: When the wireless communication device is not in the RRC_CONNECTED state, storing the QoE buffer data; as well as The first message is sent before the wireless communication device switches back to the RRC_CONNECTED state.

3. The wireless communication method according to claim 1, further comprising: include: The wireless communication device receives a second message from the wireless communication node, so that the wireless communication device switches from the RRC_CONNECTED state to the RRC_INACTIVE state or the RRC_IDLE state.

4. The wireless communication method according to claim 3, further comprising: include: Before receiving the second message, receiving, by the wireless communication device, a third message indicating that the wireless communication device can trigger QoE measurement in any one of the RRC_CONNECTED state, the RRC_INACTIVE state, or the RRC_IDLE state; as well as After switching to the RRC_INACTIVE state or the RRC_IDLE state, the wireless communication device continues to store the measurement of QoE as the QoE buffered data.

5. The wireless communication method according to claim 3, further comprising: include: Before receiving the second message, the wireless communication device receives a fourth message, wherein the fourth message indicates that the wireless communication device can only trigger QoE measurement in the RRC_INACTIVE state or the RRC_IDLE state; as well as After switching to the RRC_INACTIVE state or the RRC_IDLE state, the wireless communication device stores the measurement of QoE as the QoE buffered data.

6. The wireless communication method according to claim 3, further comprising: include: Receiving, by the wireless communication device, a fifth message from the wireless communication node, so that the wireless communication device switches back to the RRC_CONNECTED state; as well as In response to receiving the fifth message, a sixth message is sent by the wireless communication device to the wireless communication node, the sixth message including QoE buffer information.

7. The wireless communication method according to claim 6, in, The QoE buffer information of the sixth message includes at least one of the following: a 1-bit indicator indicating that the buffer of the wireless communication device is not empty; QoE session information; number of QoE reports; QoE report size for one QoE session; data on other QoE parameter related data; or the size of the buffer.

8. The wireless communication method according to claim 6, further comprising: include: After sending the sixth message, the wireless communication device switches itself to the RRC_CONNECTED state; as well as A seventh message is received by the wireless communication device from the wireless communication node, the seventh message including QoE requirement information.

9. The wireless communication method according to claim 8, in, The QoE requirement information includes at least one of the following: an application APP layer identifier ID; QoE buffer information; or a QoE reference ID.

10. The wireless communication method according to claim 9, further comprising: include: In response to receiving the seventh message, an eighth message is sent by the wireless communication device to the wireless communication node, wherein the eighth message includes confirmation information.

11. A wireless communication method, include: Receiving, by a wireless communication node, a first message from a wireless communication device, the first message comprising quality of experience (QoE) buffer data; The QoE buffer data is stored by the wireless communication device.

12. A wireless communication device comprising a processor and a memory, in, The processor is configured to read code from the memory and implement the method according to any one of claims 1 to 11.

13. A computer program product comprising computer readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the method according to any one of claims 1 to 11.

Images