WO2023133812A1 - Procédé et appareil de continuité de rapports de qualité d'expérience - Google Patents

Procédé et appareil de continuité de rapports de qualité d'expérience Download PDF

Info

Publication number
WO2023133812A1
WO2023133812A1 PCT/CN2022/072068 CN2022072068W WO2023133812A1 WO 2023133812 A1 WO2023133812 A1 WO 2023133812A1 CN 2022072068 W CN2022072068 W CN 2022072068W WO 2023133812 A1 WO2023133812 A1 WO 2023133812A1
Authority
WO
WIPO (PCT)
Prior art keywords
qoe
network device
terminal device
buffer
message
Prior art date
Application number
PCT/CN2022/072068
Other languages
English (en)
Inventor
Jing He
Ping Yuan
Malgorzata Tomala
Original Assignee
Nokia Shanghai Bell Co., Ltd.
Nokia Solutions And Networks Oy
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Shanghai Bell Co., Ltd., Nokia Solutions And Networks Oy, Nokia Technologies Oy filed Critical Nokia Shanghai Bell Co., Ltd.
Priority to PCT/CN2022/072068 priority Critical patent/WO2023133812A1/fr
Publication of WO2023133812A1 publication Critical patent/WO2023133812A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5061—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the interaction between service providers and their network customers, e.g. customer relationship management
    • H04L41/5067—Customer-centric QoS measurements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H04L43/065—Generation of reports related to network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point

