WO2023135539A1 - Rapporte de qualité d'expérience pour des services de diffusion/multidiffusion - Google Patents

Rapporte de qualité d'expérience pour des services de diffusion/multidiffusion Download PDF

Info

Publication number
WO2023135539A1
WO2023135539A1 PCT/IB2023/050270 IB2023050270W WO2023135539A1 WO 2023135539 A1 WO2023135539 A1 WO 2023135539A1 IB 2023050270 W IB2023050270 W IB 2023050270W WO 2023135539 A1 WO2023135539 A1 WO 2023135539A1
Authority
WO
WIPO (PCT)
Prior art keywords
quality
experience
radio resource
resource control
message
Prior art date
Application number
PCT/IB2023/050270
Other languages
English (en)
Inventor
Hyung-Nam Choi
Joachim Löhr
Ravi Kuchibhotla
Prateek Basu Mallick
Original Assignee
Lenovo (Singapore) Pte. Ltd.
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 Lenovo (Singapore) Pte. Ltd. filed Critical Lenovo (Singapore) Pte. Ltd.
Publication of WO2023135539A1 publication Critical patent/WO2023135539A1/fr

Links

Classifications

    • 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
    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • 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/5032—Generating service level reports
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present disclosure relates to wireless communications, and more specifically to quality of experience measurements in wireless systems.
  • a wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology.
  • Each network communication device such as a base station, may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology.
  • the wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communications system, such as time resources (e.g., symbols, subslots, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers).
  • the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other suitable radio access technologies beyond 5G.
  • wireless networks can provide related services such as multicast broadcast services (MBS).
  • MBS multicast broadcast services
  • MBS can be leveraged to provide content to UEs such as video content, audio content, notification content, and so forth.
  • wireless networks may collect Quality of Experience (QoE) information that pertaining to receipt and output of MBS on a UE.
  • QoE information for instance, informs wireless networks and MBS providers about MBS performance on instances of UEs.
  • the present disclosure relates to methods, apparatuses, and systems that support integration and implementations of QoE reporting for MBS.
  • the present disclosure provides techniques for configuring a UE to collect and report QoE measurements for MBS in a variety of different connectivity states. By supporting QoE measurement collection and reporting in different UE connectivity states, UE power can be conserved and loss of QoE measurements in some connectivity states is mitigated.
  • a request message is transmitted by a first device (e.g., a base station) for receipt by a second device (e.g., a UE), the request message requesting service information for multicast broadcast services received by the second device.
  • a reply message is received that identifies at least one multicast broadcast service received by the second device.
  • a configuration message that specifies a quality of experience measurement configuration for generating and reporting quality of experience measurements at the second device for the at least one multicast broadcast service is transmitted for receipt by the second device.
  • a reporting message is received that includes at least one quality of experience measurement based on the quality of experience configuration for the one or more multicast broadcast services.
  • a request message is received at a first device (e.g., a UE) from a second device (e.g., a base station), the request message requesting service information for multicast broadcast services received by the first device.
  • a reply message is transmitted for receipt by the second device, the reply message identifying at least one multicast broadcast service received by the first device.
  • a configuration message specifying a quality of experience measurement configuration for generating and reporting quality of experience measurements at the first device for the at least one multicast broadcast service is received.
  • a reporting message is transmitted for receipt by the second device, the reporting message including at least one quality of experience measurement based on the quality of experience configuration for the at least one multicast broadcast service.
  • a device context message is received at a first device (e.g., a core network component) from a second device (e.g., a first base station) that includes an identifier for a user equipment, an identifier for a quality of experience reference, quality of experience measurement configuration for at least one multicast broadcast service, and reporting criteria for the user equipment to report quality of experience measurements.
  • a device context request message including the identifier for the user equipment and a request for quality of experience reporting context associated with the user equipment is received from a third device, e.g., another base station.
  • a device context response message is transmitted to the third device that includes an identifier for the quality of experience reference, the quality of experience measurement configuration for the at least one multicast broadcast service, and the reporting criteria for the user equipment to report quality of experience measurements.
  • FIG. 1 illustrates an example of a wireless communications system that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • FIGS. 2-5 illustrate examples of different QoE measurement messages that support QoE reporting for MBS in accordance with aspects of the present disclosure.
  • FIGS. 6-8 illustrate different features of example systems that support QoE reporting for MBS in accordance with aspects of the present disclosure.
  • FIG. 9 illustrates an example of a block diagram of a device that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • FIG. 10 illustrates an example of a block diagram of a device that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • FIG. 11 illustrates an example of a block diagram of a device that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • FIGS. 12-19 illustrate flowcharts of methods that support QoE reporting for MBS in accordance with aspects of the present disclosure.
  • Implementations of QoE reporting for MBS are described, such as related to enabling QoE information for MBS to be collected and reported by UEs in a variety of different states. For instance, as compared with some QoE reporting protocols, by implementing QoE reporting for MBS a UE can be configured to collect and report QoE information in different network connectivity states.
  • Some wireless communications systems are limited in their ability to gather and report QoE information. For instance, some systems lack the ability to determine qualified UEs to select for QoE measurement collection of MBS in different Radio Resource Control (RRC) states, e.g., RRC CONNECTED, RRC IN ACTIVE, and RRC IDLE. For instance, since a user subscription to a broadcast service provider is not needed for the reception of MBS data, a UE may not perform a Non-Access Stratum (NAS) joining procedure to indicate to a network that the UE wants to join an MBS. Further, some systems lack the ability to retrieve QoE information for MBS broadcast services in an RRC CONNECTED state which a UE collected in RRC IDLE state. For instance, when a UE is mobile and in RRC IDLE state, the UE may want to transmit QoE information for MBS in a serving cell that does not have any information about the QoE measurement configurations for MBS of that UE.
  • RRC Radio Resource Control
  • some wireless communication systems lack specific procedures for a UE to compile and send QoE information.
  • the total size of a QoE measurement report may exceed an RRC Protocol Data Unit (PDU) size limit (e.g., 9000 bytes, which is equal to a maximum Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) size).
  • PDU RRC Protocol Data Unit
  • PDCP Packet Data Convergence Protocol
  • SDU Service Data Unit
  • the amount of uplink (UL) data to send using SDT can be limited by a network (e.g., based on data volume threshold, dynamic and configured grant (CG) size, etc.) and thus may be even lower than 9000 bytes.
  • CG dynamic and configured grant
  • this disclosure introduces comprehensive techniques for QoE reporting for MBS.
  • the present disclosure provides techniques for configuring UEs to collect QoE information for MBS in a variety of different UE connectivity states, such as RRC Connected, RRC Inactive, and RRC Idle states.
  • UE connectivity states such as RRC Connected, RRC Inactive, and RRC Idle states.
  • RRC Connected a UE can collect and report QoE information without transitioning to an RRC Connected state. This conserves UE power resources by not causing the UE to transition to a connected state and avoids loss of QoE information that may occur in an inactive state in some wireless communication systems.
  • a UE can collect QoE measurements in an RRC Idle state and report the QoE measurements when it transitions to a connected state. This avoids the loss of QoE measurements that occurs in some wireless communication systems.
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one or more base stations 102, one or more UEs 104, and a core network (CN) 106.
  • the wireless communications system 100 may support various radio access technologies.
  • the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LTE- A) network.
  • the wireless communications system 100 may be a 5G network, such as an NR network.
  • the wireless communications system 100 may be a combination of a 4G network and a 5G network.
  • the wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the one or more base stations 102 may be dispersed throughout a geographic region to form the wireless communications system 100.
  • One or more of the base stations 102 described herein may be or include or may be referred to as a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), a Radio Head (RH), a relay node, an integrated access and backhaul (IAB) node, or other suitable terminology.
  • a base station 102 and a UE 104 may communicate via a communication link 108, which may be a wireless or wired connection.
  • a base station 102 and a UE 104 may perform wireless communication over a Uu interface.
  • a base station 102 may provide a geographic coverage area 110 for which the base station 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 110.
  • a base station 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies.
  • a base station 102 may be moveable, for example, a satellite associated with a non-terrestrial network.
  • different geographic coverage areas 110 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 110 may be associated with different base stations 102.
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • the one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100.
  • a UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, a customer premise equipment (CPE), or a subscriber device, or some other suitable terminology.
  • the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples.
  • the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.
  • a UE 104 may be stationary in the wireless communications system 100.
  • a UE 104 may be mobile in the wireless communications system 100.
  • the one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1.
  • a UE 104 may be capable of communicating with various types of devices, such as the base stations 102, other UEs 104, or network equipment (e.g., the CN 106, a relay device, an integrated access and backhaul (IAB) node, or another network equipment), as shown in FIG. 1.
  • a UE 104 may support communication with other base stations 102 or UEs 104, which may act as relays in the wireless communications system 100.
  • a UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 112.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link 112 may be referred to as a sidelink.
  • a UE 104 may support wireless communication directly with another UE 104 over a PC 5 interface.
  • a base station 102 may support communications with the CN 106, or with another base station 102, or both.
  • a base station 102 may interface with the CN 106 through one or more backhaul links 114 (e.g., via an SI, NG, or another network interface).
  • the base stations 102 may communicate with each other over the backhaul links 114 (e.g., via an X2, Xn, or another network interface).
  • the base stations 102 may communicate with each other directly (e.g., between the base stations 102).
  • the base stations 102 may communicate with each other indirectly (e.g., via the CN 106).
  • one or more base stations 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC).
  • An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).
  • TRPs transmission-reception points
  • the CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)).
  • the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for the one or more UEs 104 served by the one or more base stations 102 associated with the CN 106.
  • NAS non-access stratum
  • one or more of the UEs 104, the base stations 102, and/or one or more CN 106 components are operable to implement various aspects of QoE reporting for MBS, as described herein. For instance, leveraging the described techniques, a base station 102 and a UE 104 exchange configuration messages 116 for informing the base station 102 about MBS 118 received by the UE 104, and for configuring the UE 104 to report QoE measurements for the MBS 118 to the base station 102. For instance, based on the configuration messages 116, the UE 104 generates QoE measurements for the MBS 118 and communicates QoE reporting 120 that includes the QoE measurements to the base station 102.
  • the QoE reporting 120 identifies QoE measurements collected at the UE 104.
  • QoE measurements include parameters such as Public Land Mobile Network (PLMN) target for MBS, a session to record of an application, MBS service type, MBS area scope (list of cells and/or list of tracking areas), QoE reference (e.g., a destination for the QoE measurement reports to be sent (e.g., Trace Collection Entity/ Measurement Collection Entity (TCE/MCE)), QoE metrics of the concerned service type, e.g., start time and duration of recording of MBS.
  • QoE metrics for streaming services include amongst other average throughput volume, Initial Playout Delay, UE Buffer Level, Play List, UE device information, etc.
  • Example implementations and details for the configuration messages 116 and the QoE reporting 120 are discussed below.
  • the QoE information included in the QoE reporting 120 can be utilized for various purposes, such as for optimizing MBS 118, optimizing delivery of MBS 118, optimizing performance of a UE 104 that receives MBS 118, and so forth.
  • Some wireless communication systems are implementing the ability to allow the resource-efficient and reliable transmission of MBS traffic data to multiple UEs in a specific service area at the same time in a RAN.
  • the same content of traffic data can be transmitted to all UEs in a particular service area, whereas in case of multicast services, the same content of traffic data can be transmitted to a group of UEs located in a specific service area.
  • targeted applications/services for MBS include Internet Protocol television (IPTV), Linear TV, Radio, Group communications (voice/data/video), loT applications, V2X applications, software delivery, and so forth.
  • an MBS service area consists of one or multiple cells and MBS traffic data can be delivered in each of those cells either per Point-To-Multipoint (PTM) or Point-To-Point (PTP) to the UEs.
  • PTM Point-To-Multipoint
  • PTP Point-To-Point
  • a 5G CN receives a single copy of MBS data packets and delivers the single copy of those MBS packets to RAN, which then delivers them to multiple UEs.
  • the 5G CN receives a single copy of MBS data packets and delivers separate copies of those MBS packets to RAN, which then delivers them to the UEs individually.
  • the use of the MBS delivery methods can be dependent on various factors such as type of service (broadcast or multicast), the number of MBS-capable UEs located in a service area cell, cell load situation and QoS requirements. For instance, in a scenario where a multicast service is provided and the cell load is high and there are many MBS-capable UEs located in the cell which are receiving or interested in receiving the concerned multicast service, the gNB may decide to deliver traffic data of the multicast service per PTM to the UEs. Otherwise, the gNB may decide to deliver traffic data of the multicast service individually per PTP to the UEs.
  • a UE may move across MBS and non-MBS service areas.
  • the network can receive feedback such as Hybrid Automatic Repeat Request (HARQ) or Radio Link Control (RLC) acknowledgements from the UEs.
  • HARQ Hybrid Automatic Repeat Request
  • RLC Radio Link Control
  • the network may have no knowledge whether MBS have been successfully received or not by the UEs. Hence, the network may not be able to verify the performance of broadcast transmissions in the concerned MBS service areas.
  • an information element is proposed with which a UE can inform the network about the MBS which the UE is receiving/interested to receive or no longer receiving/interested to receive.
  • the UE can utilize the UEAssistancelnformation IE or a new RRC message to report MBS interest.
  • W eMBS-Interestlndication IE has following drawbacks: firstly, it is sent by the UE in an unsolicited manner, so the network has to wait to receive this indication from the UE. Secondly, it is lacking the information about the MBS broadcast services which the UE are actually receiving. Without this information the network may not know whether the UE it selects will actually perform QoE measurement collection and reporting for MBS.
  • Smartphone applications o Traffic from Instant Messaging (IM) services o Heart-beat/keep-alive traffic from IM/email clients and other applications o Push notifications from various applications
  • IM Instant Messaging
  • Non-smartphone applications o Traffic from wearables (e.g., periodic positioning information) o Sensors (e.g., Industrial Wireless Sensor Networks transmitting temperature, pressure readings periodically or in an event-triggered manner) o Smart meters and smart meter networks sending periodic meter readings
  • wearables e.g., periodic positioning information
  • Sensors e.g., Industrial Wireless Sensor Networks transmitting temperature, pressure readings periodically or in an event-triggered manner
  • Smart meters and smart meter networks sending periodic meter readings
  • SDT in inactive state can be performed by an SDT-capable UE in the cell in which the SDT configuration was received from the gNB via common and dedicated signalling and when the amount of UL data across radio bearers for which SDT is enabled is lower than a configured data volume threshold. If the amount of UL data across radio bearers for which SDT is enabled is larger than a configured data volume threshold then the UE initiates legacy RRC connection resume procedure to resume the suspended RRC connection with the network in connected state for UL data transmission.
  • pre-allocated resources e.g., random access channel (RACH) resources
  • RACH random access channel
  • a UE can be allowed to concatenate multiple QoE measurement reports into a single MeasurementReportAppLayer message. If the size of the MeasurementReportAppLayer message exceeds a limit of 9000 bytes then it can be segmented into a number of segments. The size of each segment can be adapted according to a configured data volume threshold or dynamic/configured grant size.
  • the main drawback of this solution is that a loss of at least one segment will result in loss of all QoE measurement reports which were concatenated into the single MeasurementReportAppLayer message.
  • This disclosure provides a framework for enabling wireless networks and UEs to collect and report QoE measurement reports over various UE RRC states and of different data sizes. For instance, a wireless network implements a set of messages configured to enable QoE logic of UEs to be configured and QoE measurements to be gathered by UEs and reported. Further, different procedures are employed to accommodate UE transitions between different RRC states and different network locations.
  • FIGS. 2-5 present some example message types that can be implemented to enable QoE reporting for MBS, such as to optimize QoE measurement and reporting between a UE 104 and a wireless network.
  • the described messages represent instances of the configuration messages 116 and/or the QoS reporting 120 described with reference to the wireless communications system 100. Further, the messages can be implemented as separate messages and/or can be combined to generate integrated messages that include different parameters pertaining to QoE reporting for MBS.
  • the described messages can be implemented in various ways such as information elements, new QoE messages, novel extensions of existing messages, and so forth.
  • the described messages are presented for purpose of example only and it is to be appreciated that a variety of different types and forms of messages can be utilized in accordance with the described and claimed implementations.
  • FIG. 2 illustrates an example of a service request message 200 that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the service request message 200 may implement or be implemented by aspects of the wireless communications system 100.
  • the service request message 200 is called an “MBSServiceRequesf message and can be used by a network to request that a UE reports MBS that the UE is receiving and/or interested in receiving.
  • no specific parameter is defined in the service request message 200 but the ASN.1 structure of the service request message 200 has been defined in this way to allow extensions to the structure of the service request message 200.
  • Example usage of the service request message 200 is described below.
  • FIG. 3 illustrates an example of a service response message 300 that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the service response message 300 may implement or be implemented by aspects of the wireless communications system 100.
  • the service response message 300 is called an “MBSService Response” message and can be used by a UE to respond to the service request message 200.
  • the service response message 300 includes a parameter 302 “mbs- ResponseList-rl8” to report a list of MBS that a UE is receiving and the radio frequency on which the concerned MBS is received.
  • a UE can report a list of up to n MBS.
  • an MBS within a PLMN can be uniquely identified by an identifier of 24 bits length.
  • the UE can send an empty response, e.g., the parameter 302 will be empty.
  • Example usage of the service response message 300 is described below.
  • the service request message 200 and/or the service response message 300 can be sent when a UE is in the RRC CONNECTED and RRC INACTIVE states. Further, based on the information received from a UE in the service response message 300 a network can configure the UE for QoE measurement collection for MBS.
  • a “UE Idle QoE context” message is introduced which may contain a list of QoE configurations and where the QoE configuration can include the following information: (1) a UE identity (e.g. 5G- Shortened Temporary Mobile Subscriber Identity (5G-S-TMSI)), (2) a QoE reference identity, (3) valid QoE measurement configurations for MBS in RRC IDLE, (4) valid QoE measurement reporting configurations for MBS in RRC IDLE, and so forth.
  • a UE identity e.g. 5G- Shortened Temporary Mobile Subscriber Identity (5G-S-TMSI)
  • 5G-S-TMSI 5G- Shortened Temporary Mobile Subscriber Identity
  • FIG. 4 illustrates an example of an idle reporting message 400 that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the idle reporting message 400 may implement or be implemented by aspects of the wireless communications system 100.
  • the network when a UE is transferred by a wireless network to RRC IDLE state using an RRC Release message, the network utilizes the idle reporting message 400 to communicate new QoE measurement reporting configurations to a UE. For example, in a scenario where a UE is transferred from RRC CONNECTED to RRC IDLE or from RRC INACTIVE to RRC IDLE, the network omits the SuspendConfig IE in an RRC Release message and instead includes the idle reporting message 400 with a parameter 402 “qoe-ReportConfigIdle-rl8” which is configured to indicate a type of trigger for a UE to transmit QoE measurement reports.
  • a value “immediate” for the parameter 402 indicates that a UE is to transmit QoE measurement report(s) via a MeasurementReportAppLayer message when the UE AS receives a new QoE measurement report from its application layer (AL).
  • the UE can initiate an RRC connection establishment procedure to transmit the QoE measurement report in connected state.
  • a value “event” for the parameter 402 indicates that the UE is to transmit QoE measurement report(s) via the MeasurementReportAppLayer message when other event(s) initiate the establishment of an RRC connection, e.g., NAS registration update, paging for MT call, due to an MO call, and so forth.
  • FIG. 5 illustrates an example of suspend configuration message 500 that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the suspend configuration message 500 may implement or be implemented by aspects of the wireless communications system 100.
  • the suspend configuration message 500 can be used in scenarios where a UE is transferred from RRC CONNECTED to RRC INACTIVE. For instance, within the suspend configuration message 500 in an RRC Release message a new parameter 502 “qoe-ReportConfigInactive-rl8” is configured.
  • the field 504 “rrc- MessageSizeSDT-rl8” is applicable when the UE is configured for SDT and indicates the maximum RRC PDU size of a MeasurementReportAppLayer message on which the QoE measurement reports can be sent when the UE is in an RRC Inactive state. For instance, a value “kBl” corresponds to 1 Kbyte, value “kB2” corresponds to 2 Kbytes and so on. In accordance with the configuration of the field 504 the UE can concatenate one or multiple QoE measurement reports into a single MeasurementReportAppLayer message, such as to avoid segmentation of the MeasurementReportAppLayer message.
  • the field 504 may be used by the UE as an additional threshold to determine whether an SDT or non-SDT procedure is to be performed.
  • the value of the field 504 is defined by a network. Further, the value of the field 504 may be associated with the configured data volume threshold, e.g., if a data volume threshold of 6 Kbytes has been configured by the network then the field 504 may be set to the same or a lower value.
  • a field 506 “reportTriggerTypeNonSDT-rl8” is applicable when a UE is not configured for SDT and indicates the type of trigger for transmitting QoE measurement reports. For instance, a value “immediate” indicates that the UE is to transmit QoE measurement report(s) via the MeasurementReportAppLayer message when the UE AS receives a new QoE measurement report from its AL. For instance, in this scenario the UE initiates an RRC connection resume procedure to transmit the QoE measurement report in connected state.
  • a value “event” in the field 506 indicates that the UE is to transmit QoE measurement report(s) via the MeasurementReportAppLayer message when other event(s) initiate resumption of an RRC connection, e.g., RAN notification area update, paging for MT call, an MO call, etc.
  • an RRC connection e.g., RAN notification area update, paging for MT call, an MO call, etc.
  • a UE autonomously transfers from RRC IN ACTIVE to RRC IDLE e.g., due to reception of a CN paging message, cell reselection occurred, the UE could’t find a suitable cell
  • the UE can continue to use the field 506 (if configured) in RRC IDLE.
  • FIG 6. depicts a system 600 for implementations for QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the system 600 may implement or be implemented by aspects of the wireless communications system 100.
  • the system 600 for example, describes an implementation for configuration of QoE measurements for MBS and related QoE measurement reporting.
  • both a base station 102 and a UE 104 support MBS, QoE, and SDT in inactive state.
  • an Operation and Maintenance (OAM) entity of a wireless network is interested in receiving QoE measurements for an MBS (identified by an MBS service identity #1) from UEs which are being served in a PLMN and sends to a CN 106 a “Configure QoE measurement” message including a QoE measurement configuration for the concerned MBS.
  • the CN 106 sends to the base station 102 an “Activate QoE measurement” message including the QoE measurement configuration for the concerned MBS.
  • the UE 104 is in an RRC Connected state 602 and receives unicast services and 4 MBS 118 broadcast services with service identities #1 to #4. To determine whether the UE is qualified for the QoE measurement collection for the concerned MBS broadcast service with identity #1, the base station 102 sends to the UE 104 the service request message 200 to request that the UE 104 reports the MBS the UE 104 is receiving.
  • the UE 104 generates an instance of the service response message 300 and responds to the service request message 200 by sending the service response message 300 containing the following list of information: o Entry 1: carrierFreq-rl8 set to “frequency 1” and serviceld-rl 8 set to “Identity #1” o Entry 2: carrierFreq-rl8 set to “frequency 1” and serviceld-rl 8 set to “Identity #2” o Entry 3: carrierFreq-rl8 set to “frequency 1” and serviceld-rl 8 set to “Identity #3” o Entry 4: carrierFreq-rl8 set to “frequency 2” and serviceld-rl 8 set to “Identity #4”
  • the base station 102 determines that the UE is qualified for QoE measurement collection for the concerned MBS broadcast service with identity #1.
  • the base station 102 generates and sends an RRC Reconfiguration message 604 that includes respective QoE measurement configuration 606 for MBS.
  • the AS layer of the UE 104 sends the received QoE measurement configuration 606 to an AL of the UE 104, and the AL starts QoE measurement collection 608 in accordance with the received QoE measurement configuration 606.
  • the AL of the UE 104 sends QoE measurement reports 610 with collected QoE measurements to its AS layer.
  • the AS layer of the UE 104 sends the QoE measurement reports 610 via a MeasurementReportAppLayer message to the base station 102, and the gNB forwards the received QoE measurement reports 610 to a TCE/MCE, not expressly depicted in FIG. 6.
  • the base station 102 sends an RRC Release message 612 to the UE 104 to transfer the UE 104 to inactive state, e.g., due to low UE activity in the connected state.
  • the RRC Release message 612 includes the suspend configuration message 500 including the Next Hop Chaining Counter (NCC) value for generating security keys to be used for SDT, SDT configuration, and the parameter 502.
  • the SDT configuration includes the Signalling Radio Bearers (SRB), Data Radio Bearers (DRB), data volume threshold, the CG-SDT resources, and corresponding Timing Advance (TA) timer configuration for CG- based SDT.
  • SRB Signalling Radio Bearers
  • DRB Data Radio Bearers
  • TA Timing Advance
  • the parameter 502 of the suspend configuration message 500 includes the field 504 set to “kB2”, e.g., a maximum RRC PDU size of the MeasurementReportAppLayer message on which QoE measurement reports can be sent in inactive state is limited to 2 Kbytes. This is not to be construed as limiting, however, and a variety of different size thresholds may be utilized.
  • the UE 104 transitions to an RRC Inactive state 614 and in the inactive state continues with reception of the 4 MBS broadcast services and continues with the QoE measurement collection 608 and sending QoE measurement reports 610 for the MBS with identity #1.
  • the AL of the UE 104 sends subsequent collected measurement results to its AS layer in configured reporting interval in the QoE measurement reports 610.
  • a size of a QoE measurement report 610 is 1 Kbyte.
  • FIG. 7 depicts a UL AS protocol layer configuration 700 for UL transmissions using SDT resources in accordance with aspects of the present disclosure.
  • SRBs are configured: SRB1 for transmitting high priority RRC messages, SRB2 for transmitting NAS message, and SRB4 for transmitting the lower priority MeasurementReportAppLayer message.
  • DRB1 for transmitting data of an Instant Messaging (IM) service and DRB2 for transmitting data of a positioning service.
  • IM Instant Messaging
  • FIG 8 depicts a system 800 for implementations for QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the system 800 may implement or be implemented by aspects of the wireless communications system 100.
  • the system 800 describes a further implementation for configuration of QoE measurements for MBS and related QoE measurement reporting.
  • the different conditions discussed at the beginning of the system 600 apply.
  • the different interactions discussed in the system 600 between a base station 102a and the UE 104 to configure the UE 104 for QoE collection and reporting while the UE 104 is in the RRC Connected state 602 are incorporated into the system 800 without being expressly illustrated.
  • the base station 102a and the UE 104 exchange the service request message 200, the service response message 300, and the RRC reconfiguration message 604 with the QoE measurement configuration 606 such that the UE 104 initiates the QoE collection 608 and communicates QoE measurement reports 610 to the base station 102a.
  • the base station 102a sends an RRC Release message 802 to the UE 104 to transfer the UE 104 to an idle state, e.g., RRC Idle. For instance, since no unicast services are running on the UE 104 in the connected state 602, the base station 102a instructs the UE 104 to transition to an idle state.
  • an idle state e.g., RRC Idle.
  • the RRC Release message 802 includes the idle reporting message 400 with the parameter “qoe-ReportConfigIdle-rl8” where the parameter 402 “reportTriggerType-rl8” is set to value “immediate.” In at least one implementation this means the UE 104 is to transmit QoE measurement report(s) via the MeasurementReportAppLayer message when the AS of the UE 104 receives a new QoE measurement report from its AL. [0060] The base station 102a sends a UE Idle QoE context message 804 to the core network 106, e.g., an AMF.
  • the core network 106 e.g., an AMF.
  • the UE Idle QoE context message 804 includes the following information: i) the UE identity for the UE 104 set to 5G-S-TMSI; ii) the QoE measurement configuration for the MBS with identity #1 iii) the QoE reference identity associated with the MBS with identity #1; and iv) the QoE measurement reporting configuration, e.g., the reportTriggerType-rl8 set to value “immediate”.
  • the UE 104 in idle state continues with reception of the 4 MBS 118 and continues with the QoE measurement collection and reporting for the MBS broadcast service with identity #1.
  • the AL of the UE sends collected QoE measurements to its AS layer in a QoE measurement report.
  • a reporting trigger 806 occurs based on the UE 104 determining that QoE measurements are available from its AL.
  • the UE 104 to transmit pending QoE measurement reports immediately as specified by the idle reporting message 400, the UE 104 initiates an RRC connect procedure 808 with a base station 102b, e.g., a base station in a current serving cell on which the UE is camped on.
  • the UE 104 for instance, has moved to a different serving cell since the RRC release message 802.
  • the UE indicates in the RRCSetupComplete message the availability of QoE measurements for MBS by including the “UE Idle QoE context” as part of the RRC connect procedure 808.
  • the base station 102b sends a UE idle context request message 810 to the CN 106.
  • the UE idle context request message 810 for instance, includes an identifier for the UE 104 and a request for QoE reporting context for the UE 104.
  • the core network 106 generates UE idle context response 812 and communicates the UE idle context response 812 to the base station 102b.
  • the UE idle context response 812 for instance, includes information from the UE Idle QoE context message 804, such as described above.
  • the base station 102b verifies a QoE configuration for the UE so that the base station 102b sends the RRC reconfiguration message 604 with an indication for the UE 104 to activate QoE measurement reporting.
  • the UE 104 sends a pending QoE measurement report 610 via a MeasurementReportAppLayer message to the base station 102b, and the base station 102b forwards the received QoE measurement report 610 to the TCE/MCE, which is not expressly depicted in the system 800.
  • FIG. 9 illustrates an example of a block diagram 900 of a device 902 that supports
  • the device 902 may be an example of a UE 104 as described herein.
  • the device 902 may support wireless communication with one or more base stations 102, UEs 104, or any combination thereof.
  • the device 902 may include components for bi-directional communications including components for transmitting and receiving communications, such as a communication manager 904, a processor 906, a memory 908, a receiver 910, a transmitter 912, and an EO controller 914. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).
  • the communication manager 904, the receiver 910, the transmitter 912, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the communication manager 904, the receiver 910, the transmitter 912, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
  • the communication manager 904, the receiver 910, the transmitter 912, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry).
  • the hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 906 and the memory 908 coupled with the processor 906 may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor 906, instructions stored in the memory 908).
  • the communication manager 904, the receiver 910, the transmitter 912, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by the processor 906. If implemented in code executed by the processor 906, the functions of the communication manager 904, the receiver 910, the transmitter 912, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).
  • code e.g., as communications management software or firmware
  • the functions of the communication manager 904, the receiver 910, the transmitter 912, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in
  • the communication manager 904 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 912, or both.
  • the communication manager 904 may receive information from the receiver 910, send information to the transmitter 912, or be integrated in combination with the receiver 910, the transmitter 912, or both to receive information, transmit information, or perform various other operations as described herein.
  • the communication manager 904 is illustrated as a separate component, in some implementations, one or more functions described with reference to the communication manager 904 may be supported by or performed by the processor 906, the memory 908, or any combination thereof.
  • the memory 908 may store code, which may include instructions executable by the processor 906 to cause the device 902 to perform various aspects of the present disclosure as described herein, or the processor 906 and the memory 908 may be otherwise configured to perform or support such operations.
  • the communication manager 904 may support wireless communication at a first device (e.g., the device 902) in accordance with examples as disclosed herein.
  • the communication manager 904 and/or other device components may be configured as or otherwise support a means for wireless communication at a device, including receiving a request message from a second device, the request message requesting service information for multicast broadcast services received by the first device; transmitting a reply message for receipt by the second device, the reply message identifying at least one multicast broadcast service received by the first device; receiving a configuration message, the configuration message specifying a quality of experience measurement configuration for generating and reporting quality of experience measurements at the first device for the at least one multicast broadcast service; and transmitting a reporting message for receipt by the second device, the reporting message including at least one quality of experience measurement based on the quality of experience configuration for the at least one multicast broadcast service.
  • wireless communication at the device includes any one or combination of: further including receiving the request message while the first device is in a radio resource control connected state or a radio resource control inactive state; further including collecting the one or more quality of experience measurements for the at least one multicast broadcast service while the first device is in any one of a radio resource control inactive state or a radio resource control idle state; further including generating the at least one quality of experience measurement for the at least one multicast broadcast service, and communicating the at least one quality of experience measurement to the communications manager for inclusion as part of the reporting message; where the quality of experience measurement configuration specified by the configuration message includes a report trigger for the first device to send quality of experience measurements to the second device, further including transmitting the reporting message based on detecting the report trigger; further including receiving a radio resource control release message from the second device, the radio resource control release message specifying reporting parameters for the first device to report quality of experience measurements for multicast broadcast services received at the first device while the first device is in a radio resource control inactive state; and transmitting a further reporting message that
  • wireless communication at the device includes any one or combination of: further including receiving a radio resource control release message from the second device, the radio resource control release message specifying a report trigger for the first device to initiate reporting of quality of experience measurements for multicast broadcast services received at the first device while the first device is in a radio resource control idle state; receiving an indication that the report trigger occurs while the first device is in the radio resource control idle state; transmitting an indication of an availability of quality of experience measurements in conjunction with a transition of the first device from the radio resource control idle state to a radio resource control connected state; receiving a radio resource control reconfiguration message in conjunction with transitioning from the radio resource control idle state to a radio resource control connected state, the radio resource control reconfiguration message indicating that the second device is to activate quality of experience reporting; and transmitting a further reporting message that includes at least one further quality of experience measurement for receipt by the second device; where the report trigger specifies one or more of: that the first device is to initiate reporting of quality of experience measurements upon detecting an availability of the at least one further quality of experience measurement
  • a device for wireless communication includes a communications manager and a transceiver configured to cooperatively: receive a request message from a second device, the request message requesting service information for multicast broadcast services received by the first device; transmit a reply message for receipt by the second device, the reply message identifying at least one multicast broadcast service received by the first device; receive a configuration message, the configuration message specifying a quality of experience measurement configuration for generating and reporting quality of experience measurements at the first device for the at least one multicast broadcast service; and transmit a reporting message for receipt by the second device, the reporting message including at least one quality of experience measurement based on the quality of experience configuration for the at least one multicast broadcast service.
  • the device for wireless communication includes any one or combination of: where the communications manager and the transceiver are configured to cooperatively receive the request message while the first device is in a radio resource control connected state or a radio resource control inactive state; where the communications manager is further configured to collect the one or more quality of experience measurements for the at least one multicast broadcast service while the first device is in any one of a radio resource control inactive state or a radio resource control idle state; further including an application layer configured to generate the at least one quality of experience measurement for the at least one multicast broadcast service, and to communicate the at least one quality of experience measurement to the communications manager for inclusion as part of the reporting message; where the quality of experience measurement configuration specified by the configuration message includes a report trigger for the first device to send quality of experience measurements to the second device, and where the communications manager and the transceiver are configured to transmit the reporting message based on detecting the report trigger; where the communications manager and the transceiver are further configured to cooperatively: receive a radio resource control release message from the second device, the radio resource control
  • the device for wireless communication includes any one or combination of: where the communications manager and the transceiver are further configured to cooperatively: receive a radio resource control release message from the second device, the radio resource control release message specifying a report trigger for the first device to initiate reporting of quality of experience measurements for multicast broadcast services received at the first device while the first device is in a radio resource control idle state; receive an indication that the report trigger occurs while the first device is in the radio resource control idle state; transmit an indication of an availability of quality of experience measurements in conjunction with a transition of the first device from the radio resource control idle state to a radio resource control connected state; receive a radio resource control reconfiguration message in conjunction with transitioning from the radio resource control idle state to a radio resource control connected state, the radio resource control reconfiguration message indicating that the second device is to activate quality of experience reporting; and transmit a further reporting message that includes at least one further quality of experience measurement for receipt by the second device; where the report trigger specifies one or more of: that the first device is to initiate reporting of quality of experience measurements upon
  • the processor 906 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof).
  • the processor 906 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 906.
  • the processor 906 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 908) to cause the device 902 to perform various functions of the present disclosure.
  • the memory 908 may include random access memory (RAM) and read-only memory (ROM).
  • the memory 908 may store computer-readable, computer-executable code including instructions that, when executed by the processor 906 cause the device 902 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code may not be directly executable by the processor 906 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 908 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 914 may manage input and output signals for the device 902.
  • the I/O controller 914 may also manage peripherals not integrated into the device 902.
  • the I/O controller 914 may represent a physical connection or port to an external peripheral.
  • the I/O controller 914 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system.
  • the I/O controller 914 may be implemented as part of a processor, such as the processor 906.
  • a user may interact with the device 902 via the I/O controller 914 or via hardware components controlled by the I/O controller 914.
  • the device 902 may include a single antenna 916. However, in some other implementations, the device 902 may have more than one antenna 916, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the receiver 910 and the transmitter 912 may communicate bi-directionally, via the one or more antennas 916, wired, or wireless links as described herein.
  • the receiver 910 and the transmitter 912 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 916 for transmission, and to demodulate packets received from the one or more antennas 916.
  • FIG. 10 illustrates an example of a block diagram 1000 of a device 1002 that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the device 1002 may be an example of a base station 102, such as a gNB as described herein.
  • the device 1002 may support wireless communication with one or more base stations 102, UEs 104, or any combination thereof.
  • the device 1002 may include components for bi-directional communications including components for transmitting and receiving communications, such as a communications manager 1004, a processor 1006, a memory 1008, a receiver 1010, a transmitter 1012, and an I/O controller 1014.
  • the communications manager 1004, the receiver 1010, the transmitter 1012, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the communications manager 1004, the receiver 1010, the transmitter 1012, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
  • the communications manager 1004, the receiver 1010, the transmitter 1012, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry).
  • the hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 1006 and the memory 1008 coupled with the processor 1006 may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor 1006, instructions stored in the memory 1008).
  • the communications manager 1004, the receiver 1010, the transmitter 1012, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by the processor 1006. If implemented in code executed by the processor 1006, the functions of the communications manager 1004, the receiver 1010, the transmitter 1012, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).
  • code e.g., as communications management software or firmware
  • the functions of the communications manager 1004, the receiver 1010, the transmitter 1012, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in
  • the communications manager 1004 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1012, or both.
  • the communications manager 1004 may receive information from the receiver 1010, send information to the transmitter 1012, or be integrated in combination with the receiver 1010, the transmitter 1012, or both to receive information, transmit information, or perform various other operations as described herein.
  • the communications manager 1004 is illustrated as a separate component, in some implementations, one or more functions described with reference to the communications manager 1004 may be supported by or performed by the processor 1006, the memory 1008, or any combination thereof.
  • the memory 1008 may store code, which may include instructions executable by the processor 1006 to cause the device 1002 to perform various aspects of the present disclosure as described herein, or the processor 1006 and the memory 1008 may be otherwise configured to perform or support such operations.
  • the communications manager 1004 may support wireless communication at a first device (e.g., the base station as device 1002) in accordance with examples as disclosed herein.
  • the communications manager 1004 and/or other device components may be configured as or otherwise support a means for wireless communication at a base station, including transmitting from a first device a request message for receipt by a second device, the request message requesting service information for multicast broadcast services received by the second device; receiving a reply message that identifies at least one multicast broadcast service received by the second device; transmitting a configuration message for receipt by the second device, the configuration message specifying a quality of experience measurement configuration for generating and reporting quality of experience measurements at the second device for the at least one multicast broadcast service; and receiving a reporting message that includes at least one quality of experience measurement based on the quality of experience configuration for the one or more multicast broadcast services.
  • wireless communication at the base station includes any one or combination of: where the service information requested by the request message represents service information for multicast broadcast services received by the second device while the second device is in any one of a radio resource control connected state, a radio resource control idle state, or a radio resource control inactive state; transmitting the request message and the configuration message for receipt by the second device while the second device is in a radio resource control connected state or a radio resource control inactive state; where the quality of experience measurement configuration specified by the configuration message includes a report trigger for the second device to send quality of experience measurements to the first device; where the quality of experience measurement configuration specified by the configuration message includes a maximum size for the reporting message; further including determining that the second device is to transition to a radio resource control inactive state; transmitting a radio resource control release message for receipt by the second device, the radio resource control release message specifying reporting parameters for the second device to report quality of experience measurements for multicast broadcast services received at the second device; and receiving a further reporting message that includes at least one further quality of experience measurement from the
  • wireless communication at the base station includes any one or combination of: where the reporting parameters specify a maximum data volume threshold for the second device to report quality of experience measurements while the second device is in the radio resource control inactive state; further including determining that the second device is to transition to a radio resource control idle state; transmitting a radio resource control release message for receipt by the second device, the radio resource control release message specifying a report trigger for the second device to report quality of experience measurements for multicast broadcast services received at the second device; receiving an indication from the second device of an availability of quality of experience measurements in conjunction with a transition of the second device from the radio resource control idle state to a radio resource control connected state; transmitting a radio resource control reconfiguration message for receipt by the second device, the radio resource control reconfiguration message indicating that the second device is to activate quality of experience reporting; and receiving a further reporting message that includes at least one further quality of experience measurement from the second device while the second device is in the radio resource control connected state; where the report trigger specifies one or more of: that the second device is to initiate reporting
  • wireless communication at the base station includes any one or combination of: further including transmitting, based on to determine that the second device is to transition to the radio resource control idle state, a device context message to a core network element, the device context message including an identifier for the second device, an identifier for the quality of experience reference, the quality of experience measurement configuration for the at least one multicast broadcast service, and the report trigger for the second device to report quality of experience measurements; transmitting, based on the indication that the second device transitions from the radio resource control idle state to the radio resource control connected state, a device context request message to the core network element, the device context request message including the identifier for the second device and a request for quality of experience reporting context associated with the second device; and receiving, from the core network element, a device context response message that includes an identifier for the quality of experience reference, the quality of experience measurement configuration for the at least one multicast broadcast service, and the report trigger for the second device to report quality of experience measurements, where transmitting the radio resource control reconfiguration message is based
  • a base station for wireless communication includes a communications manager and a transceiver configured to cooperatively: transmit a request message for receipt by a second device, the request message requesting service information for multicast broadcast services received by the second device; receive a reply message that identifies at least one multicast broadcast service received by the second device; transmit a configuration message for receipt by the second device, the configuration message specifying a quality of experience measurement configuration for generating and reporting quality of experience measurements at the second device for the at least one multicast broadcast service; and receive a reporting message that includes at least one quality of experience measurement based on the quality of experience configuration for the one or more multicast broadcast services.
  • the base station for wireless communication includes any one or combination of: where the service information requested by the request message represents service information for multicast broadcast services received by the second device while the second device is in any one of a radio resource control connected state, a radio resource control idle state, or a radio resource control inactive state; where the communications manager and the transceiver are further configured to cooperatively transmit the request message and the configuration message for receipt by the second device while the second device is in a radio resource control connected state or a radio resource control inactive state; where the quality of experience measurement configuration specified by the configuration message includes a report trigger for the second device to send quality of experience measurements to the first device; where the quality of experience measurement configuration specified by the configuration message includes a maximum size for the reporting message; where the communications manager and the transceiver are further configured to cooperatively: determine that the second device is to transition to a radio resource control inactive state; transmit a radio resource control release message for receipt by the second device, the radio resource control release message specifying reporting parameters for the second device to report quality of experience measurements for multi
  • the base station for wireless communication includes any one or combination of: where the reporting parameters specify a maximum data volume threshold for the second device to report quality of experience measurements while the second device is in the radio resource control inactive state; where the communications manager and the transceiver are further configured to cooperatively: determine that the second device is to transition to a radio resource control idle state; transmit a radio resource control release message for receipt by the second device, the radio resource control release message specifying a report trigger for the second device to report quality of experience measurements for multicast broadcast services received at the second device; receive an indication from the second device of an availability of quality of experience measurements in conjunction with a transition of the second device from the radio resource control idle state to a radio resource control connected state; transmit a radio resource control reconfiguration message for receipt by the second device, the radio resource control reconfiguration message indicating that the second device is to activate quality of experience reporting; and receive a further reporting message that includes at least one further quality of experience measurement from the second device while the second device is in the radio resource control connected state.
  • the base station for wireless communication includes any one or combination of: where the report trigger specifies one or more of: that the second device is to initiate reporting of quality of experience measurements upon detecting an availability of at least one further quality of experience measurement; or that the second device is to initiate reporting of quality of experience measurements upon detecting an event type that causes the second device to transition from the radio resource control idle state to the radio resource control connected state; where the communications manager and the transceiver are further configured to cooperatively: transmit, based on to determine that the second device is to transition to the radio resource control idle state, a device context message to a core network element, the device context message including an identifier for the second device, an identifier for the quality of experience reference, the quality of experience measurement configuration for the at least one multicast broadcast service, and the report trigger for the second device to report quality of experience measurements; transmit, based on the indication that the second device transitions from the radio resource control idle state to the radio resource control connected state, a device context request message to the core network element, the device context request message including the
  • the processor 1006 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof).
  • the processor 1006 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1006.
  • the processor 1006 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1008) to cause the device 1002 to perform various functions of the present disclosure.
  • the memory 1008 may include random access memory (RAM) and read-only memory (ROM).
  • the memory 1008 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1006 cause the device 1002 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code may not be directly executable by the processor 1006 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 1008 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 1014 may manage input and output signals for the device 1002.
  • the I/O controller 1014 may also manage peripherals not integrated into the device 1002.
  • the I/O controller 1014 may represent a physical connection or port to an external peripheral.
  • the I/O controller 1014 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system.
  • the I/O controller 1014 may be implemented as part of a processor, such as the processor 1006.
  • a user may interact with the device 1002 via the I/O controller 1014 or via hardware components controlled by the RO controller 1014.
  • the device 1002 may include a single antenna 1016. However, in some other implementations, the device 1002 may have more than one antenna 1016, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the receiver 1010 and the transmitter 1012 may communicate bi-directionally, via the one or more antennas 1016, wired, or wireless links as described herein.
  • the receiver 1010 and the transmitter 1012 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1016 for transmission, and to demodulate packets received from the one or more antennas 1016.
  • FIG. 11 illustrates an example of a block diagram 1100 of a device 1102 that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the device 1102 may be an example of a core network 106 component, examples of which are described above with reference to the wireless communications system 100.
  • the device 1102 may support wireless communication with one or more base stations 102, UEs 104, or any combination thereof.
  • the device 1102 may include components for bi-directional communications including components for transmitting and receiving communications, such as a communications manager 1104, a processor 1106, a memory 1108, a receiver 1110, a transmitter 1112, and an VO controller 1114. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).
  • the communications manager 1104, the receiver 1110, the transmitter 1112, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the communications manager 1104, the receiver 1110, the transmitter 1112, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
  • the communications manager 1104, the receiver 1110, the transmitter 1112, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry).
  • the hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 1106 and the memory 1108 coupled with the processor 1106 may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor 1106, instructions stored in the memory 1108).
  • the communications manager 1104, the receiver 1110, the transmitter 1112, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by the processor 1106. If implemented in code executed by the processor 1106, the functions of the communications manager 1104, the receiver 1110, the transmitter 1112, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).
  • code e.g., as communications management software or firmware
  • the functions of the communications manager 1104, the receiver 1110, the transmitter 1112, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in
  • the communications manager 1104 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 1110, the transmitter 1112, or both.
  • the communications manager 1104 may receive information from the receiver 1110, send information to the transmitter 1112, or be integrated in combination with the receiver 1110, the transmitter 1112, or both to receive information, transmit information, or perform various other operations as described herein.
  • the communications manager 1104 is illustrated as a separate component, in some implementations, one or more functions described with reference to the communications manager 1104 may be supported by or performed by the processor 1106, the memory 1108, or any combination thereof.
  • the memory 1108 may store code, which may include instructions executable by the processor 1106 to cause the device 1102 to perform various aspects of the present disclosure as described herein, or the processor 1106 and the memory 1108 may be otherwise configured to perform or support such operations.
  • the communications manager 1104 may support wireless communication at a first device (e.g., a core network 106 component) in accordance with examples as disclosed herein.
  • the communications manager 1104 and/or other device components may be configured as or otherwise support a means for wireless communication at a core network component, including receiving, from a second device, a device context message including an identifier for a user equipment, an identifier for the quality of experience reference, quality of experience measurement configuration for at least one multicast broadcast service, and reporting criteria for the user equipment to report quality of experience measurements; receiving, from a third device, a device context request message including the identifier for the user equipment and a request for quality of experience reporting context associated with the user equipment; and transmitting, for receipt by the third device, a device context response message that includes an identifier for the quality of experience reference, the quality of experience measurement configuration for the at least one multicast broadcast service, and the reporting criteria for the user equipment to report quality of experience measurements.
  • wireless communication at the core network component includes any one or combination of: where the device context message further includes an identifier for an instance of a multicast broadcast service and a report trigger for the user equipment to initiate reporting of quality of experience measurements, and further including generating the device context response to include the identifier for the instance of the multicast broadcast service and the report trigger.
  • a core network component for wireless communication includes a communications manager and a transceiver implemented cooperatively to: receive, from a second device, a device context message including an identifier for a user equipment, an identifier for the quality of experience reference, quality of experience measurement configuration for at least one multicast broadcast service, and reporting criteria for the user equipment to report quality of experience measurements; receive, from a third device, a device context request message including the identifier for the user equipment and a request for quality of experience reporting context associated with the user equipment; and transmit, for receipt by the third device, a device context response message that includes an identifier for the quality of experience reference, the quality of experience measurement configuration for the at least one multicast broadcast service, and the reporting criteria for the user equipment to report quality of experience measurements.
  • the core network component for wireless communication includes any one or combination of: where the device context message further includes an identifier for an instance of a multicast broadcast service and a report trigger for the user equipment to initiate reporting of quality of experience measurements, and where the communications manager is further configured to generate the device context response to include the identifier for the instance of the multicast broadcast service and the report trigger.
  • the processor 1106 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof).
  • the processor 1106 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1106.
  • the processor 1106 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1108) to cause the device 1102 to perform various functions of the present disclosure.
  • the memory 1108 may include random access memory (RAM) and read-only memory (ROM).
  • the memory 1108 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1106 cause the device 1102 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code may not be directly executable by the processor 1106 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 1108 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 1114 may manage input and output signals for the device 1102.
  • the I/O controller 1114 may also manage peripherals not integrated into the device 1102.
  • the I/O controller 1114 may represent a physical connection or port to an external peripheral.
  • the I/O controller 1114 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system.
  • the I/O controller 1114 may be implemented as part of a processor, such as the processor 1106.
  • a user may interact with the device 1102 via the I/O controller 1114 or via hardware components controlled by the I/O controller 1114.
  • the device 1102 may include a single antenna 1116. However, in some other implementations, the device 1102 may have more than one antenna 1116, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the receiver 1110 and the transmitter 1112 may communicate bi-directionally, via the one or more antennas 1116, wired, or wireless links as described herein.
  • the receiver 1110 and the transmitter 1112 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1116 for transmission, and to demodulate packets received from the one or more antennas 1116.
  • FIG. 12 illustrates a flowchart of a method 1200 that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the operations of the method 1200 may be implemented by a device or its components as described herein.
  • the operations of the method 1200 may be performed by a device, such as a UE 104 as described with reference to FIGS. 1 through 11.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving, at a first device, a request message from a second device, the request message requesting service information for multicast broadcast services received by the first device.
  • the operations of 1202 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1202 may be performed by a device as described with reference to FIG. 1.
  • the method may include transmitting a reply message for receipt by the second device, the reply message identifying at least one multicast broadcast service received by the first device.
  • the operations of 1204 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1204 may be performed by a device as described with reference to FIG. 1.
  • the method may include receiving a configuration message, the configuration message specifying a quality of experience measurement configuration for generating and reporting quality of experience measurements at the first device for the at least one multicast broadcast service.
  • the operations of 1206 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1206 may be performed by a device as described with reference to FIG. 1.
  • the method may include transmitting a reporting message for receipt by the second device, the reporting message including at least one quality of experience measurement based on the quality of experience configuration for the at least one multicast broadcast service.
  • the operations of 1208 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1208 may be performed by a device as described with reference to FIG. 1.
  • FIG. 13 illustrates a flowchart of a method 1300 that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the operations of the method 1300 may be implemented by a device or its components as described herein.
  • the operations of the method 1300 may be performed by a device, such as a UE 104 as described with reference to FIGS. 1 through 11.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving at a first device a radio resource control release message from the second device, the radio resource control release message specifying reporting parameters for the first device to report quality of experience measurements for multicast broadcast services received at the first device while the first device is in a radio resource control inactive state.
  • the operations of 1302 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1302 may be performed by a device as described with reference to FIG. 1.
  • the method may include transmitting a further reporting message that includes at least one further quality of experience measurement collected at the first device while the first device is in the radio resource control inactive state.
  • the operations of 1304 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1304 may be performed by a device as described with reference to FIG. 1.
  • FIG. 14 illustrates a flowchart of a method 1400 that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the operations of the method 1400 may be implemented by a device or its components as described herein.
  • the operations of the method 1400 may be performed by a device, such as a UE 104 as described with reference to FIGS. 1 through 11.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving at a first device a radio resource control release message from a second device, the radio resource control release message specifying a report trigger for the first device to initiate reporting of quality of experience measurements for multicast broadcast services received at the first device while the first device is in a radio resource control idle state.
  • the operations of 1402 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1402 may be performed by a device as described with reference to FIG. 1.
  • the method may include receiving an indication that the report trigger occurs while the first device is in the radio resource control idle state.
  • the operations of 1404 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1404 may be performed by a device as described with reference to FIG. 1.
  • the method may include transmitting an indication of an availability of quality of experience measurements in conjunction with a transition of the first device from the radio resource control idle state to a radio resource control connected state.
  • the operations of 1406 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1406 may be performed by a device as described with reference to FIG. 1.
  • the method may include receiving a radio resource control reconfiguration message in conjunction with transitioning from the radio resource control idle state to a radio resource control connected state, the radio resource control reconfiguration message indicating that the second device is to activate quality of experience reporting.
  • the operations of 1408 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1408 may be performed by a device as described with reference to FIG. 1.
  • the method may include transmitting a further reporting message that includes at least one further quality of experience measurement for receipt by the second device.
  • the operations of 1410 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1410 may be performed by a device as described with reference to FIG. 1.
  • FIG. 15 illustrates a flowchart of a method 1500 that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the operations of the method 1500 may be implemented by a device or its components as described herein.
  • the operations of the method 1500 may be performed by a device, such as a base station 102 as described with reference to FIGS. 1 through 11.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include transmitting by a first device a request message for receipt by a second device, the request message requesting service information for multicast broadcast services received by the second device.
  • the operations of 1502 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1502 may be performed by a device as described with reference to FIG. 1.
  • the method may include receiving a reply message that identifies at least one multicast broadcast service received by the second device.
  • the operations of 1504 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1504 may be performed by a device as described with reference to FIG. 1.
  • the method may include transmitting a configuration message for receipt by the second device, the configuration message specifying a quality of experience measurement configuration for generating and reporting quality of experience measurements at the second device for the at least one multicast broadcast service.
  • the operations of 1506 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1506 may be performed by a device as described with reference to FIG. 1.
  • the method may include receiving a reporting message that includes at least one quality of experience measurement based on the quality of experience configuration for the one or more multicast broadcast services.
  • the operations of 1508 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1508 may be performed by a device as described with reference to FIG. 1.
  • FIG. 16 illustrates a flowchart of a method 1600 that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the operations of the method 1600 may be implemented by a device or its components as described herein.
  • the operations of the method 1600 may be performed by a device, such as a base station 102 as described with reference to FIGS. 1 through 11.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include determining at a first device that a second device is to transition to a radio resource control inactive state.
  • the operations of 1602 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1602 may be performed by a device as described with reference to FIG. 1.
  • the method may include transmitting a radio resource control release message for receipt by the second device, the radio resource control release message specifying reporting parameters for the second device to report quality of experience measurements for multicast broadcast services received at the second device.
  • the operations of 1604 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1604 may be performed by a device as described with reference to FIG. 1.
  • the method may include receiving a further reporting message that includes at least one further quality of experience measurement from the second device while the second device is in the radio resource control inactive state.
  • the operations of 1606 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1606 may be performed by a device as described with reference to FIG. 1.
  • FIG. 17 illustrates a flowchart of a method 1700 that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the operations of the method 1700 may be implemented by a device or its components as described herein.
  • the operations of the method 1700 may be performed by a device, such as a base station 102 as described with reference to FIGS. 1 through 11.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include determining at a first device that a second device is to transition to a radio resource control idle state.
  • the operations of 1702 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1702 may be performed by a device as described with reference to FIG. 1.
  • the method may include transmitting a radio resource control release message for receipt by the second device, the radio resource control release message specifying a report trigger for the second device to report quality of experience measurements for multicast broadcast services received at the second device.
  • the operations of 1704 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1704 may be performed by a device as described with reference to FIG. 1.
  • the method may include receiving an indication from the second device of an availability of quality of experience measurements in conjunction with a transition of the second device from the radio resource control idle state to a radio resource control connected state.
  • the operations of 1706 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1706 may be performed by a device as described with reference to FIG. 1.
  • the method may include transmitting a radio resource control reconfiguration message for receipt by the second device, the radio resource control reconfiguration message indicating that the second device is to activate quality of experience reporting.
  • the operations of 1708 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1708 may be performed by a device as described with reference to FIG. 1.
  • the method may include receiving a further reporting message that includes at least one further quality of experience measurement from the second device while the second device is in the radio resource control connected state.
  • the operations of 1710 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1710 may be performed by a device as described with reference to FIG. 1.
  • FIG. 18 illustrates a flowchart of a method 1800 that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the operations of the method 1800 may be implemented by a device or its components as described herein.
  • the operations of the method 1800 may be performed by a device, such as a base station 102 as described with reference to FIGS. 1 through 11.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include transmitting, at a first device and based on to determine that the second device is to transition to the radio resource control idle state, a device context message to a core network element, the device context message including an identifier for the second device, an identifier for the quality of experience reference, the quality of experience measurement configuration for the at least one multicast broadcast service, and the report trigger for the second device to report quality of experience measurements.
  • the operations of 1802 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1802 may be performed by a device as described with reference to FIG. 1.
  • the method may include transmitting, based on the indication that the second device transitions from the radio resource control idle state to the radio resource control connected state, a device context request message to the core network element, the device context request message including the identifier for the second device and a request for quality of experience reporting context associated with the second device.
  • the operations of 1804 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1804 may be performed by a device as described with reference to FIG. 1.
  • the method may include receiving, from the core network element, a device context response message that includes an identifier for the quality of experience reference, the quality of experience measurement configuration for the at least one multicast broadcast service, and the report trigger for the second device to report quality of experience measurements, wherein to transmit the radio resource control reconfiguration message is based on the device context response message.
  • the operations of 1806 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1806 may be performed by a device as described with reference to FIG. 1.
  • FIG. 19 illustrates a flowchart of a method 1900 that supports QoE reporting for MBS in accordance with aspects of the present disclosure.
  • the operations of the method 1900 may be implemented by a device or its components as described herein.
  • the operations of the method 1900 may be performed by a device, such as a component and/or set of components of a core network 106 as described with reference to FIGS. 1 through 11.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving, at a first device from a second device, a device context message including an identifier for a user equipment, an identifier for the quality of experience reference, quality of experience measurement configuration for at least one multicast broadcast service, and reporting criteria for the user equipment to report quality of experience measurements.
  • the operations of 1902 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1902 may be performed by a device as described with reference to FIG. 1.
  • the method may include receiving, from a third device, a device context request message including the identifier for the user equipment and a request for quality of experience reporting context associated with the user equipment.
  • the operations of 1904 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1904 may be performed by a device as described with reference to FIG. 1.
  • the method may include transmitting, for receipt by the third device, a device context response message that includes an identifier for the quality of experience reference, the quality of experience measurement configuration for the at least one multicast broadcast service, and the reporting criteria for the user equipment to report quality of experience measurements.
  • the operations of 1906 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1906 may be performed by a device as described with reference to FIG. 1.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • RAM random access memory
  • ROM read only memory
  • EEPROM electrically erasable programmable ROM
  • CD compact disk
  • magnetic disk storage or other magnetic storage devices or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • any connection may be properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

Landscapes

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

Abstract

Divers aspects de la présente divulgation concernent le rapport de la qualité d'expérience (QoE) pour un service de diffusion/multidiffusion (MBS). Une station de base peut demander à un équipement utilisateur (UE) le MBS qu'il reçoit. L'UE répond en identifiant au moins un MBS, et la station de base et l'UE interagissent pour configurer l'UE afin qu'il rapporte des informations QoE pour le(s) MBS. Différents messages et procédures décrits permettent de configurer un UE pour collecter et rapporter des informations QoE dans différents états de connectivité, tels qu'un état connecté, un état inactif et un état de veille.
PCT/IB2023/050270 2022-01-14 2023-01-12 Rapporte de qualité d'expérience pour des services de diffusion/multidiffusion WO2023135539A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263299648P 2022-01-14 2022-01-14
US63/299,648 2022-01-14

Publications (1)

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

Family

ID=85037065

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2023/050270 WO2023135539A1 (fr) 2022-01-14 2023-01-12 Rapporte de qualité d'expérience pour des services de diffusion/multidiffusion

Country Status (1)

Country Link
WO (1) WO2023135539A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130128756A1 (en) * 2011-11-17 2013-05-23 Qualcomm Incorporated Method and apparatus for physical layer measurements in multicast broadcast multimedia service systems
US20140112236A1 (en) * 2011-05-02 2014-04-24 Pantech Co., Ltd Apparatus and method for transmitting control information for continuous mbms service
WO2018142345A1 (fr) * 2017-02-03 2018-08-09 Telefonaktiebolaget Lm Ericsson (Publ) Collecte de mesures dans des réseaux de communication sans fil
WO2022005361A1 (fr) * 2020-06-30 2022-01-06 Telefonaktiebolaget Lm Ericsson (Publ) Rapport de qualité d'expérience (qoe) pour gestion de qoe à base de ran

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140112236A1 (en) * 2011-05-02 2014-04-24 Pantech Co., Ltd Apparatus and method for transmitting control information for continuous mbms service
US20130128756A1 (en) * 2011-11-17 2013-05-23 Qualcomm Incorporated Method and apparatus for physical layer measurements in multicast broadcast multimedia service systems
WO2018142345A1 (fr) * 2017-02-03 2018-08-09 Telefonaktiebolaget Lm Ericsson (Publ) Collecte de mesures dans des réseaux de communication sans fil
WO2022005361A1 (fr) * 2020-06-30 2022-01-06 Telefonaktiebolaget Lm Ericsson (Publ) Rapport de qualité d'expérience (qoe) pour gestion de qoe à base de ran

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3 Generation Partnership Project; Technical Specification Group Radio Access Network; Study on NR QoE (Quality of Experience) management and optimizations for diverse services (Release 17)", vol. RAN WG3, no. V17.0.0, 9 April 2021 (2021-04-09), pages 1 - 18, XP052000775, Retrieved from the Internet <URL:https://ftp.3gpp.org/Specs/archive/38_series/38.890/38890-h00.zip 38890-h00.docx> [retrieved on 20210409] *