Definitions

  • Various example embodiments described herein generally relate to communication technologies, and more particularly, to methods and apparatuses supporting quality of experience (QoE) reporting continuity.
  • QoE quality of experience
  • 5G New Radio the latest evolution of the cellular communication network, is designed to deliver diverse services and use cases to end users with greater speed, lower latency and massive connectivity.
  • the network operators may quantify end users’ satisfaction on the services by collecting quality of experience (QoE) measurements from end user devices.
  • QoE quality of experience
  • the terminal device may comprise at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code may be configured to, with the at least one processor, cause the terminal device at least to perform Quality of Experience, QoE, measurement on a service received via a source network device and, upon detection of an indication indicative of a mobility procedure for handing over the terminal device from the source network device to a target network device for the service, transmit, during or after the mobility procedure, to the target network device a buffer status report associated with a buffer for storing one or more QoE measurement reports.
  • QoE Quality of Experience
  • the network device may comprise at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code may be configured to, with the at least one processor, cause the network device at least to receive from a terminal device a buffer status report associated with a buffer for storing one or more Quality of Experience, QoE, measurement reports, during or after a mobility procedure by which the terminal device hands over from a source network device to the network device, and transmit a QoE reporting request message or QoE reporting resume command to the terminal device.
  • the network device may operate as a target network device for the terminal device.
  • the QoE reporting request message or QoE reporting resume command may be determined at least partially based on the received buffer status report.
  • Example embodiments of methods, apparatus and computer program products are also provided. Such example embodiments generally correspond to the above example embodiments of the terminal and the network device, and a repetitive description thereof is omitted here for convenience.
  • Fig. 1 is a schematic diagram illustrating a cellular communication network in which example embodiments of the present disclosure can be implemented.
  • Fig. 2 is a schematic message flow diagram illustrating operations for quality of experience (QoE) measurement reporting in accordance with some example embodiments.
  • QoE quality of experience
  • Fig. 3 is a schematic message flow diagram illustrating operations for QoE measurement reporting in accordance with some example embodiments.
  • Fig. 4 is a schematic message flow diagram illustrating operations for QoE measurement reporting in accordance with some example embodiments.
  • Fig. 5 is a schematic message flow diagram illustrating operations for QoE measurement reporting in accordance with some example embodiments.
  • Fig. 6 is a schematic message flow diagram illustrating operations for QoE measurement reporting in accordance with some example embodiments.
  • Fig. 7 is a schematic message flow diagram illustrating operations for QoE measurement reporting in accordance with some example embodiments.
  • Fig. 8 is a schematic structure block diagram illustrating devices in a communication system in which example embodiments of the present disclosure can be implemented.
  • the term “network device” refers to any suitable entities or devices that can provide cells or coverage, through which the terminal device can access the network or receive services.
  • the network device may be commonly referred to as a base station.
  • the term “base station” used herein can represent a node B (NodeB or NB) , an evolved node B (eNodeB or eNB) , or a gNB or an ng-eNB.
  • the base station may be embodied as a macro base station, a relay node, or a low power node such as a pico base station or a femto base station.
  • the base station may consist of several distributed network units, such as a central unit (CU) , one or more distributed units (DUs) , one or more remote radio heads (RRHs) or remote radio units (RRUs) .
  • CU central unit
  • DUs distributed units
  • RRHs remote radio heads
  • RRUs remote radio units
  • terminal device or “user equipment” (UE) refers to any entities or devices that can wirelessly communicate with the network devices or with each other.
  • the terminal device can include a mobile phone, a mobile terminal, a mobile station, a subscriber station, a portable subscriber station, an access terminal, a computer, a wearable device, an on-vehicle communication device, a machine type communication (MTC) device, a D2D communication device, a V2X communication device, a sensor and the like.
  • MTC machine type communication
  • D2D communication device a D2D communication device
  • V2X communication device a sensor and the like.
  • the term “terminal device” can be used interchangeably with UE, a user terminal, a mobile terminal, a mobile station, or a wireless device.
  • Fig. 1 illustrates a schematic diagram of a cellular communication network 100 in which example embodiments of the present disclosure can be implemented.
  • the cellular communication network 100 may be implemented as a multiple access system capable of supporting communication with multiple users sharing available system resources.
  • the cellular communication network 100 may employ one or more channel access schemes such as Time Division Multiple Access (TDMA) , Code Division Multiple Access (CDMA) , Time Division Synchronous Code Division Multiple Access (TD-SCDMA) , Frequency Division Multiple Access (FDMA) , Orthogonal Frequency Division Multiple Access (OFDMA) , Single Carrier Frequency Division Multiple Access (SC-FDMA) and the like.
  • TDMA Time Division Multiple Access
  • CDMA Code Division Multiple Access
  • TD-SCDMA Time Division Synchronous Code Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • Fig. 1 shows the cellular communication network 100 as a 5G NR network including a plurality of 5G base stations “gNB” , but it would be appreciated that example embodiments disclosed herein can also be implemented in a 4G LTE network or a beyond 5G network.
  • the cellular communication network 100 may include a plurality of base stations (BSs) and a plurality of user equipments (UEs) in wireless communication with the base stations.
  • the plurality of base stations may form a so-called random access network (RAN) and provide network access to the plurality of UEs.
  • the base stations may also connect to a core network (not shown) such as a 5G core network (5GC) via backhaul connections.
  • a core network such as a 5G core network (5GC) via backhaul connections.
  • Each of the base stations may provide service coverage for one or more cells, including for example macro cells and small cells such as femto cells, pico cells and micro cells.
  • a UE may camp in a cell and connect with a base station serving the cell to transmit and receive data on uplink and downlink channels.
  • Fig. 1 depicts two 5G base stations 122, 124 (also referred to as “gNB” ) and one UE 110 as an example, and it would be appreciated that the cellular
  • the UE 110 may initially connect to the first base station 122 and receive a service for example a streaming video service through the first base station 122.
  • the UE 110 may also be configured to perform Quality of Experience (QoE) measurements on the service and transmit QoE measurement reports to the network.
  • QoE Quality of Experience
  • QoE measurement is performed at the application layer and it aims to quantify how much the end users are satisfied with a service provided by a network operator or a service provider.
  • the network operator or the service provider may configure QoE measurements based on services, applications and/or use cases provided to the end users.
  • the base station 122 may temporarily pause QoE reporting from the UE 110. Then the UE 110 may store the QoE measurement reports in a local memory. The UE 110 would not transmit the QoE measurement reports until the base station 122 resumes the QoE reporting from the UE 110.
  • the UE 110 may move for example from the serving cell supported by the first base station 122 to a neighbor cell supported by the second base station 124.
  • the UE 110 may transition from the first base station 122 to the second base station 124 to continue to receive the service for example the streaming video service through the second base station 124.
  • the first base station 122 may be referred to as a source base station
  • the second base station 124 may be referred to as a target base station.
  • QMC QoE measurement collection
  • the UE when a UE detects an indication of a UE mobility procedure, the UE may inform the target base station of how much QoE measurement data is stored at the UE during or after the mobility procedure. Then the target base station can determine when to resume the QoE reporting from the UE at least partially based on the data volume stored at the UE and/or load at the target base station.
  • QoE measurement collection and reporting continuity can be ensured after the UE mobility procedure while signaling overhead is not significantly increased.
  • Fig. 2 is a schematic message flow diagram illustrating operations for QoE measurement reporting in accordance with some example embodiments.
  • the operations can be performed by a UE, a source base station and a target base station such as the UE 110, the source base station 122 and the target base station 124 described above with reference to Fig. 1.
  • the UE 110, the source base station 122 and the target base station 124 each may include a plurality of means, modules or elements implemented to perform operations discussed below with respect to Fig. 2.
  • the means, modules and elements may be implemented in various manners including but not limited to for example software, hardware, firmware or any combination thereof to perform the operations.
  • the UE 110 is connected to the source base station 122 and receives a service through the source base station 122.
  • the service may include but not be limited to a streaming video service, an interactive multimedia service like videoconference, a Voice on Internet Protocol (VoIP) service, an Internet Protocol Television (IPTV) service, a Multicast Broadcast service (MBS) , a Multimedia Telephony Service for IMS (MTSI) , a Virtual Reality (VR) service and the like.
  • VoIP Voice on Internet Protocol
  • IPTV Internet Protocol Television
  • MBS Multicast Broadcast service
  • MMSI Multimedia Telephony Service for IMS
  • VR Virtual Reality
  • the UE 110 may perform QoE measurements on the service received through the source base station 122 and generate a QoE measurement report.
  • the QoE measurement may be performed in UE application layer based on QoE configuration received from the network.
  • the core network or Operation and Maintenance (Q&M) may determine QoE configuration for a service or application received at the UE 110 and transmit the QoE configuration via the base station 122 to the UE 110.
  • the QoE configuration may provision QoE metrics and QoE reporting parameters for the UE 110.
  • the UE 110 may receive a QoE reporting Pause command from the source base station 122.
  • the QoE reporting Pause command indicates the UE 110 to pause transmission of the QoE measurement report to the base station 122.
  • the base station 122 may pause the QoE reporting from the UE 110 to reduce consumption of radio resources.
  • the UE 110 When the QoE reporting is paused by the network, the UE 110 would not send the QoE measurement report to the network unless a QoE reporting Resume command is received. However, the UE 110 may continue to receive the service and perform QoE measurements on the received service. Then the UE 110 may store one or more QoE measurement reports in a buffer at an operation 214.
  • the buffer may be predefined in the UE application layer or in the UE Access Stratum (AS) layer for storing the QoE measurement reports. It may have a predetermined size such as 32 kB, 64 kB, 128 kB or a larger size.
  • the buffer may also be referred to as a QoE buffer, QoE reporting buffer, or a QMC buffer.
  • the UE 110 may also store one or more QoE measurement reports in the QoE buffer when the timing for QoE reporting is not triggered.
  • the network may configure a long period (i.e., a low frequency) for QoE reporting from the UE 110 to reduce resource consumption and impact on other services.
  • the UE 110 may generate one or more QoE measurement reports during the period and temporarily store them in the QoE buffer.
  • the network may configure a UE load threshold or a cell load threshold for the UE 110. When the threshold is violated, for example when the UE or the cell has higher load than the threshold, the UE 110 would not transmit the QoE measurement reports and instead store the reports in the QoE buffer. In such example embodiments, the operation 212 may be omitted.
  • the UE 110 may detect an indication of a UE mobility procedure.
  • the UE mobility procedure refers to a process where the UE 110 transfers its connection from a source base station (e.g. the base station 122) to a target base station (e.g. the base station 124) .
  • a source base station e.g. the base station 122
  • a target base station e.g. the base station 124.
  • the UE 110 may perform the mobility procedure to transfer connection from the source base station 122 to the target base station 124.
  • the mobility procedure may be performed in different ways.
  • the mobility procedure may include a handover procedure for handing over a UE in a connected state (RRC_CONNECTED) to another cell by sending the corresponding RRC message, e.g., RRCReconfiguration containing ReconfigurationWithSync or MobilityFromNRCommand, a connection setup procedure for a UE in an idle state (RRC_IDLE) , or a connection resume procedure for a UE in an inactive state (RRC_INACTIVE) , which will be discussed in detail below.
  • the UE 110 may detect different indications for the mobility procedures.
  • the UE 110 may determine that an indication of the mobility procedure (i.e. the handover procedure) is detected.
  • the indication of the mobility procedure may also be detected from channel quality measurements when the UE 110 is in the inactive or idle state. For example, when a channel quality measurement reveals that channel quality of the serving cell for the UE 110 deteriorates below a predetermined threshold and a neighbor cell becomes the best cell for the UE 110, the UE 110 knows that the channel quality measurement would trigger a UE mobility procedure, i.e. the connection setup procedure for a UE in the idle state or the connection resume procedure for a UE in the inactive state. Then the UE 110 determines that an indication of the mobility procedure is detected from the channel quality measurement.
  • the UE 110 may also detect the indication of the mobility procedure from other messages, signaling, and actions which explicitly or implicitly indicate that a UE mobility procedure would be performed.
  • the messages, signaling and actions utilized in the UE mobility procedure may also be considered as an indication of the mobility procedure.
  • the UE 110 may transmit a QoE buffer status report relating to the buffer for storing the QoE measurement reports to the target base station 124 during or after the mobility procedure at an operation 218.
  • the QoE buffer status report is triggered by the indication of the mobility procedure.
  • the QoE buffer status report may include at least one of size of buffered QoE data (i.e., one or more QoE measurement reports) in the buffer, left space in the buffer, left time before overflow of the buffer, and initial time for the buffer to store the QoE measurement reports.
  • the left time before overflow of the buffer may be calculated from the left space in the buffer, the size of a single QoE measurement report and the frequency of generating the QoE measurement reports. After the left time, the buffer cannot store a new QoE measurement report because of its limited size, and buffer overflow and data loss may occur.
  • the initial time for the buffer to store the QoE measurement reports may refer to the time of receiving the QoE reporting Pause command at the UE 110 or the time of storing the first QoE measurement report in the buffer.
  • the left time before overflow can also be calculated from the initial time to store the QoE measurement reports, the frequency of generating the QoE measurement reports and the total size of the buffer.
  • the QoE buffer status report may be carried in a message transmitted during the mobility procedure, which will be discussed in detail below.
  • the QoE buffer status report may also be transmitted after the mobility procedure, i.e. when the UE 110 has transferred its connection to the target base station 124. From the QoE buffer status report received at the operation 218, the target base station 124 would know how much QoE data needs to be transmitted from the UE 110 to the target base station 124 and/or how long time the buffer can provide storage for new QoE measurement reports.
  • the target base station 124 may decide to resume the QoE reporting from the UE 110.
  • the target base station 124 may make the decision at least partially based on the QoE buffer status report received from the UE 110 at the operation 218. For example, the target base station 124 has to resume the QoE reporting from the UE 110 before the buffer overflows.
  • the target base station 124 may also make the decision in further consideration of for example load at the new serving cell (the target cell) for the UE 110.
  • the target base station 124 may send a QoE reporting Request message or a QoE reporting Resume command to the UE 110, which indicates the UE 110 to resume transmitting the QoE measurement reports stored in the QoE buffer to the target base station 124.
  • the QoE reporting Request message or Resume command may be transmitted via RRC signaling, MAC CE or downlink control information (DCI) .
  • the UE 110 may transmit the QoE measurement reports stored in the QoE buffer to the target base station 124 at an operation 224.
  • the UE 110 may also transmit the new report to the target base station 124.
  • the buffered and new QoE measurement reports may be transmitted in a container in an RRC measurement report message.
  • the RRC measurement report message may be transmitted on Signaling Radio Bearer Type 4 (SRB4) .
  • the container may be transparent to the target base station 124, and the target base station 124 may just forward the container to the core network (not shown) .
  • QoE measurement collection and reporting continuity can be ensured after the UE 110 transfers from the source base station 122 to the target base station 124.
  • Fig. 2 can be implemented in combination with different UE mobility procedures, examples of which will be described below in detail with reference to Figs. 3-7.
  • Fig. 3 is a schematic message flow diagram illustrating operations for QoE measurement reporting in accordance with some example embodiments.
  • QoE measurement collection and reporting continuity is achieved when the UE 110 transfers its connection from the source base station 122 to the target base station 124 in a handover procedure.
  • the UE 110 may initially connect to the source base station 122 and perform QoE measurements on a service received through the source base station 122 in an operation 310.
  • the UE 110 may stop transmitting the QoE measurement reports to the source base station 122 and instead store the QoE measurement reports in a buffer predefined for QoE measurement report storage at an operation 314.
  • the UE 110 may also store QoE measurement reports in the QoE buffer when the timing for transmitting the QoE measurement reports is not triggered.
  • the operations 310, 312 and 314 may be similar to the operations 210, 212 and 214 discussed above with respect to Fig. 2, and a repetitive description thereof is omitted here.
  • the source base station 122 may send a handover request to the target base station 124.
  • the source base station 122 may make a handover decision based on a channel quality measurement report received from the UE 110.
  • the channel quality measurement report may include channel quality of the serving cell and one or more best cells for the UE 110.
  • the source base station 122 may decide to hand over the UE 110 from the current serving cell (the source cell) to the neighbor cell (the target cell) of the target base station 124 and send the handover request to the target base station 124 to initiate the handover procedure.
  • the handover request may contain UE context and QoE configuration for the UE 110 in the source cell (i.e. the current serving cell) .
  • the QoE configuration of the UE 110 is configured by the source base station 122 before the handover procedure.
  • the target base station 124 may send a handover request acknowledgement message to the source base station 122 at an operation 318.
  • the handover request acknowledgement message may include a transparent container to be sent to the UE 110 as an RRC message to perform the handover, and the container may include resource allocation information for the UE 110 to access the target cell.
  • the container also includes QoE configuration for the UE 110 in the target cell.
  • the target base station 124 may determine the QoE configuration for the UE 110 in the target cell at least partially based on the QoE configuration for the UE 110 in the source cell received in the operation 316.
  • the QoE configuration determined at the target base station 124 for the UE 110 in the target cell may also be referred to as new QoE configuration
  • the QoE configuration determined at the source base station 122 for the UE 110 in the source cell may also be referred to as old QoE configuration.
  • the source base station 122 may send the RRC message prepared by the target base station 124, i.e. an RRC Connection Reconfiguration message, to the UE 110 in a handover command by which the UE 110 is commanded to perform handover.
  • the handover command may include the resource allocation information for the UE 110 to access the target cell and the QoE configuration determined at the target base station 124 for the UE 110 in the target cell.
  • the UE 110 may move connection from the source base station 122 to the target base station 124.
  • the UE 110 may also apply the new QoE configuration to perform QoE measurements on the service received through the target base station 124.
  • the UE 110 may send an RRC Reconfiguration Complete message to the target base station 124.
  • the RRC Reconfiguration Complete message may include a QoE buffer status report relating to the buffer for storing the QoE measurement reports. As discussed above with respect to the operation 218 in Fig.
  • the QoE buffer status report may include at least one of size of buffered data (i.e., one or more QoE measurement reports) in the buffer, left space in the buffer, left time before overflow of the buffer, and initial time for the buffer to store the QoE measurement reports.
  • the target base station 124 can know how much QoE data needs to be transmitted from the UE 110 to the target base station 124 and/or how long time the buffer can provide storage for new QoE measurement reports before buffer overflow occurs.
  • the target base station 124 may decide to resume the QoE reporting from the UE 110 at least partially based on the QoE buffer status report received from the UE 110. Then at an operation 326, the target base station 124 may send a QoE reporting Request message or a QoE reporting Resume command to the UE 110, which indicates the UE 110 to resume transmitting the QoE measurement reports stored in the buffer to the target base station 124. In response to the QoE reporting Request message or Resume command, the UE 110 may transmit on SRB4 the QoE measurement reports stored in the buffer to the target base station 124 at an operation 328.
  • the operations 324, 326 and 328 may be similar to the operations 220, 222 and 224 discussed above with respect to Fig. 2, and a repetitive description thereof is omitted here.
  • the target base station 124 does not know if the QoE reporting is paused or not when the UE 110 connects to the source base station 122.
  • the target base station 124 may determine the timing to resume the QoE reporting from the UE 110.
  • the source base station 122 may also inform the target base station 124 of the QoE reporting status in the UE 110.
  • Fig. 4 illustrates such an example. In the procedure shown in Fig. 4, operations similar to those shown in Fig. 3 are denoted with similar reference numerals and a repetitive description thereof is omitted here.
  • the handover request transmitted from the source base station 122 to the target base station 124 may further include a QoE reporting status indication for the UE 110 in the source cell, in addition to the old QoE configuration for the UE 110 in the source cell.
  • the QoE reporting status indication may indicate whether or not the QoE reporting from the UE 110 is paused by the source base station 122. In the example embodiment shown in Fig. 4, the QoE reporting status indication indicates that the QoE reporting from the UE 110 is paused by the source base station 122.
  • the handover request acknowledgement message transmitted from the target base station 124 to the source base station 122 may further include a new QoE reporting status indication for the UE 110 in the target cell, in addition to the new QoE configuration for the UE 110 in the target cell.
  • the new QoE reporting status indication for the UE 110 in the target cell may be determined by the target base station 124 based on for example the old QoE reporting status of the UE 110 before the handover procedure and the load of the target cell.
  • the target base station 124 may pause QoE reporting from the UE 110 to the target base station 124.
  • Fig. 4 shows an example where the target base station 124 also pauses the QoE reporting from the UE 110 in the new QoE reporting status indication.
  • the source base station 122 may forward the new QoE reporting status indication together with the new QoE configuration to the UE 110 in the handover command at an operation 320a. Since the QoE reporting is paused by the target base station 124, the UE 110 would not transmit the QoE measurement reports stored in the buffer to the target base station 124 until it receives the QoE reporting request message or the QoE reporting resume command in the operation 326.
  • the target base station 124 may decide to resume the QoE reporting from the UE 110 at the operation 318a, when for example the target cell has low load.
  • the UE 110 may transmit the QoE buffer status report to the target base station 124 at the operation 322 and transmit the QoE measurement reports to the target base station 124 at the operation 328.
  • the operations 324, 326 may be omitted in this example embodiment.
  • Fig. 5 is a schematic message flow diagram illustrating operations for QoE measurement reporting in accordance with some example embodiments.
  • QoE measurement collection and reporting continuity is achieved when the UE 110 performs a connection resume procedure to recover from the RRC inactive state to the RRC connected state.
  • the UE 110 may initially connect to the source base station 122 and perform QoE measurements on a service received through the source base station 122 in an operation 410.
  • the UE 110 may stop transmitting the QoE measurement reports to the source base station 122 and instead store the QoE measurement reports in a buffer predefined for QoE measurement report storage at an operation 414.
  • the UE 110 may also store QoE measurement reports in the buffer when the timing for transmitting the QoE measurement reports is not triggered.
  • the operations 410, 412 and 414 may be similar to the operations 210, 212 and 214 discussed above with respect to Fig. 2, and a repetitive description thereof is omitted here.
  • the source base station 122 may send an RRC Connection Release with suspend message to the UE 110 to put the UE 110 in the RRC inactive state.
  • the UE 110 transitions from the RRC connected state to the RRC inactive state at an operation 418.
  • the UE 110 can still receive the service e.g. streaming video service, the Multicast Broadcast Service (MBS) , the Multimedia Telephony Service for IMS (MTSI) , or the Virtual Reality (VR) service from the source base station 122 and perform the QoE measurements on the service when it is in the inactive state.
  • MMS Multicast Broadcast Service
  • MMSI Multimedia Telephony Service for IMS
  • VR Virtual Reality
  • the UE 110 may send an RRC Connection Resume Request message to the target base station 124 to initiate a UE mobility procedure.
  • the network may initiate the UE mobility procedure by paging the UE 110, and then the UE 110 may send the RRC Connection Resume Request message to the target base station 124.
  • the UE 110 may detect/determine an indication of the mobility procedure from the channel quality measurement revealing that the channel quality of the last serving cell for the UE 110 deteriorates below a predetermined threshold and a neighbor cell supported by the target base station 124 becomes the best cell for the UE 110.
  • the RRC Connection Resume Request message may include a QoE buffer status report relating to the buffer for storing the QoE measurement reports at the UE 110.
  • the buffer status report may include at least one of size of buffered data (i.e., one or more QoE measurement reports) in the buffer, left space in the buffer, left time before overflow of the buffer, and initial time for the buffer to store the QoE measurement reports. From the buffer status report, the target base station 124 can know how much QoE data needs to be transmitted from the UE 110 to the target base station 124 and/or how long time the buffer can provide storage for new QoE measurement reports before buffer overflow occurs.
  • the target base station 124 may request the source base station 122 to provide UE context of the UE 110 by sending a Retrieve UE Context Request message to the source base station 122.
  • the source base station 122 may transmit UE Context of the UE 110 to the target base station 124 via a Retrieve UE Context response message.
  • the Retrieve UE Context response message may include QoE configuration for the UE 110 in the source cell.
  • the retrieve UE Context response message may further include a QoE reporting status indication for the UE 110 in the source cell.
  • the QoE reporting status indication may indicate that the QoE reporting from the UE 110 is paused by the source base station 122.
  • the target base station 124 may move the UE 110 to the RRC connected state by sending an RRC Connection Resume message to the UE 110 at an operation 426.
  • the target base station 124 may send the UE 110 back to the RRC inactive state by sending an RRC Release with suspend message.
  • the RRC Connection Resume message or the RRC Release with suspend message may include a new QoE configuration for the UE 110 in the target cell.
  • the RRC Connection Resume message or the RRC Release with suspend message may further include a new QoE reporting status indication for the UE 110 in the target cell.
  • the target base station 124 may determine the new QoE reporting status indication for the UE 110 based on for example the old QoE reporting status of the UE 110 in the source cell and the load in the target cell. In the example shown in Fig. 4, the target base station 124 may also decide to pause the QoE reporting from the UE 110 in the new QoE reporting status indication.
  • the target base station 124 may decide to resume the QoE reporting from the UE 110 at least partially based on the buffer status report received from the UE 110. Then at an operation 430, the target base station 124 may send a QoE reporting Request message or a QoE reporting Resume command to the UE 110, which indicates the UE 110 to resume transmitting the QoE measurement reports stored in the buffer to the target base station 124. In response to the QoE reporting Request message or Resume command, the UE 110 may transmit on SRB4 the QoE measurement reports stored in the buffer to the target base station 124 at an operation 432.
  • the operations 4284, 430 and 432 may be similar to the operations 220, 222 and 224 discussed above with respect to Fig. 2, and a repetitive description thereof is omitted here.
  • the target base station 124 may decide to resume the QoE reporting from the UE 110 at the operation 426 for example when the target cell has low load.
  • the UE 110 may transmit the QoE measurement reports to the target base station 124 at the operation 432.
  • the operations 428, 430 may be omitted in this example embodiment.
  • Fig. 6 is a schematic message flow diagram illustrating operations for QoE measurement reporting in accordance with some example embodiments.
  • QoE measurement collection and reporting continuity is achieved when the UE 110 is in the idle state and it performs a connection setup procedure to establish RRC connection with the target base station.
  • the UE 110 may initially connect to the source base station 122 and perform QoE measurements on a service received through the source base station 122 in an operation 510.
  • the UE 110 may stop transmitting the QoE measurement reports to the source base station 122 and instead store the QoE measurement reports in a buffer predefined for QoE measurement report storage at an operation 514.
  • the UE 110 may also store QoE measurement reports in the buffer when the timing for transmitting the QoE measurement reports is not triggered.
  • the operations 510, 512 and 514 may be similar to the operations 210, 212 and 214 discussed above with respect to Fig. 2, and a repetitive description thereof is omitted here.
  • the source base station 122 may send an RRC Connection Release message to the UE 110 to put the UE 110 in the RRC idle state.
  • the UE 110 transitions from the RRC connected state to the RRC idle state at an operation 518.
  • the UE 110 may stop receiving the service from the source base station 122, but the QoE measurement reports stored in the QoE buffer may be kept at the UE 110.
  • the UE 110 may establish connection with the target base station 124 in a connection setup procedure.
  • the UE 110 may send an RRC Connection Setup Request message to the target base station 124.
  • the RRC Connection Setup Request may be transmitted via Msg. 3 in a 4-step random access (RA) procedure or via Msg. A in a 2-step RA procedure.
  • the RRC Connection Setup Request message may include a QoE buffer status report relating to the buffer for storing the QoE measurement reports at the UE 110.
  • the buffer status report may include at least one of size of buffered data (i.e., one or more QoE measurement reports) in the buffer, left space in the buffer, left time before overflow of the buffer, and initial time for the buffer to store the QoE measurement reports. From the buffer status report, the target base station 124 can know how much QoE data needs to be transmitted from the UE 110 to the target base station 124 and/or how long time the buffer can provide storage for new QoE measurement reports before buffer overflow occurs.
  • the RRC Connection Setup Request transmitted at the operation 520 may further include a QoE reporting status indication for the UE 110 when the UE 110 connects to the source base station 122.
  • the QoE reporting status indication may indicate that the QoE reporting from the UE 110 is paused by the source base station 122.
  • the target base station 124 may send an RRC Connection Setup message to the UE 110.
  • the RRC Connection Setup message may be transmitted via Msg. 4 in the 4-step RA procedure or via Msg. B in the 2-step RA procedure.
  • the RRC Connection Setup message may include QoE configuration for the UE 110 in the target cell.
  • the RRC Connection Setup message may further include a new QoE reporting status indication for the UE 110 in the target cell.
  • the target base station 124 may determine the new QoE reporting status indication for the UE 110 based on for example the old QoE reporting status of the UE 110 before the connection setup procedure and the load in the target cell. In the example shown in Fig. 6, the target base station 124 may also decide to pauses the QoE reporting from the UE 110 in the new QoE reporting status indication.
  • the UE 110 may send an RRC Connection Setup Complete message to the target base station 124.
  • the target base station 124 may decide to resume the QoE reporting from the UE 110 at least partially based on the buffer status report received from the UE 110. Then at an operation 528, the target base station 124 may send a QoE reporting Request message or a QoE reporting Resume command to the UE 110, which indicates the UE 110 to resume transmitting the QoE measurement reports stored in the buffer to the target base station 124. In response to the QoE reporting Request message or Resume command, the UE 110 may transmit on SRB4 the QoE measurement reports stored in the buffer to the target base station 124 at an operation 530.
  • the operations 526, 528 and 530 may be similar to the operations 220, 222 and 224 discussed above with respect to Fig. 2, and a repetitive description thereof is omitted here.
  • the target base station 124 may decide to resume the QoE reporting from the UE 110 at the operation 522 for example when the target cell has low load.
  • the UE 110 may transmit the QoE measurement reports to the target base station 124 at the operation 530.
  • the operations 526, 528 may be omitted in this example embodiment.
  • Fig. 7 illustrates another example of operations to ensure QoE measurement collection and reporting continuity when the UE 110 performs a connection setup procedure.
  • operations similar to those shown in Fig. 6 are denoted with similar reference numerals and a repetitive description thereof is omitted here.
  • the UE 110 may send to the target base station 124 the QoE buffer status report in the RRC Connection Setup Complete message transmitted in the operation 524a, instead of in the RRC Connection Setup Request message transmitted in the operation 520a.
  • the target base station 124 may send to the UE 110 the QoE configuration for the UE 110 in the target cell in an RRC Connection Reconfiguration message transmitted in an operation 525, instead of in the RRC Connection Setup message transmitted in the operation 522a.
  • the target base station 124 may send the QoE configuration to the UE 110 in the operation 522a, and the operation 525 may be omitted.
  • Other aspects of the procedure shown in Fig. 7 may be similar to the procedure shown in Fig. 6 and a repetitive description is omitted here.
  • Fig. 8 is a schematic block diagram illustrating devices in a communication system 600 for implementing one or more example embodiments.
  • the communication system 600 may comprise a plurality erminal devices 610 (one is shown) which may be implemented as the UE 110 discussed above and a plurality of network devices 620 (one is shown) which may be implemented as the base stations 122, 124 discussed above.
  • the terminal device 610 may comprise one or more processors 611, one or more memories 612 and one or more transceivers 613 interconnected through one or more buses 614.
  • the one or more buses 614 may be address, data, or control buses, and may include any interconnection mechanism such as series of lines on a motherboard or integrated circuit, fiber, optics or other optical communication equipment, and the like.
  • Each of the one or more transceivers 613 may comprise a receiver and a transmitter, which are connected to one or more antennas 616.
  • the terminal device 610 may wirelessly communicate with the network device 620 through the one or more antennas 616.
  • the one or more memories 612 may include computer program code 615.
  • the one or more memories 612 and the computer program code 615 may be configured to, when executed by the one or more processors 611, cause the terminal device 610 to perform processes and steps relating to the UE 110 as described above.
  • the network device 620 may comprise one or more processors 621, one or more memories 622, one or more transceivers 623 and one or more network interfaces 627 interconnected through one or more buses 624.
  • the one or more buses 624 may be address, data, or control buses, and may include any interconnection mechanism such as a series of lines on a motherboard or integrated circuit, fiber, optics or other optical communication equipment, and the like.
  • Each of the one or more transceivers 623 may comprise a receiver and a transmitter, which are connected to one or more antennas 626.
  • the network device 620 may wirelessly communicate with the terminal device 610 through the one or more antennas 626.
  • the one or more transceivers 623 and the one or more antennas 626 may be implemented as one or more remote radio heads (RRHs) 628.
  • the one or more RRHs 628 may be collocated or located at different positions.
  • the one or more buses 624 could be implemented in part as fiber optic cable to connect the RRHs 628 to other components of the network device 620.
  • the one or more network interfaces 627 may provide wired or wireless communication links through which the network device 620 may communicate with other network devices, entities, elements or functions.
  • the one or more memories 622 may include computer program code 625.
  • the one or more memories 622 and the computer program code 625 may be configured to, when executed by the one or more processors 621, cause the network device 620 to perform processes and steps relating to the base station 120 as described above.
  • the one or more processors 611, 621 discussed above may be of any appropriate type that is suitable for the local technical network, and may include one or more of general purpose processors, special purpose processor, microprocessors, a digital signal processor (DSP) , one or more processors in a processor based multi-core processor architecture, as well as dedicated processors such as those developed based on Field Programmable Gate Array (FPGA) and Application Specific Integrated Circuit (ASIC) .
  • the one or more processors 611, 621 may be configured to control other elements of the UE/network device and operate in cooperation with them to implement the procedures discussed above.
  • the one or more memories 612, 622 may include at least one storage medium in various forms, such as a volatile memory and/or a non-volatile memory.
  • the volatile memory may include but not limited to for example a random access memory (RAM) or a cache.
  • the non-volatile memory may include but not limited to for example a read only memory (ROM) , a hard disk, a flash memory, and the like.
  • the one or more memories 612, 622 may include but not limited to an electric, a magnetic, an optical, an electromagnetic, an infrared, or a semiconductor system, apparatus, or device or any combination of the above.
  • blocks in the drawings may be implemented in various manners, including software, hardware, firmware, or any combination thereof.
  • one or more blocks may be implemented using software and/or firmware, for example, machine-executable instructions stored in the storage medium.
  • parts or all of the blocks in the drawings may be implemented, at least in part, by one or more hardware logic components.
  • FPGAs Field-Programmable Gate Arrays
  • ASICs Application-Specific Integrated Circuits
  • ASSPs Application-Specific Standard Products
  • SOCs System-on-Chip systems
  • CPLDs Complex Programmable Logic Devices
  • Some exemplary embodiments further provide computer program code or instructions which, when executed by one or more processors, may cause a device or apparatus to perform the procedures described above.
  • the computer program code for carrying out procedures of the exemplary embodiments may be written in any combination of one or more programming languages.
  • the computer program code may be provided to one or more processors or controllers of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • Some exemplary embodiments further provide a computer program product or a computer readable medium having the computer program code or instructions stored therein.
  • the computer readable medium may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the machine readable medium may be a machine readable signal medium or a machine readable storage medium.
  • a machine readable medium may include but is not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • machine readable storage medium More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM portable compact disc read-only memory
  • magnetic storage device or any suitable combination of the foregoing.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers modes de réalisation donnés à titre d'exemple concernent un procédé et un appareil de continuité de rapports de qualité d'expérience. Un dispositif terminal peut être configuré pour réaliser une mesure de qualité d'expérience, QoE, sur un service reçu via un dispositif de réseau source, et lors de la détection d'une indication indiquant une procédure de mobilité pour un transfert, par le biais du dispositif terminal, du dispositif de réseau source vers un dispositif de réseau cible pour le service, transmettre, durant ou après la procédure de mobilité, au dispositif de réseau cible un rapport d'état de mémoire tampon associé à une mémoire tampon servant à stocker un ou plusieurs rapports de mesure QoE.