Similar Documents

Publication Publication Date Title
US9775105B2 (en) Optimization on network assisted proximity services discovery management
CN111819879B (zh) 在rrc非活动状态下暂停/恢复测量
KR102571193B1 (ko) D2d 통신 시스템에서 d2d 단말을 위한 사이드링크 그랜트를 선택하는 방법 및 그 장치
JP6084979B2 (ja) 通信端末、方法およびプログラム
US20180035340A1 (en) Base station and user terminal in mobile communication system
JP5770948B2 (ja) 無線接続システムにおいてｍａｃ制御メッセージを放送する方法及び装置
CN106576336B (zh) 配置d2d发现特定的逻辑信道组的方法和装置
US9913218B2 (en) Communications device and methods
US20190394712A1 (en) Network event reporting for pdn connectivity
EP3384716B1 (fr) Mécanisme de radiorecherche pour réseaux sans fil
KR20140050636A (ko) Ｍｔｃ를 위한 감소된 컨텍스트 또는 컨텍스트리스 단문 메시지 송신
US20160037450A1 (en) Infrastructure equipment, mobile communications network and method
KR20140042844A (ko) 무선 통신 시스템에서 멀티캐스트 데이터 수신 방법 및 이를 위한 장치
US20200100212A1 (en) Method and apparatus to support mobility in lwa
WO2023199171A1 (fr) Sélection d&#39;agrégation de porteuses de liaison latérale
CN111937416A (zh) 用于在移动通信系统中提供蜂窝物联网服务的方法和装置
WO2023135539A1 (fr) Rapporte de qualité d&#39;expérience pour des services de diffusion/multidiffusion
JP7227401B2 (ja) 通信制御方法及びユーザ装置
KR20200036705A (ko) 저전력 모드를 사용하는 IoT 단말의 연결성 관리 방법
JP7319474B2 (ja) 通信制御方法
WO2024033832A1 (fr) Collecte de mesures de qualité d&#39;expérience
US20220174775A1 (en) Ue-triggered connection resume with early data transmission and network-triggered connection resume
WO2024069419A1 (fr) Rapport de dispositif utilisateur de mesure de qualité d&#39;expérience pour un service de diffusion par multidiffusion dans un état inactif
WO2023203546A1 (fr) Acquisition d&#39;informations essentielles sur le système par un dispositif à distance de liaison latérale
WO2023199173A1 (fr) Configuration d&#39;agrégation de porteuses de liaison latérale

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: 23701815

Country of ref document: EP

Kind code of ref document: A1