PCT/CN2022/072068 2022-01-14 2022-01-14 Procédé et appareil de continuité de rapports de qualité d'expérience WO2023133812A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/072068 WO2023133812A1 (fr) 2022-01-14 2022-01-14 Procédé et appareil de continuité de rapports de qualité d'expérience

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/072068 WO2023133812A1 (fr) 2022-01-14 2022-01-14 Procédé et appareil de continuité de rapports de qualité d'expérience

Publications (1)

Publication Number Publication Date
WO2023133812A1 true WO2023133812A1 (fr) 2023-07-20

Family

ID=87280062

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/072068 WO2023133812A1 (fr) 2022-01-14 2022-01-14 Procédé et appareil de continuité de rapports de qualité d'expérience

Country Status (1)

Country Link
WO (1) WO2023133812A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103796270A (zh) * 2009-01-29 2014-05-14 三星电子株式会社 在用户设备处发送缓冲器状态报告的方法及用户设备
CN104205918A (zh) * 2012-03-19 2014-12-10 诺基亚公司 提供数据卸载和载波聚合关联的测量上报的方法和装置
WO2017166989A1 (fr) * 2016-04-01 2017-10-05 电信科学技术研究院 Procédé pour une affectation de ressource dans un processus de commutation, station de base source et station de base cible
WO2021168865A1 (fr) * 2020-02-29 2021-09-02 华为技术有限公司 Procédé et appareil de communication

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103796270A (zh) * 2009-01-29 2014-05-14 三星电子株式会社 在用户设备处发送缓冲器状态报告的方法及用户设备
CN104205918A (zh) * 2012-03-19 2014-12-10 诺基亚公司 提供数据卸载和载波聚合关联的测量上报的方法和装置
WO2017166989A1 (fr) * 2016-04-01 2017-10-05 电信科学技术研究院 Procédé pour une affectation de ressource dans un processus de commutation, station de base source et station de base cible
WO2021168865A1 (fr) * 2020-02-29 2021-09-02 华为技术有限公司 Procédé et appareil de communication

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED, ZTE: "Remaining BSR Transfer in Handover", 3GPP DRAFT; R3-210342, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. 20210125 - 20210205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051975058 *
QUALCOMM INCORPORATED: "Remaining BSR transfer in handover", 3GPP DRAFT; R3-210343, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20210125 - 20210205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051975059 *

Similar Documents

Publication Publication Date Title
US10440691B2 (en) Method for controlling connection status of UE and apparatus thereof
US10736033B2 (en) Secondary cell group configuration
KR102091696B1 (ko) 이동 통신 시스템에서 매크로 셀과 스몰 셀 간 스위칭 동작 수행 장치 및 방법
WO2017152757A1 (fr) Procédé et système de transfert intercellulaire de cellule, et dispositif associé
WO2022147776A1 (fr) Procédé, dispositif et support d'enregistrement informatique de communication
CN105637930A (zh) 用于控制移动通信系统中的移交的方法和装置
EP2936873B1 (fr) Création de rapport de mesure efficace par un équipement d'utilisateur (ue)
US9813953B2 (en) Radio network node, a user equipment and methods therein
CN116965095A (zh) 用于通信的方法、终端设备、网络设备和计算机可读介质
WO2022082567A1 (fr) Procédé et appareil pour des services de multidiffusion/diffusion
WO2023133812A1 (fr) Procédé et appareil de continuité de rapports de qualité d'expérience
US20220182892A1 (en) Communication Method and Apparatus
US20230276203A1 (en) Multicast/broadcast support in dual-connectivity
US20230262566A1 (en) Method, device and computer storage medium of communication
US11140656B2 (en) Paging in a group communications system
KR102640815B1 (ko) 랜덤 액세스 방법, 데이터 수신 방법 및 그 장치, 및 통신 시스템
WO2021102837A1 (fr) Procédés, dispositifs et support pour la communication
US20240015618A1 (en) Methods, devices and computer readable media for communications
EP4366380A1 (fr) Utilisation d'informations relatives à la probabilité d'arrivée estimée pour sélectionner des noeuds secondaires cibles pour un transfert de données précoce pour des communications sans fil à double connectivité
WO2024093097A1 (fr) Dispositifs de communication et procédés de communication
CN110662248B (zh) 信号测量方法和设备
WO2022011515A1 (fr) Procédé et dispositif de communication, et support de stockage d'ordinateur
WO2023194019A1 (fr) Mobilité d'équipement d'utilisateur pour des services de diffusion sélective et de diffusion non sélective
CN117279048A (zh) 小区切换方法及装置、计算机可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22919466

Country of ref document: EP

Kind code of ref document: A1