WO2019174588A1 - Amélioration de qualité de service concernant un changement d'humeur basé sur un rapport de consommation - Google Patents

Amélioration de qualité de service concernant un changement d'humeur basé sur un rapport de consommation Download PDF

Info

Publication number
WO2019174588A1
WO2019174588A1 PCT/CN2019/077915 CN2019077915W WO2019174588A1 WO 2019174588 A1 WO2019174588 A1 WO 2019174588A1 CN 2019077915 W CN2019077915 W CN 2019077915W WO 2019174588 A1 WO2019174588 A1 WO 2019174588A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
service
delivery service
data delivery
user
Prior art date
Application number
PCT/CN2019/077915
Other languages
English (en)
Inventor
Jie LING
Wu Wang
Wenhu Tang
Jinyang Xie
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to EP19766501.1A priority Critical patent/EP3766226A4/fr
Publication of WO2019174588A1 publication Critical patent/WO2019174588A1/fr

Links

Images

Classifications

    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0007—Control or signalling for completing the hand-off for multicast or broadcast services, e.g. MBMS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services

Definitions

  • 3GPP MBMS has defined MBMS operation on Demand (MooD) within 3GPP Release 12 (3GPP TS 26.346) .
  • MooD MBMS operation on Demand
  • certain content that is initially delivered over the unicast network may be turned into an MBMS User Service, in order to efficiently use network resources when the traffic volume exceeds a certain threshold.
  • Such dynamic conversion from unicast delivery to MBMS delivery is referred to as “MBMS offloading” . It is also possible to stop MBMS delivery when the traffic volume is lower than another threshold. And then the UEs will switch the consumption from MBMS delivery towards unicast delivery.
  • ⁇ Consumption report-based MooD UEs send consumption reports towards BM-SC for the service consumption together with their location information. Based on the consumption reports, BM-SC may dynamically start or stop MBMS delivery for the service.
  • ⁇ Proxy-based MooD UEs send HTTP/RTSP requests towards a pre-configured MooD proxy server.
  • the MooD proxy server determine the needs of starting the MBMS delivery for a certain service based on the UE location information. Once the MBMS delivery is started, the MooD proxy server redirect the reception to MBMS in the HTTP/RTSP response.
  • the proxy-based MooD solution is more efficient without introducing the addition consumption report traffic. But it can only provide means to start MBMS delivery (i.e. enable UE to switch from unicast delivery to MBMS delivery) . It cannot provide an effective way to stop MBMS delivery based on the UE consumption situation.
  • the consumption report-based MooD solution is able to measure the accurate information about the MooD switching, including both start MBMS delivery and stop MBMS delivery, due to the reason that UE provides the accurate consumption information together with its location information in the consumption report.
  • FIGURE 1 illustrates an example architecture of the consumption report-based MooD.
  • the UE sends the consumption reports information towards the consumption reporting server inside BM-SC, when it starts, stops, transitions, location changes and periodically when consumption a service.
  • BM-SC counts UEs consuming DASH content via unicast when MBMS is not available.
  • the BM-SC triggers the starting of the MBMS delivery.
  • BM-SC counts UEs consumption content via broadcast when MBMS is available.
  • the BM-SC triggers the stopping of the MBMS delivery.
  • BM-SC shall include an Associated Delivery Procedure Description indicates the parameters of a consumption reporting procedure.
  • the ADPD schema is defined as below:
  • the BM-SC specifies the consumption report server URI in the serviceURI element, which can be multiple for service scalability reasons.
  • the BM-SC can specify the percentage subset of MBMS receivers that the BM-SC would like to perform consumption reporting via the samplePercentage attribute.
  • the BM-SC can specify the nominal periodicity by which the UE, when it is continuously consuming the service of concern, shall perform consumption reporting.
  • This periodicity defined as a time duration between consecutive reports, is specified by the reportInterval attribute.
  • the BM-SC can specify whether the UE shall include its current location by serving cell-ID or MBMS SAI when it performs consumption reporting, via the location child element of r12: consumptionReport.
  • the UE shall report its location according to the enumerated value of the location element, i.e., "MBMS SAI” , "CGI” or ECGI” .
  • the BM-SC can specify whether the UE shall include, in the consumption report message, the clientId attribute which represents the unique identifier for the receiver, e.g. an MSISDN of the UE.
  • UE Based on the instructions in the ADPD for consumption report from BM-SC, UE shall send the consumption report to BM-SC as defined in serviceURI element.
  • the schema of the consumption report is defined as below:
  • the MBMS User Service identification is included in serviceId attribute.
  • the UE identification is included in clientId attribute.
  • the reportTime attribute reflects the time when the consumption report is generated.
  • the location attribute represents the UE location information by CGI, ECGI or the list of MBMS SAI (s) .
  • the consumptionType attribute declares the conditions for consumption reporting:
  • BM-SC can get the UE location information and consumption information for the specific service.
  • BM-SC can start MBMS delivery based on the number of UEs within certain area who are consuming the specific service.
  • BM-SC can stop MBMS delivery based on number of UEs within certain area who are consuming the specific service via broadcast.
  • BM-SC will not be able to determine the quality of the consumption on UE side.
  • BM-SC can start the MBMS delivery for this service, it can offload the radio network more effectively. And those UEs can consume the service via MBMS which provides much better user experience.
  • BM-SC should terminate the MBMS delivery, so that the UEs could consume the service via unicast.
  • unicast would be better than MBMS even if it is less efficient.
  • BM-SC is not able to decide to start or stop MBMS delivery based on the quality of services on UE side.
  • the quality of service information is introduced in the consumption report so that the UE can report the quality of service information towards BM-SC. Based on such information, BM-SC can decide to start or stop MBMS delivery to optimize end user experience.
  • a method performed by a wireless device includes receiving, via a first data delivery service, data associated with a user service; determining quality of service information associated with the data delivered via the first data delivery service; transmitting, to a network node, a first data consumption report that includes the quality of service information associated with the data delivered via the first data delivery service; and in response to transmitting the first data consumption report, receiving, via a second data delivery service, data associated with the user service.
  • a wireless device comprises memory operable to store instructions and processing circuitry operable to execute the instructions to cause the wireless device to receive, via a first data delivery service, data associated with a user service; determine quality of service information associated with the data delivered via the first data delivery service; transmit, to a network node, a first data consumption report that includes the quality of service information associated with the data delivered via the first data delivery service; and in response to transmitting the first data consumption report, receive, via a second data delivery service, data associated with the user service.
  • a method in a network node includes transmitting, via a first data delivery service, data associated with a user service to a wireless device; receiving, from the wireless device, a first data consumption report that includes quality of service information associated with the data delivered via the first data delivery service; based on the quality of service information from the wireless device, switching from the first data delivery service to a second data delivery service; and transmitting, via the second data delivery service, additional data associated with the user service.
  • a network node comprises memory operable to store instructions and processing circuitry operable to execute the instructions to cause the network node to transmit, via a first data delivery service, data associated with a user service to a wireless device; receive, from the wireless device, a first data consumption report that includes quality of service information associated with the data delivered via the first data delivery service; based on the quality of service information from the wireless device, switch from the first data delivery service to a second data delivery service; and transmit, via the second data delivery service, additional data associated with the user service.
  • Certain embodiments may provide one or more of the following technical advantage (s) .
  • the benefit of the invention is that BM-SC can start or stop MBMS delivery based on the quality of experience in UE side to improve end user experience.
  • FIGURE 1 illustrates an example architecture of the consumption report-based MooD
  • FIGURE 2 illustrates an example workflow of triggering MBMS delivery based on bad user experience on UE, according to certain embodiments
  • FIGURE 3 illustrates an example workflow of stopping MBMS delivery based on bad user experience on UE, according to certain embodiments
  • FIGURES 4A-4C illustrate an example wireless network, according to certain embodiments.
  • FIGURE 5 illustrates one embodiment of a UE, according to certain embodiments
  • FIGURES 6A-6B illustrate a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments
  • FIGURE 7 illustrates a telecommunication network connected via an intermediate network to a host computer, according to certain embodiments
  • FIGURE 8 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments
  • FIGURE 9 illustrates a method implemented in a communication system, according to certain embodiments.
  • FIGURE 10 illustrates another method implemented in a communication system, according to certain embodiments.
  • FIGURE 11 illustrates yet another method implemented in a communication system, according to certain embodiments.
  • FIGURE 12 illustrating still another method implemented in a communication system, according to certain embodiments.
  • FIGURE 13 illustrates a method by a wireless device, according to certain embodiments
  • FIGURE 14 illustrates a schematic block diagram of an apparatus in a wireless network, according to certain embodiments.
  • FIGURE 15 depicts a method by a network node, according to certain embodiments.
  • FIGURE 16 illustrates a schematic block diagram of an apparatus in a wireless network, according to certain embodiments.
  • FIGURE 17 illustrate a table defining metrics derived by the MBMS client implementing QoE, according to certain embodiments
  • FIGURE 18 illustrates the nodes and leaf objects contained under the 3GPP_MBMS MooD MO, according to certain embodiments
  • FIGURE 19 illustrates a table comprising semantics of metrics elements, according to certain embodiments.
  • FIGURE 20 illustrates a table that includes DASH-Metrics client reference model, according to certain embodiments
  • FIGURE 21 illustrates a table that includes the metric defining the list of TCP connections, according to certain embodiments
  • FIGURE 22 illustrates a table that includes the metric defining the List of HTTP Request/Response Transactions, according to certain embodiments
  • FIGURE 23 illustrate a table defining the metric for Representation switch events, according to certain embodiments.
  • FIGURE 24 illustrates a table defining the metric for buffer level status events, according to certain embodiments.
  • FIGURES 25A-B illustrate a table defining play list event metrics, according to certain embodiments.
  • an existing Quality-of-Experience (QoE) metric defined for reception report ( “Loss of Objects” ) may be utilized to make the measurement for consumption report (see 3GPP TS 26.346) .
  • DASH-Metrics may be utilized to make the measurement for consumption report (see ISO/IEC 23009-1) .
  • many metrics may be used to monitor the service quality. Some example metrics include:
  • the throughput trace for HTTP request/response transactions could be used to monitor whether the throughput is sufficient for the DASH segment retrieval.
  • the buffer level could be used to monitor whether the buffer on the media player is under-run.
  • the UE may report the “Loss of Objects” in the consumption report when it is consuming the service over MBMS. According to certain other embodiments, the UE may report the “rebuffering” in the consumption report when it is consuming the service over unicast.
  • QoE metrics may also be introduced to further improve the measurement algorithm. The two indications described above are used merely as an example.
  • BM-SC could enhance ADPD for consumption report to provide such indication.
  • ADPD schema update by introducing unicastQoEMetrics and mbmsQoEMetrics:
  • BM-SC requests UEs to report Object_Loss information when consuming service over MBMS and time of rebuffering when consuming service over unicast.
  • BM-SC To gather the information from the DASH QoE metrics reports, it could also be essential for BM-SC to include the DASHQoEProcedure element in ADPD.
  • the consumption report schema can be updated as below:
  • the rebufferingEvents attribute indicates the number of rebuffering events during the last consumption report period.
  • the numberOfLostObjects and numberOfReceivedObjects indicate the number of lost files and received files during the last consumption report period.
  • FIGURE 2 illustrates an example workflow of triggering MBMS delivery based on bad user experience on UE. The steps of the depicted figure may be described as follows:
  • UE start the consumption of the service via unicast, when it detects the MBMS is not available
  • UE send a consumption report towards BM-SC to indicate it starts consumption over unicast. At this time, no measurement statistics available.
  • unicastQoEMetrics includes Rebuffering_Events
  • UE needs to measure number of rebuffering happens in unicast. Such information may be collected from DASH QoE reports
  • UE sends a consumption report towards BM-SC to indicate and on-going consumption over unicast, together with the number of rebuffering during this period.
  • BM-SC could get the QoE information of this UE.
  • BM-SC may decide to start MBMS to improve the user experience.
  • BM-SC delivers the service over MBMS to UE
  • UE detects the service available on MBMS, it switches to MBMS to consume the service
  • UE sends consumption report towards BM-SC to indicate it transit the consumption from unicast to MBMS together with the rebuffering times since the last consumption report
  • UE needs to measure object loss information in MBMS. Such information may be collected from reception reports.
  • UE When the report interval reaches, UE sends a consumption report towards BM-SC to indicate and on-going consumption over MBMS, together with the number of received objects as well as the number of loss objects.
  • FIGURE 3 illustrates the workflow of stopping MBMS delivery based on bad user experience on UE. The steps of the depicted figure may be described as follows:
  • BM-SC delivers the service over MBMS.
  • UE start the consumption of the service via MBMS, when it detects the MBMS is available
  • UE send a consumption report towards BM-SC to indicate it starts consumption over MBMS. At this time, no measurement statistics available.
  • UE needs to measure object loss information in MBMS. Such information may be collected from reception reports.
  • UE sends a consumption report towards BM-SC to indicate and on-going consumption over MBMS, together with the number of received objects as well as the number of loss objects.
  • BM-SC could get the QoE information of this UE.
  • BM-SC may decide to stop MBMS to improve the user experience.
  • UE sends consumption report towards BM-SC to indicate it transit the consumption from MBMS to unicast together the number of received objects as well as the number of loss objects.
  • unicastQoEMetrics includes Rebuffering_Events
  • UE needs to measure number of rebuffering happens in unicast. Such information may be collected from DASH QoE reports
  • UE When the report interval reaches, UE sends a consumption report towards BM-SC to indicate and on-going consumption over unicast, together with the number of rebuffering during this period.
  • the consumption report mechanism is enhanced to enable UE (s) to report QoE metrics information towards BM-SC, including both over unicast and over MBMS. Based on such information, BM-SC is able to decide to start or stop MBMS delivery to improve the user experience.
  • Rebuffering_events may be applicable on both unicast and MBMS. It may be possible to measure the QoE from other aspects, e.g. throughput, or the media player’s buffer.
  • FIGURES 4A-4C illustrate an example wireless network, according to certain embodiments.
  • the wireless network only depicts network 406, network nodes 460 and 460b, and WDs 410a and 410b.
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • wireless device (WD) 410 and network node 460 are depicted with additional detail in FIGURES 4A and 4B, respectively.
  • the wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM) , Universal Mobile Telecommunications System (UMTS) , Long Term Evolution (LTE) , and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax) , Bluetooth, Z-Wave and/or ZigBee standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z-Wave and/or ZigBe
  • Network 406 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs) , packet data networks, optical networks, wide-area networks (WANs) , local area networks (LANs) , wireless local area networks (WLANs) , wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks
  • wireless networks metropolitan area networks
  • Network node 460 and WD 410 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points) , base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs) ) .
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs) , sometimes referred to as Remote Radio Heads (RRHs) .
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS) .
  • DAS distributed antenna system
  • network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs) , base transceiver stations (BTSs) , transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs) , core network nodes (e.g., MSCs, MMEs) , O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs) , and/or MDTs.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes
  • SON nodes e.g., SON nodes
  • positioning nodes e.g.
  • network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node 460 includes processing circuitry 470, device readable medium 480, interface 490, auxiliary equipment 484, power source 486, power circuitry 487, and antenna 462.
  • network node 460 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • network node 460 may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 480 may comprise multiple separate hard drives as well as multiple RAM modules) .
  • network node 460 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc. ) , which may each have their own respective components.
  • network node 460 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeB’s.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node 460 may be configured to support multiple radio access technologies (RATs) .
  • RATs radio access technologies
  • Network node 460 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 460, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 460.
  • Processing circuitry 470 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 470 may include processing information obtained by processing circuitry 470 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 470 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Processing circuitry 470 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 460 components, such as device readable medium 480, network node 460 functionality.
  • processing circuitry 470 may execute instructions stored in device readable medium 480 or in memory within processing circuitry 470. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 470 may include a system on a chip (SOC) .
  • SOC system on a chip
  • processing circuitry 470 may include one or more of radio frequency (RF) transceiver circuitry 472 and baseband processing circuitry 474.
  • radio frequency (RF) transceiver circuitry 472 and baseband processing circuitry 474 may be on separate chips (or sets of chips) , boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry 472 and baseband processing circuitry 474 may be on the same chip or set of chips, boards, or units
  • processing circuitry 470 executing instructions stored on device readable medium 480 or memory within processing circuitry 470.
  • some or all of the functionality may be provided by processing circuitry 470 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry 470 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 470 alone or to other components of network node 460, but are enjoyed by network node 460 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium 480 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM) , read-only memory (ROM) , mass storage media (for example, a hard disk) , removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD) ) , and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 470.
  • volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM) , read-only memory (ROM) , mass storage media (for example, a hard disk) , removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital
  • Device readable medium 480 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 470 and, utilized by network node 460.
  • Device readable medium 480 may be used to store any calculations made by processing circuitry 470 and/or any data received via interface 490.
  • processing circuitry 470 and device readable medium 480 may be considered to be integrated.
  • Interface 490 is used in the wired or wireless communication of signalling and/or data between network node 460, network 406, and/or WDs 410. As illustrated, interface 490 comprises port (s) /terminal (s) 494 to send and receive data, for example to and from network 406 over a wired connection. Interface 490 also includes radio front end circuitry 492 that may be coupled to, or in certain embodiments a part of, antenna 462. Radio front end circuitry 492 comprises filters 498 and amplifiers 496. Radio front end circuitry 492 may be connected to antenna 462 and processing circuitry 470. Radio front end circuitry may be configured to condition signals communicated between antenna 462 and processing circuitry 470.
  • Radio front end circuitry 492 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 492 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 498 and/or amplifiers 496. The radio signal may then be transmitted via antenna 462. Similarly, when receiving data, antenna 462 may collect radio signals which are then converted into digital data by radio front end circuitry 492. The digital data may be passed to processing circuitry 470. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • network node 460 may not include separate radio front end circuitry 492, instead, processing circuitry 470 may comprise radio front end circuitry and may be connected to antenna 462 without separate radio front end circuitry 492. Similarly, in some embodiments, all or some of RF transceiver circuitry 472 may be considered a part of interface 490. In still other embodiments, interface 490 may include one or more ports or terminals 494, radio front end circuitry 492, and RF transceiver circuitry 472, as part of a radio unit (not shown) , and interface 490 may communicate with baseband processing circuitry 474, which is part of a digital unit (not shown) .
  • Antenna 462 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 462 may be coupled to radio front end circuitry 490 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • antenna 462 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz.
  • An omni-directional antenna may be used to transmit/receive radio signals in any direction
  • a sector antenna may be used to transmit/receive radio signals from devices within a particular area
  • a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line.
  • the use of more than one antenna may be referred to as MIMO.
  • antenna 462 may be separate from network node 460 and may be connectable to network node 460 through an interface or port.
  • Antenna 462, interface 490, and/or processing circuitry 470 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 462, interface 490, and/or processing circuitry 470 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry 487 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 460 with power for performing the functionality described herein. Power circuitry 487 may receive power from power source 486. Power source 486 and/or power circuitry 487 may be configured to provide power to the various components of network node 460 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component) . Power source 486 may either be included in, or external to, power circuitry 487 and/or network node 460.
  • network node 460 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 487.
  • power source 486 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 487. The battery may provide backup power should the external power source fail.
  • Other types of power sources such as photovoltaic devices, may also be used.
  • network node 460 may include additional components beyond those shown in Figure 400 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • network node 460 may include user interface equipment to allow input of information into network node 460 and to allow output of information from network node 460. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 460.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • the term WD may be used interchangeably herein with user equipment (UE) .
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD may be configured to transmit and/or receive information without direct human interaction.
  • a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA) , a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE) , a laptop-mounted equipment (LME) , a smart device, a wireless customer-premise equipment (CPE) . a vehicle-mounted wireless terminal device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • a wireless cameras a gaming console or device
  • a gaming console or device a music storage device
  • a playback appliance a wearable terminal device
  • a wireless endpoint a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE)
  • a WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V) , vehicle-to-infrastructure (V2I) , vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc. ) personal wearables (e.g., watches, fitness trackers, etc. ) .
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • FIGURE 4B illustrates an example wireless device 410 that includes antenna 411, interface 414, processing circuitry 420, device readable medium 430, user interface equipment 432, auxiliary equipment 434, power source 436 and power circuitry 437.
  • WD 410 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 410, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 410.
  • Antenna 411 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 414. In certain alternative embodiments, antenna 411 may be separate from WD 410 and be connectable to WD 410 through an interface or port. Antenna 411, interface 414, and/or processing circuitry 420 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 411 may be considered an interface.
  • interface 414 comprises radio front end circuitry 412 and antenna 411.
  • Radio front end circuitry 412 comprise one or more filters 418 and amplifiers 416.
  • Radio front end circuitry 414 is connected to antenna 411 and processing circuitry 420, and is configured to condition signals communicated between antenna 411 and processing circuitry 420.
  • Radio front end circuitry 412 may be coupled to or a part of antenna 411.
  • WD 410 may not include separate radio front end circuitry 412; rather, processing circuitry 420 may comprise radio front end circuitry and may be connected to antenna 411.
  • some or all of RF transceiver circuitry 422 may be considered a part of interface 414.
  • Radio front end circuitry 412 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 412 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 418 and/or amplifiers 416. The radio signal may then be transmitted via antenna 411. Similarly, when receiving data, antenna 411 may collect radio signals which are then converted into digital data by radio front end circuitry 412. The digital data may be passed to processing circuitry 420. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • Processing circuitry 420 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 410 components, such as device readable medium 430, WD 410 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 420 may execute instructions stored in device readable medium 430 or in memory within processing circuitry 420 to provide the functionality disclosed herein.
  • processing circuitry 420 includes one or more of RF transceiver circuitry 422, baseband processing circuitry 424, and application processing circuitry 426.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry 420 of WD 410 may comprise a SOC.
  • RF transceiver circuitry 422, baseband processing circuitry 424, and application processing circuitry 426 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry 424 and application processing circuitry 426 may be combined into one chip or set of chips, and RF transceiver circuitry 422 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 422 and baseband processing circuitry 424 may be on the same chip or set of chips, and application processing circuitry 426 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 422, baseband processing circuitry 424, and application processing circuitry 426 may be combined in the same chip or set of chips.
  • RF transceiver circuitry 422 may be a part of interface 414.
  • RF transceiver circuitry 422 may condition RF signals for processing circuitry 420.
  • processing circuitry 420 executing instructions stored on device readable medium 430, which in certain embodiments may be a computer-readable storage medium.
  • some or all of the functionality may be provided by processing circuitry 420 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry 420 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 420 alone or to other components of WD 410, but are enjoyed by WD 410 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry 420 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 420, may include processing information obtained by processing circuitry 420 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 410, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 420 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 410, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Device readable medium 430 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 420.
  • Device readable medium 430 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM) ) , mass storage media (e.g., a hard disk) , removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD) ) , and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 420.
  • processing circuitry 420 and device readable medium 430 may be considered to be integrated.
  • User interface equipment 432 may provide components that allow for a human user to interact with WD 410. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 432 may be operable to produce output to the user and to allow the user to provide input to WD 410. The type of interaction may vary depending on the type of user interface equipment 432 installed in WD 410. For example, if WD 410 is a smart phone, the interaction may be via a touch screen; if WD 410 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected) .
  • usage e.g., the number of gallons used
  • a speaker that provides an audible alert
  • User interface equipment 432 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 432 is configured to allow input of information into WD 410, and is connected to processing circuitry 420 to allow processing circuitry 420 to process the input information. User interface equipment 432 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 432 is also configured to allow output of information from WD 410, and to allow processing circuitry 420 to output information from WD 410. User interface equipment 432 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 432, WD 410 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • Auxiliary equipment 434 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 434 may vary depending on the embodiment and/or scenario.
  • Power source 436 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet) , photovoltaic devices or power cells, may also be used.
  • WD 410 may further comprise power circuitry 437 for delivering power from power source 436 to the various parts of WD 410 which need power from power source 436 to carry out any functionality described or indicated herein.
  • Power circuitry 437 may in certain embodiments comprise power management circuitry.
  • Power circuitry 437 may additionally or alternatively be operable to receive power from an external power source; in which case WD 410 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • Power circuitry 437 may also in certain embodiments be operable to deliver power from an external power source to power source 436. This may be, for example, for the charging of power source 436. Power circuitry 437 may perform any formatting, converting, or other modification to the power from power source 436 to make the power suitable for the respective components of WD 410 to which power is supplied.
  • FIGURE 5 illustrates one embodiment of a UE in accordance with various aspects described herein.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller) .
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter) .
  • UE 500 may be any UE identified by the 3 rd Generation Partnership Project (3GPP) , including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE 500 as illustrated in FIGURE 5, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3 rd Generation Partnership Project (3GPP) , such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3 rd Generation Partnership Project
  • 3GPP 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • the term WD and UE may be used interchangeable. Accordingly, although FIGURE 5 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.
  • UE 500 includes processing circuitry 501 that is operatively coupled to input/output interface 505, radio frequency (RF) interface 509, network connection interface 511, memory 515 including random access memory (RAM) 517, read-only memory (ROM) QQ219, and storage medium 521 or the like, communication subsystem 531, power source 533, and/or any other component, or any combination thereof.
  • Storage medium 521 includes operating system 523, application program 525, and data QQ227. In other embodiments, storage medium 521 may include other similar types of information.
  • Certain UEs may utilize all of the components shown in FIGURE 5, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • processing circuitry 501 may be configured to process computer instructions and data.
  • Processing circuitry 501 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc. ) ; programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP) , together with appropriate software; or any combination of the above.
  • the processing circuitry 501 may include two central processing units (CPUs) . Data may be information in a form suitable for use by a computer.
  • input/output interface 505 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE 500 may be configured to use an output device via input/output interface 505.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from UE 500.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • UE 500 may be configured to use an input device via input/output interface 505 to allow a user to capture information into UE 500.
  • the input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc. ) , a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface 509 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface 511 may be configured to provide a communication interface to network 543a.
  • Network 543a may encompass wired and/or wireless networks such as a local-area network (LAN) , a wide-area network (WAN) , a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • LAN local-area network
  • WAN wide-area network
  • network 543a may comprise a Wi-Fi network.
  • Network connection interface 511 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface 511 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like) .
  • the transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
  • RAM 517 may be configured to interface via bus 502 to processing circuitry 501 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM QQ219 may be configured to provide computer instructions or data to processing circuitry 501.
  • ROM QQ219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O) , startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • Storage medium 521 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM) , erasable programmable read-only memory (EPROM) , electrically erasable programmable read-only memory (EEPROM) , magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium 521 may be configured to include operating system 523, application program 525 such as a web browser application, a widget or gadget engine or another application, and data file QQ227.
  • Storage medium 521 may store, for use by UE 500, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium 521 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID) , floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM) , synchronous dynamic random access memory (SDRAM) , external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SIM/RUIM removable user identity
  • Storage medium 521 may allow UE 500 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 521, which may comprise a device readable medium.
  • processing circuitry 501 may be configured to communicate with network 543b using communication subsystem 531.
  • Network 543a and network 543b may be the same network or networks or different network or networks.
  • Communication subsystem 531 may be configured to include one or more transceivers used to communicate with network 543b.
  • communication subsystem 531 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802. QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver may include transmitter 533 and/or receiver 535 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like) . Further, transmitter 533 and receiver 535 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem 531 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • communication subsystem 531 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network 543b may encompass wired and/or wireless networks such as a local-area network (LAN) , a wide-area network (WAN) , a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 543b may be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source 513 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 500.
  • communication subsystem 531 may be configured to include any of the components described herein.
  • processing circuitry 501 may be configured to communicate with any of such components over bus 502.
  • any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 501 perform the corresponding functions described herein.
  • the functionality of any of such components may be partitioned between processing circuitry 501 and communication subsystem 531.
  • the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
  • FIGURES 6A-6B are schematic block diagrams illustrating a virtualization environment 600 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks) .
  • a node e.g., a virtualized base station or a virtualized radio access node
  • a device e.g., a UE, a wireless device or any other type of communication device
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 600 hosted by one or more of hardware nodes 630. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node) , then the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications 620 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc. ) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications 620 are run in virtualization environment 600 which provides hardware 630 comprising processing circuitry 660 and memory 690.
  • Memory 690 contains instructions 695 executable by processing circuitry 660 whereby application 620 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment 600 comprises general-purpose or special-purpose network hardware devices 630 comprising a set of one or more processors or processing circuitry 660, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs) , or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • processors or processing circuitry 660 may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs) , or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device may comprise memory 690-1 which may be non-persistent memory for temporarily storing instructions 695 or software executed by processing circuitry 660.
  • Each hardware device may comprise one or more network interface controllers (NICs) 670, also known as network interface cards, which include physical network interface 680.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine-readable storage media 690-2 having stored therein software 695 and/or instructions executable by processing circuitry 660.
  • Software 695 may include any type of software including software for instantiating one or more virtualization layers 650 (also referred to as hypervisors) , software to execute virtual machines 640 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines 640 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 650 or hypervisor. Different embodiments of the instance of virtual appliance 620 may be implemented on one or more of virtual machines 640, and the implementations may be made in different ways.
  • processing circuitry 660 executes software 695 to instantiate the hypervisor or virtualization layer 650, which may sometimes be referred to as a virtual machine monitor (VMM) .
  • Virtualization layer 650 may present a virtual operating platform that appears like networking hardware to virtual machine 640.
  • hardware 630 may be a standalone network node with generic or specific components. Hardware 630 may comprise antenna 625 and may implement some functions via virtualization. Alternatively, hardware 630 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE) ) where many hardware nodes work together and are managed via management and orchestration (MANO) 605, which, among others, oversees lifecycle management of applications 620.
  • CPE customer premise equipment
  • MANO management and orchestration
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • virtual machine 640 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of virtual machines 640, and that part of hardware 630 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 640, forms a separate virtual network elements (VNE) .
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units 610 that each include one or more transmitters 610-2 and one or more receivers 610-1 may be coupled to one or more antennas 625. Radio units 610 may communicate directly with hardware nodes 630 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • control system 607 which may alternatively be used for communication between the hardware nodes 630 and radio units 610.
  • FIGURE 7 schematically illustrates a telecommunication network connected via an intermediate network to a host computer, according to certain embodiments.
  • a communication system includes a telecommunication network 3210, such as a 3GPP-type cellular network, which comprises an access network 3211, such as a radio access network, and a core network 3214.
  • the access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 3213a, 3213b, 3213c.
  • Each base station 3212a, 3212b, 3212c is connectable to the core network 3214 over a wired or wireless connection 3215.
  • a first user equipment (UE) 3291 located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c.
  • a second UE 3292 in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. While a plurality of UEs 3291, 3292 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212.
  • the telecommunication network 3210 is itself connected to a host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 3221, 3222 between the telecommunication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may go via an optional intermediate network 3220.
  • the intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 3220, if any, may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more sub-networks (not shown) .
  • the communication system of FIGURE 7 as a whole enables connectivity between one of the connected UEs 3291, 3292 and the host computer 3230.
  • the connectivity may be described as an over-the-top (OTT) connection 3250.
  • the host computer 3230 and the connected UEs 3291, 3292 are configured to communicate data and/or signaling via the OTT connection 3250, using the access network 3211, the core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection 3250 may be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of routing of uplink and downlink communications.
  • a base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, the base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.
  • FIGURE 8 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments.
  • Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIGURE 8.
  • a host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 3300.
  • the host computer 3310 further comprises processing circuitry 3318, which may have storage and/or processing capabilities.
  • the processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the host computer 3310 further comprises software 3311, which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318.
  • the software 3311 includes a host application 3312.
  • the host application 3312 may be operable to provide a service to a remote user, such as a UE 3330 connecting via an OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the remote user, the host application 3312 may provide user data which is transmitted using the OTT connection 3350.
  • the communication system 3300 further includes a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330.
  • the hardware 3325 may include a communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 3300, as well as a radio interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in FIGURE 8) served by the base station 3320.
  • the communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310.
  • connection 3360 may be direct or it may pass through a core network (not shown in FIGURE 8) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the base station 3320 further has software 3321 stored internally or accessible via an external connection.
  • the communication system 3300 further includes the UE 3330 already referred to.Its hardware 3335 may include a radio interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located.
  • the hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the UE 3330 further comprises software 3331, which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338.
  • the software 3331 includes a client application 3332.
  • the client application 3332 may be operable to provide a service to a human or non-human user via the UE 3330, with the support of the host computer 3310.
  • an executing host application 3312 may communicate with the executing client application 3332 via the OTT connection 3350 terminating at the UE 3330 and the host computer 3310.
  • the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data.
  • the OTT connection 3350 may transfer both the request data and the user data.
  • the client application 3332 may interact with the user to generate the user data that it provides.
  • the host computer 3310, base station 3320 and UE 3330 illustrated in FIGURE 8 may be identical to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291, 3292 of FIGURE 7, respectively.
  • the inner workings of these entities may be as shown in FIGURE 8 and independently, the surrounding network topology may be that of FIGURE 7.
  • the OTT connection 3350 has been drawn abstractly to illustrate the communication between the host computer 3310 and the use equipment 3330 via the base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the UE 3330 or from the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network) .
  • the wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate and/or latency and thereby provide benefits such as reduced user waiting time and/or better responsiveness.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311, 3331 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating the host computer’s 3310 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 3311, 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while it monitors propagation times, errors etc.
  • FIGURE 9 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 7 and 8. For simplicity of the present disclosure, only drawing references to FIGURE 9 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE executes a client application associated with the host application executed by the host computer.
  • FIGURE 10 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 7 and 8. For simplicity of the present disclosure, only drawing references to FIGURE 10 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE receives the user data carried in the transmission.
  • FIGURE 11 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 7 and 8. For simplicity of the present disclosure, only drawing references to FIGURE 11 will be included in this section.
  • the UE receives input data provided by the host computer.
  • the UE provides user data.
  • the UE provides the user data by executing a client application.
  • the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in an optional third substep 3630, transmission of the user data to the host computer.
  • the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIGURE 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 7 and 8. For simplicity of the present disclosure, only drawing references to FIGURE 12 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • FIGURE 13 depicts a method by a wireless device, in accordance with particular embodiments.
  • the method begins at step 1302 when the wireless device receives, via a first data delivery service, data associated with a user service.
  • the wireless device determines quality of service information associated with the data delivered via the first data delivery service.
  • the wireless device transmits, to a network node, a first data consumption report that includes the quality of service information associated with the data delivered via the first data delivery service, at step 1306.
  • the wireless device receives, via a second data delivery service, data associated with the user service.
  • FIGURE 14 illustrates a schematic block diagram of an apparatus 1400 in a wireless network (for example, the wireless network shown in FIGURES 4A-4C) .
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 410 or network node 460 shown in FIGURES 4A-4C) .
  • Apparatus WW00 is operable to carry out the example method described with reference to FIGURE 13 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 13 is not necessarily carried out solely by apparatus 1400. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1400 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs) , special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM) , random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause first receiving unit 1402, determining unit 1404, transmitting unit 1406, and second receiving unit 1408, and any other suitable units of apparatus 1400 to perform corresponding functions according one or more embodiments of the present disclosure.
  • apparatus 1400 includes first receiving unit 1402, determining unit 1404, transmitting unit 1406, and second receiving unit 1408.
  • First receiving unit 1402 is configured to receive, via a first data delivery service, data associated with a user service.
  • Determining unit 1404 is configured to determine quality of service information associated with the data delivered via the first data delivery service.
  • Transmitting unit 1406 is configured to transmit, to a network node, a first data consumption report that includes the quality of service information associated with the data delivered via the first data delivery service.
  • Second receiving unit 1408 is configured to receive, via a second data delivery service, data associated with the user service.
  • FIGURE 15 depicts a method 1500 by a network node, in accordance with particular embodiments.
  • the method begins at step 1502 when the network node transmits, via a first data delivery service, data associated with a user service to a wireless device.
  • the network node receives, from the wireless device, a first data consumption report that includes quality of service information associated with the data delivered via the first data delivery service.
  • the network node switches from the first data delivery service to a second data delivery service based on the quality of service information from the wireless device.
  • the network node transmits, via the second data delivery service, additional data
  • FIGURE 16 illustrates a schematic block diagram of an apparatus 1600 in a wireless network (for example, the wireless network shown in FIGURES 4A-4C) .
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 410 or network node 460 shown in FIGURES 4A-4C) .
  • Apparatus 1600 is operable to carry out the example method described with reference to FIGURE 15 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 15 is not necessarily carried out solely by apparatus 1600. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1600 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs) , special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM) , random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause first transmitting unit 1602, receiving unit 1604, switching unit 1606, and second transmitting unit 1608, and any other suitable units of apparatus 1600 to perform corresponding functions according one or more embodiments of the present disclosure.
  • apparatus 1600 includes first transmitting unit 1602, receiving unit 1604, switching unit 1606, and second transmitting unit 1608.
  • First transmitting unit 1602 is configured to transmit, via a first data delivery service, data associated with a user service to a wireless device.
  • Receiving unit 1604 is configured to receive, from the wireless device, a first data consumption report that includes quality of service information associated with the data delivered via the first data delivery service.
  • Switching unit 1606 is configured to switch from the first data delivery service to a second data delivery service based on the quality of service information from the wireless device.
  • Second transmitting unit 1608 is configured to transmit, via the second data delivery service, additional data associated with the user service.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • the MBMS Quality of Experience (QoE) metrics feature is optional for both MBMS streaming server and MBMS client, and shall not disturb the MBMS service.
  • An MBMS Server that supports the QoE metrics feature shall activate the gathering of client QoE metrics with SDP as described in sub-clauses 8.3.2.1 and 8.4.2 and via the reception reporting procedure as described in sub-clause 9.4. Alternatively QoE activation can be done with OMA-DM as described in sub-clause 8.3.2.2.
  • An MBMS client supporting the feature shall perform the quality measurements in accordance to the measurement definitions, aggregate them into client QoE metrics and report the metrics to the specified server using the content reception reporting procedure. The way the QoE metrics are processed and made available is out of the scope of the present document.
  • An MBMS client should measure the metrics at the transport layer after FEC decoding (if FEC is used) , but may also do it at the application layer for better accuracy.
  • the measurement period for the metrics is the whole streaming duration and the measurement resolution of each reported metrics value is defined by the "Measure-Resolution" field.
  • the measurement period may be less than the session duration, because of late joiners or early leavers.
  • the measurement period shall not include any voluntary event that impacts the actual play, such as pause, or any buffering or freezes/gaps caused by them.
  • the metrics shown in Table 8.4.2, as illustrated in FIGURE 17, shall be derived by the MBMS client implementing QoE.
  • All media metrics are only applicable to at least one of audio, video, speech and timed text media types, and are not applicable to other media types such as synthetic audio, still images, bitmap graphics, vector graphics, and text.
  • Corruption duration, M is the time period from the NPT time of the last good frame before the corruption, (since the NPT time for the first corrupted frame cannot always be determined) or the start of the measurement period (whichever is later) to the NPT time of the first subsequent good frame or the end of the measurement period (whichever is sooner) .
  • a corrupted frame may either be an entirely lost frame, or a media frame that has quality degradation and the decoded frame is not the same as in error-free decoding.
  • a good frame is a "completely received" frame X that, either:
  • Corruption duration, M, in milliseconds can be calculated according to the derivation of good frames as below:
  • a good frame can be derived by the client using the codec layer, in which case the codec layer signals the decoding of a good frame to the client.
  • a good frame could also be derived by error tracking methods, but decoding quality evaluation methods shall not be used.
  • An error tracking method may derive that a frame is a good frame even when it references previously decoded corrupted frames, as long as all the referenced pixels for generating the prediction signal were correctly reconstructed when decoding the reference frames.
  • a decoding quality evaluation method may derive that a frame is a good frame even one or more pixels of the frame have not been correctly reconstructed, as long as the decoding quality is considered by the method as acceptable. Such a frame is not a good frame according to the definition above, which shall be strictly followed.
  • a good frame should be derived according to N, where N is optionally signalled from MBMS streaming server (via SDP) to the MBMS client and represents the maximum duration, in presentation time, between two subsequent refresh frames in milliseconds. After a corrupted frame, if all subsequent frames within N milliseconds in presentation time have been completely received, then the next frame is a good frame.
  • N is not signalled, then it defaults to ⁇ (for video) or to one frame duration (for audio) .
  • the optional parameter D is defined to indicate which of options a) and b) is in use. D is signalled from the client to the server. When D is equal to "a" , option a) shall be in use, and the optional parameter T shall be present. When D is equal to "b” , option b) shall be in use and the optional parameter T shall not be present.
  • the optional parameter N as defined in point b is used with the "Corruption_Duration" parameter.
  • the optional parameter T is defined to indicate whether the client uses error tracking (when T is equal to “On” ) or not (when T is equal to "Off” ) . T is signalled from the client to the server.
  • Rebuffering is defined as any stall in playback time due to any involuntary event at the client side.
  • Rebuffering starts at the NPT time of the last played frame before the occurrence of the rebuffering.
  • MBMS reception reporting will be done only once at the end of streaming, hence all the occurred rebuffering durations are summed up over each resolution period of the stream and stored in the vector TotalRebufferingDuration.
  • the unit of this metrics is expressed in seconds, and can be a fractional value.
  • the number of individual rebuffering events for each resolution duration are summed up and stored in the vector NumberOfRebufferingEvents.
  • Initial buffering duration is the time from receiving the first RTP packet until playing starts.
  • the metric value indicates the initial buffering duration where the unit of this metrics is expressed in seconds, and can be a fractional value. There can be only one measure and it can only take one value. "Initial_Buffering_Duration" is a session level parameter. This value is reported by the MBMS client as part of the reception report (sub-clauses 9.4.6 and 9.5.3) .
  • the metric "Successive_Loss” indicates the number of RTP packets lost in succession (excluding FEC packets) per media channel.
  • MBMS reception reporting will be done only once at the end of streaming, hence all the number of successively lost RTP packets are summed up over each resolution period of the stream and stored in the vector TotalNumberofSuccessivePacketLoss.
  • the unit of this metric is expressed as an integer equal to or larger than 0.
  • the number of individual successive packet loss events over each resolution duration are summed up and stored in the vector NumberOfSuccessiveLossEvents.
  • the number of received packets is also summed up over each resolution duration and stored in the vector NumberOfReceivedPackets.
  • Frame rate and frame rate deviation indicates the playback frame rate information.
  • Frame rate deviation happens when the actual playback frame rate during a measurement period is deviated from a pre-defined value.
  • the actual playback frame rate is equal to the number of frames played during the resolution period divided by the time duration, in seconds, of the actual measurement. For the last measurement period in the session this time duration might be shorter than the configured measurement resolution (see 8.3.2.1 for the definition of the measurement resolution) .
  • the parameter FR that denotes the pre-defined frame rate value is used with the "Framerate_Deviation” parameter in the "3GPP-QoE-Metrics” attribute.
  • the value of FR shall be set by the server.
  • the syntax for FR to be included in the "att-measure-spec" (sub-clause 8.3.2.1) is as follows:
  • the metric "Framerate” indicates the actual playback frame rate. It is expressed in frames per second, and can be a fractional value.
  • the value field indicates the frame rate deviation value that is equal to the pre-defined frame rate minus the actual playback frame rate. This metric is expressed in frames per second, and can be a fractional value, and can be negative.
  • the frame rate and the frame rate deviations for each resolution period are stored in the vectors Framerate and FramerateDeviation and the vectors are reported by the MBMS client as part of the reception report (sub-clauses 9.4.6 and 9.5.3) .
  • Jitter happens when the absolute difference between the actual playback time and the expected playback time is larger than a pre-defined value, which is 100 milliseconds.
  • the expected time of a frame is equal to the actual playback time of the last played frame plus the difference between the NPT time of the frame and the NPT time of the last played frame.
  • Content access/switch time is the time that elapses between the initiation of a content request/switch by the user and up to the time when the first packet of the content or media stream is received.
  • the metric value indicates the content access/switch time and the unit of this metrics is expressed in seconds, and can be a fractional value. There can be only one measure and it can only take one value.
  • Content_Access_Time is a session level parameter. This value is reported by the MBMS client as part of the reception report (sub-clauses 9.4.6 and 9.5.3) .
  • the Network_Resource identifies the cell which has been used during each measurement resolution duration. There may be many measurement resolution durations in a reception report for a session, each of which identified with a cell identity in which the measurement was performed.
  • the cell is identified by the Cell Global Identity (as described in 3GPP TS 23.003 [77] ) , which is a concatenation of MCC, MNC, LAC and CI. It shall be coded as a text string as follows: Starting with the most significant bit, MCC (3 digits) , MNC (2 or 3 digits depending on MCC value) , LAC (4 hexadecimal digits) and CI (4 hexadecimal digits) .
  • E-UTRAN the cell is identified by the E-UTRAN Cell Global Identification (ECGI) (as described in 3GPP TS 36.331 [97] ) which is a concatenation of the PLMN Identifier (PLMN-Id) and the E-UTRAN Cell Identity (ECI) .
  • the PLMN identifier consists of MCC and MNC. It shall be coded as a text string as follows: starting with the most significant bit, MCC (3 digits) , MNC (2 or 3 digits depending on MCC value) and ECI (7 hexadecimal digits) .
  • the reported ECGI shall be the identity of the MBMS cell [96] , which could be the Primary Cell (PCell) , the Secondary Cell (SCell) , or the configurable SCell, if Carrier Aggregation [96] is employed in the E-UTRAN.
  • PCell Primary Cell
  • SCell Secondary Cell
  • PCell Carrier Aggregation
  • the vector is reported by the MBMS client as part of the reception report (sub-clauses 9.4.6 and 9.5.3) .
  • the average codec bitrate is the bitrate used for coding “active” media information during the measurement resolution period.
  • “active” information is defined by frames containing audio. If the audio codec uses silence frames (SID-frames) , these frames are not counted as “active” , and the SID-frames and the corresponding DTX time periods are excluded from the calculation. Thus for audio media the average codec bitrate can be calculated as the number of audio bits received for “active” frames , divided by the total time, in seconds, covered by these frames. The total time covered is calculated as the number of “active” frames times the length of each audio frame.
  • SID-frames silence frames
  • the average codec bitrate is the total number of media bits played out during the measurement resolution period, divided by the length of the playout period.
  • the playout period length is normally equal to the length of the measurement resolution period, but if rebuffering occurs the playout period will be shorter (i.e. any rebuffering time shall be ignored when calculating the codec bitrate) .
  • the average codec bitrate value for each measurement resolution period shall be stored in the vector AverageCodecBitrate.
  • the unit of this metrics is expressed in kbit/sand can be a fractional value.
  • the vector is reported by the client as part of the reception report (sub-clauses 9.4.6 and 9.5.3) .
  • the codec information metrics contain details of the media codec used during the measurement resolution period. If the codec information is changed during the measurement resolution period, the codec information valid when each measurement resolution period ends shall be reported.
  • the unit of this metric is a string value. No "white space" characters are allowed in the string values, and shall be removed if necessary.
  • the codec information contains the audio codec type, represented as in an SDP offer, for instance "AMR-WB/16000/1" .
  • the codec information contains the video codec type, represented as in an SDP offer, for instance “H263-2000/90000” .
  • the image size reported for each measurement resolution period shall be the one actually used, not the maximum size allowed by the SDP negotiation.
  • the codec information contains the text encoding, represented as in an SDP offer, for instance "3gpp-tt/1000" .
  • the CodecInfo, CodecProfileLevel and CodecImageSize vectors are reported by the client as part of the reception report (sub-clauses 9.4.6 and 9.5.3) .
  • the metric "Object_Loss” indicates the number of objects lost in a FLUTE session during a resolution period.
  • the number of lost objects are summed up over each resolution period of the session and stored in the vector numberOfLostObjects.
  • the unit of this metric is expressed as an integer equal to or larger than 0.
  • the number of received objects is also summed up over each resolution duration and stored in the vector NumberOfReceivedObjects.
  • the elements of the distribution of the metric "Distribution_of_Symbol_Count_Underrun" are calculated by subtracting the total number of source symbols, from the number of received symbols for a failed block in a failed object.
  • the range of values of the distribution are limited to the range of interest through top and bottom range parameters. Values greater than the top of the range are reported as the maximum value. Values lower than the bottom of the range are reported as the minimum value.
  • Reported values may also be grouped in bins.
  • the size of the bins used for collecting statistics are specified through a bin size parameter. The first bin starts at the bottom of the range. The last bin must include the top of the range. Collection bins are adjacent.
  • the range of file sizes considered for calculating the metric can also be restricted through optional minimum, and maximum file size parameters.
  • the distribution is reported per measurement duration as a string list of (bin lower bound, number of occurrences) pairs, with each pair corresponding to a single entry.
  • the bin lower bound uniquely identifies a bin by providing the lowest value of the range of each bin.
  • the bin lower bound, and number of occurrences are both integer values.
  • the following string format shall be used: “ (bin lower bound, number of occurrences) ” , where the parentheses represent the delimiter and the comma separates the bin lower bound (integer range of values) and number of occurrences (positive integer range of values) .
  • the vector SymbolCountUnderrun is a string vector where the entries are listed sequentially, without a space character between adjacent entries of the overall set.
  • the set of entries is delimited by curly brackets: “ ⁇ “at the beginning and “ ⁇ ” at the end. Bins with zero occurrences are omitted from the list. Values greater than the top of the range are reported within the bin containing the top of the range. Values lower than the bottom of the range are reported within the first bin containing the bottom of the range.
  • SymbolCountUnderrun When SymbolCountUnderrun contains information for multiple measurement durations, it shall comprise a sequence of curly bracket delimited entries, with adjacent members of the sequence separated by one or more space characters. If the number of occurrences for all bins equals zero for a particular measurement duration within the SymbolCountUnderrun, the string “ ⁇ ” shall be used to signal that event.
  • the following example shows a scenario whereby the reported distribution of the symbol count underrun comprises the entries of a single measurement duration, and for which bins -9, -4 and 0 have occurrences 2, 6 and 4, respectively.
  • the vector SymbolCountUnderrun is given as:
  • the next example shows a scenario whereby the reported distribution comprises entries of multiple measurement durations.
  • bins -3, -2 and -1 have occurrences 1, 3 and 5, respectively, and there are no occurrences in the next two measurement durations.
  • the vector SymbolCountUnderrun is given as:
  • the top, bottom, and bin size of the distribution range are provided through the optional parameters T, B, and S respectively.
  • T, B, and S are provided through the optional parameters T, B, and S respectively.
  • the syntax for T, B, and S to be included in the "att-measure-spec" (sub-clause 8.3.2.1) is as follows:
  • the default value of the top of the range, in case the T parameter is omitted, is 0.
  • the default value of the bottom of the range, in case the B parameter is omitted, is -10.
  • the default value of the bin size is 1.
  • the minimum and maximum file sizes considered for calculating the metric are provided through the optional parameters Y and Z, respectively.
  • the syntax for Y and Z to be included in the "att-measure-spec" (sub-clause 8.3.2.1) is as follows:
  • the default value of the minimum file size is 0, and the default value of the maximum file size is infinity.
  • This following example shows the syntax of the SDP attribute for QoE metrics.
  • the session level QoE metrics description (Initial buffering duration, rebufferings and network resource) are to be monitored with a measurement resolution of 20 seconds and reported at the end of the session.
  • video specific description of metrics (corruptions) are to be monitored and reported at the end from the beginning of the stream until the time 40s.
  • audio specific description of metrics (corruptions) is to be monitored with a measurement resolution of 10s and reported at the end of the stream.
  • the MBMS service consumption reporting procedure is initiated by the MBMS receiver (UE) to the BM-SC, in accordance to parameters in the Associated Delivery Procedure description.
  • Consumption of an MBMS User Service over an MBMS bearer by a UE is defined as the reception of service content on any of the transport session (s) referenced by the deliveryMethod element (s) under the userServiceDescription element of that service.
  • Consumption of an MBMS User Service delivered over unicast by the UE, in the event that the MBMS bearer for such service is not provisioned where the UE is located, is represented by the reception of service content associated with either (but not both) the r12: unicastAppService child element or the r8: alternativeAccessDelivery child element under the deliveryMethod element.
  • the MBMS Receiver shall determine whether a consumption report is required for an associated MBMS User Service.
  • An Associated Delivery Procedure Description indicates the parameters of a consumption reporting procedure (transported using the HTTP request mechanism procedure similarly used for File Repair and Reception Reporting) .
  • An MBMS User Service may associate zero or one Consumption Reporting Description instances with the MBMS User Service.
  • the UE shall initiate a consumption reporting procedure when any of the conditions below become valid:
  • the UE stops consuming the MooD eligible MBMS User Service on unicast, and starts consumption of the service on an MBMS bearer;
  • the UE stops consuming the MooD eligible non-MBMS service on unicast, and starts consumption of the corresponding MBMS User Service on an MBMS bearer
  • the UE stops consuming the MBMS User Service on a MBMS bearer, and starts consumption of the MBMS User Service on unicast;
  • the "ongoing" report is performed at periodic intervals as set by the reportInterval attribute of the r12: consumptionReport element.
  • ⁇ Upon determining a location change. If the location element in r12: consumptionReport is included, and upon detecting a change of location while consuming an MBMS User Service. Depending on the value of the location child element in the r12: consumptionReport element, the UE detects a location change as either
  • an MBMS SAI change if the location element indicates to report MBMS SAI.
  • An MBMS SAI location change shall be detected by the UE if there are one or more SAI values that have changed in its non-empty SAI list (s) prepared for inclusion in the Consumption Report Request message as specified in clause 9.5A. 5, and any of the SAIs in the list match any of the SAI in availabilityInfo. infoBinding. serviceArea elements in the USD.
  • ⁇ SIB 15 is not present.
  • the UE shall not generate Consumption Report signalling unicast comsumption to indicate:
  • the UE shall instead report Start of UE consumption of the MBMS User Service on the MBMS bearer if Consumption Report is enabled for MBMS User Service consumed on the MBMS bearer;
  • the UE shall instead report Stop of UE consumption of the MBMS User Service on the MBMS bearer if Consumption Report is enabled for MBMS User Service consumed on the MBMS bearer;
  • the BM-SC can specify the percentage subset of MBMS receivers that the BM-SC would like to perform consumption reporting via the samplePercentage attribute.
  • the samplePercentage takes on a value between 0 and 100, including the use of decimals. It is recommended that no more than 3 digits follow a decimal point (e.g. 67.323 is sufficient precision) .
  • the samplePercentage attribute is optional and the default UE behavior when it is absent is to always perform consumption reporting in accordance to the rules and criteria stated in this sub-clause 9.4A. 2, as well as sub-clauses 9.4A. 3, 9.4A. 4 and 9.4A. 5.
  • the BM-SC can specify the nominal periodicity by which the UE, when it is continuously consuming the service of concern, shall perform consumption reporting.
  • This periodicity defined as a time duration between consecutive reports, is specified by the reportInterval attribute.
  • Periodic consumption reporting uses the ′report interval′ timer, which is preset to the reportInterval value whenever the UE starts consumption of the associated MBMS User Service, or when the timer has expired from the previous countdown cycle, and begins a subsequent countdown cycle.
  • the reportInterval attribute is optional and the default UE behavior when it is absent is not to perform ongoing consumption reporting.
  • the BM-SC can specify whether the UE shall include its current location by serving cell-ID or MBMS SAI when it performs consumption reporting, via the location child element of r12: consumptionReport.
  • the cell-ID (s) to be reported depends on whether the MBMS service is delivered on unicast bearer (s) or MBMS bearer (s) , if Carrier Aggregation [96] is employed in the E-UTRAN. If the MBMS service is delivered via unicast bearer (s) , the reported ECGI (s) should include the identity (identities) of all serving cell (s) , i.e., that of the PCell and zero or more SCells.
  • the reported cell-ID shall be that of the MBMS cell, which could be either the PCell, the SCell, or a configurable SCell.
  • the UE shall report its location according to the enumerated value of the location element, i.e., "MBMS SAI” , "CGI” or ECGI".
  • the location element is optional and the default UE behavior when it is absent, or if its content is set to an unknown value, is not to include the UE′s location in the consumption report.
  • the BM-SC can specify whether the UE shall include, in the consumption report message, the clientId attribute which represents the unique identifier for the receiver, e.g. an MSISDN of the UE as defined in [77] .
  • the clientId attribute which represents the unique identifier for the receiver, e.g. an MSISDN of the UE as defined in [77] .
  • This is specified by the reportClientId attribute of r12: consumptionReport, which when set to "1" or "true” indicates that the UE shall include clientId in the consumption report message, and when set to "0" or "false” indicates that the UE shall not include clientId in the consumption report message.
  • the reportClientId attribute is optional and the default UE behavior when it is absent is not to include the client identifier in the consumption report.
  • One or more consumption report servers are implemented in the BM-SC, and the selection of which consumption report to use by the UE is performed similar to the procedure described for file repair server selection in sub-clause 9.1. If more than one serviceURI elements are present under consumptionReporting, the UE shall randomly select one of them, with uniform distribution as the destination of the consumption report message. Use of the selected consumption report server by the UE shall be maintained for the entire duration span of UE submissions of the "start” , "ongoing” (one or more) , and “stop” consumption reports, unless the consumption report server redirects the UE to another consumption report server using an HTTP 3xx status code in the response message.
  • the UE When a UE obtains an updated APD fragment for the MBMS User Service of interest, and the serviceURI under the consumptionReporting element that the UE had selected is no longer listed in the updated APD, the UE shall randomly select a new serviceURI element currently present under consumptionReporting, with uniform distribution as the destination of the consumption report request message. The UE shall send consumption reports to the newly selected destination at the next scheduled “ongoing” consumption report opportunity, as well as for consumption report submission resulting from a “location change” , a “stop” , or a “start” condition.
  • Back-off timing is used to spread the load of consumption report requests uniformly over time.
  • Back-off timing is performed according to the procedure described in sub-clause 9.3.4.
  • the offset time and random time period used for consumption reporting may differ in values from those used in file-repair and/or reception reporting, and are signalled separately by the offsetTime and randomTimePeriod attributes of the consumptionReport child element of the Associated Delivery Procedure Description instance. For example, UEs might be required to submit consumption reports within a tighter time window and with a smaller offset delay to enable more timely reception of consumption reports by the BM-SC in order to affect dynamic decision on whether to maintain or disable the associated MBMS service.
  • the offsetTime attribute is optional. The default UE behavior when this attribute is absent or set to ′0′ is not to employ a wait time before computing a random time within the time window given by randomTimePeriod in initiating the consumption report procedure.
  • the MBMS receiver sends one or more Consumption Report request messages to the consumption report server identified by the serviceURI.
  • Consumption Report requests and responses pertaining to a single complete sequence of the "start” , one or more "ongoing” , and the "stop" consumption reports to/from the same consumption report server shall take place in one or more TCP sessions using the HTTP protocol (RFC 2616 [18] ) , i.e., via the use of either persistent or non-persistent TCP connections for carrying the HTTP consumption reporting traffic.
  • the reportClientId attribute of the r12 consumptionReport element in the ADPD fragment should be set to "1" or "true” .
  • the MBMS client shall make a Consumption Report request using the HTTP (RFC 2616 [18] ) POST request carrying XML formatted metadata for each report.
  • the MIME Type for the document in the request shall be as defined in Annex C. 16.
  • Each consumption report is formatted in XML according to the XML schema shown in sub-clause 9.5.4.
  • An informative example of a single consumption report XML object is given in sub-clause 9.5.4.1) .
  • the Consumption Report request message contains the following mandatory and optional parameters:
  • the consumptionType attribute which declares the consumption report as belonging to one of the following types, and are mapped to the conditions for consumption reporting as indicated in sub-clause 9.4A. 2:
  • the reportTime attribute which identifies the time when the report is generated by the UE.
  • the location attribute which represents the UE′s location by CGI or ECGI or the list (s) of MBMS SAI (s) from SIB15 [97] as defined by the MooD configuration parameter ⁇ X>/LocationType in sub-clause 12.2.2.
  • the UE shall build the list of MBMS SAIs to include in its Consumption Report Request message as follows:
  • the HTTP header shall use a status code of 200 OK to signal successful processing of a Consumption Report request message.
  • Other status codes may be used in error cases as defined in RFC 2616 [18] .
  • the schema filename of consumption report request is consumptionreport. xsd.
  • the UE shall set the schemaVersion element, defined as a child of r12: consumptionReport element, to 1.
  • the schema version attribute (part of the schema instruction) shall be included in the UE schema.
  • the network When the network receives an instantiation of a consumption report request message compliant to this schema, it shall determine the schema version required to parse the instantiation as follows:
  • the network If the network supports one or more versions of the consumption report request message schema with the schema version attribute, then it shall use the schema that has the highest schema version attribute value that is equal to or less than the value in the received schemaVersion element.
  • MBMS operation on Demand In the operation of "MBMS operation on Demand” , or MooD, certain content that is initially delivered over the unicast network may be turned into an MBMS User Service, in order to efficiently use network resources when the traffic volume exceeds a certain threshold.
  • Such dynamic conversion from unicast delivery to MBMS delivery is also referred to as "MBMS offloading" .
  • the MBMS offloading may apply to unicast traffic carried over HTTP or RTP/RTSP. In the former case, the MBMS download delivery method is used, and in the latter, the MBMS streaming method based on RTP is used, for delivering the offloaded content.
  • MBMS offloading There are two types of MBMS offloading: UE-Elected and Network-Elected offloading. In both types, there could be a network proxy/server to detect whether unicast traffic volume for the same service or content exceeds a certain threshold, and to indicate such occurrence to the BM-SC to enable MBMS offloading. To assist the MooD decision, the network proxy/server may obtain UE location from the UE per operator’s policy. Alternatively, the network proxy/server may act as an Application Function in requesting from the PCRF, via the Rx reference point, the UE′s location information via the 3GPP-User-Location-Info AVP defined in TS 29.214 [117] .
  • Rx-specific AVP as defined in TS 29.214 [117] are outside the scope of MooD.
  • the network proxy/server may also use LCS procedure defined in 23.271 [118] to obtain the UE’s location information.
  • the network proxy/server may deliver user location information to the BM-SC for MooD decision.
  • the interface between the network proxy/server and the BM-SC is outside the scope of this specification.
  • UE-elected offloading means that a MooD-capable UE will send its unicast requests, for content eligible for conversion to delivery as an MBMS service (as described by the MooD Configuration Management Object (MO) based on the request domains) , to a designated proxy server.
  • MO MooD Configuration Management Object
  • the UE If the UE receives a MooD redirect response (containing the MooD header field) , it will activate the MBMS client by providing it with entry point information to the USD that is already provisioned or that is provided in the MooD header field.
  • the MooD redirect response is sent by the network proxy server in one of the following ways:
  • the MBMS client when the MBMS client is operational, having acquired the USD fragments (including the Media Presentation Description fragment in the case of DASH-formatted content) for the new MBMS service, and has begun receiving contents over the MBMS bearer, future requests for content by the client application (e.g., the DASH client) will be served by the MBMS client.
  • the client application e.g., the DASH client
  • the UE Via OMA-DM (Device Management) based MooD Configuration MO, the UE is provisioned with configuration information pertaining to MooD operation as described in clause X. 2.2 .
  • Configuration parameters may include the proxy server over which unicast content requests have to be sent, identification of contents for which offloading to MBMS is eligible, and the location of the USD for UE to acquire service announcement information.
  • the redirection message shall contain the 3GPP-specified MooD header field that triggers the activation of the MBMS receiver in the UE, as defined below in clause 12.2.1.
  • a UE that is not able to handle the redirection message appropriately shall not use the proxy server for the requests.
  • UEs that comply to this specifications shall support handling of the redirection message.
  • a new 3GPP header field i.e., MooD header
  • the MooD header field applies both to RTSP and HTTP redirections. If the UE detects the presence of the MooD header, it shall assume that this is an indication to activate the MBMS client. If the MBMS client is already activated or operational, the header represents an implicit notification that updated USD fragments must be acquired.
  • the MooD header field may contain entry point information to the MBMS USBD fragment which in turn enables reception of the dynamically-established MBMS service.
  • the precedence rules for UE acquisition of USD fragments as result of the UE receiving the MooD header are given below, in decreasing order of priority (refer to clause 12.2.2 regarding the details of the MooD Configuration Management Object) :
  • the MBMS client shall use it to retrieve the USBD fragment over unicast.
  • the MBMS client shall use it to retrieve USD fragments over unicast.
  • the MBMS client shall use that information to acquire the USD fragments over broadcast.
  • the UE should continue to request contents via the unicast network, to avoid service disruption or a "break before make" switching from unicast to broadcast content reception.
  • a switch in reception mode from unicast to broadcast is expected to occur internally to the UE.
  • the MooD header field shall also be used by the UE to indicate its current location to the MooD proxy server, if requested to do so by the information in the MooD Configuration MO.
  • the UE′s current location shall be formatted according to the "LocationType" value as described in sub-clause 12.2.2. If the UE has acquired the serviceId from the USBD, then the service-id shall also be included.
  • the ABNF syntax for the MooD header field is defined as follows:
  • MooD "3gpp-mbms-offloading” ": " [ (absolute-URI “; “ service-id) / (relative-ref “; “ service-id) / (currentLocation “; “ service-id) /currentLocation “; “ /”; “ service-id] , where
  • ⁇ ⁇ absolute-URI> and ⁇ relative-ref> are as defined in RFC 3986 [19] .
  • ⁇ ⁇ currentLocation> represents the serving cell-ID (s) or a list of MBMS SAI of the UE whose format is defined by the location type in the / ⁇ X> /LocationType leaf of the MooD Configuration MO as defined in sub-clause 12.2.2, whereby the one or more entries of cell-ID or SAI are specified as a string of comma-separated values, and
  • ⁇ ⁇ service-id> represents the associated serviceId attribute (as defined in clause 11.2.1.1) of the MBMS User Service.
  • the serviceId content in the MooD header shall be formatted according to the rules specified in RFC 2616 [18] , in particular regarding handling of special characters in field values that have to be quoted (clause 2.2 of RFC 2616 [18] ) .
  • the serving cell-ID (s) should correspond to all cells from which the UE receives the service, i.e., the PCell and any SCell (s) , if Carrier Aggregation [96] is employed in the E-UTRAN.
  • the serving cell-Id text format follows the format defined in clause 8.4.2.8.
  • ⁇ ⁇ intersected-SAI> Comma-separated list of SAIs corresponding to the intersection between the SAIs in SIB 15 (see [97] ) intersected and the list of MBMS Service Area Identities included in the userServiceDescription. availabilityInfo. infoBinding. serviceArea elements for the same serviceId. Before the intersection is created, all SAIs from intra-frequency neighbour cells shall be removed from the SIB15 SAI list (see [97] for details SAIs from intra-frequency neighbour cells) .
  • the MooD header shall include the ⁇ currentLocation> field-value.
  • the UE does not contain the MooD Configuration MO, but is MooD-capable and is preconfigured with the rule to include its location in the HTTP request, then the ⁇ currentLocation> field-value shall be contained in the MooD header.
  • the UE does not contain the MooD Configuration MO, but is MooD-capable and is not preconfigured with the rule to include its location in the HTTP request, then the MooD header containing solely the field-name followed by a colon ( ": " ) , i.e. "3gpp-mbms-offloading: " , is sent to indicate that the UE is MooD-capable.
  • a subsequent MooD redirect response will contain the MooD header instantiated in one of the following ways:
  • the MooD header comprises the concatenation of field-name "3gpp-mbms-offloading" , a colon ( ": " ) , and the service-id;
  • the MooD header comprises the concatenation of the field-name "3gpp-mbms-offloading" , a colon ( “: “ ) , an HTTP_URL representing the location of the USBD fragment for unicast HTTP acquisition, a semi-colon ( “; “ ) , and the service-id;
  • the MooD header comprises the concatenation of the field-name "3gpp-mbms-offloading” , a colon ( “: “ ) , a relative reference to the USBD fragment which can be resolved by using a base URI, a semi-colon ( “; “ ) , and the service-id.
  • the MooD header shall include the ⁇ currentLocation> field-value.
  • the UE does not contain the MooD Configuration MO, but is MooD-capable and is preconfigured with the rule to always include its location in the RTSP request, then the ⁇ currentLocation> field-value shall be contained in the MooD header.
  • the MooD header containing solely the field-name followed by a colon ( ": " ) , i.e. "3gpp-mbms-offloading: " , is sent to indicate that the UE is MooD-capable.
  • a subsequent MooD redirect response will contain the MooD header instantiated in one of the following ways:
  • the MooD header comprises the concatenation of field-name "3gpp-mbms-offloading" , a colon ( ": " ) , and the service-id;
  • the MooD header comprises the concatenation of the field-name "3gpp-mbms-offloading” , a colon ( “: “ ) , an RTSP_URL representing the location of the USBD fragment for unicast RTP/RTSP acquisition, a semi-colon ( ";” ) , and the service-id;
  • the MooD header comprises the concatenation of the field-name "3gpp-mbms-offloading” , a colon ( “: “ ) , a relative reference to the USBD fragment which can be resolved by using a base URI, a semi-colon ( “; “ ) , and the service-id.
  • OMA-DM should be used to specify the MooD configuration information. If such a DM configuration object exists on the UE, the UE shall use it whenever it elects to support MBMS offloading.
  • the OMA DM management object is used to configure offloading for any type of eligible content accessed over the unicast network via HTTP or RTP.
  • the Management Object Identifier shall be set to: urn: oma: mo: ext-3gpp-mbmsmood: 1.0.
  • the MO is compatible with OMA Device Management protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework as described in the Enabler Release Definition OMA-ERELD _DM-V1_2 [94] .
  • the MO information may be translated into a Proxy Auto-Config (PAC) file that can be used by the UE to automatically pick the proxy server for the eligible content.
  • PAC Proxy Auto-Config
  • FIGURE 18 depicts the nodes and leaf objects contained under the 3GPP_MBMS MooD MO, if an MBMS client supports the feature described in this clause (information on the DDF for this MO is given below in Annex X) .
  • This interior node specifies the unique object id of a MBMS MooD management object.
  • the purpose of this interior node is to group together the parameters of a single object.
  • the following interior nodes shall be contained if the UE supports the “MBMS MooD Management Object” .
  • This leaf indicates if MooD is supported by the BM-SC.
  • This node represents the one or more Proxy Servers that the UE shall use for all its unicast requests to resources that it elects to potentially receive over MBMS.
  • This interior node acts as a placeholder for one or more instances of ProxyServer information as addresses associated with content restriction identifiers for proxy server selection. Should more than one proxy server satisfy the conditions of the content restriction, the UE may randomly select one of them.
  • This leaf indicates the one or more address of a ProxyServer in the form of a Fully-Qualified Domain Name (FQDN) , and is associated with a set of content restrictions of which at least one must be satisfied in order for a UE to use that/those Proxy Server (s) for all its unicast requests to resources that it elects to potentially receive over MBMS.
  • FQDN Fully-Qualified Domain Name
  • the ContentRestriction leaf contains one or more domain names for matching against the HTTP (s) or RTSP URL of the resource request issued by the UE to determine whether the requested content is eligible for conversion from unicast access to an MBMS User Service, and if so, the corresponding Proxy Server to use.
  • a match between this value and the requested resource URL indicates that the requested resource may be switched to MBMS delivery, and the associated proxy server shall be used by the UE for unicast access of that resource.
  • the ContentRestrictionExt node allows for more refined definition of the MooD eligible content and the rules on when to use the proxy server to query for availability of content over MBMS. If both ContentRestriction and ContentRestrictionExt exist, then the UE shall apply both of them to determine if a particular resource URL is MooD eligible and needs to be sent through the MooD proxy. In particular, if a ContentRestriction element exists and none of the provided FQDNs match, then the UE shall assume that the content is not eligible. If the ContentRestriction is not available, then it shall be assumed that all FQDNs are MooD eligible but only those that match at least one of the patterns in ContentRestrictionExt will use the MooD proxy.
  • the UrlPattern leaf provides a regular expression as defined by [126] that the request URL will be matched against. If the request matches, the requested resource is marked as MooD eligible.
  • the Ext node is an interior node where vendor-specific information can be placed (vendor meaning application vendor, device vendor, etc. ) , pertaining to UE selection of the proxy server.
  • vendor-specific information can be placed (vendor meaning application vendor, device vendor, etc. ) , pertaining to UE selection of the proxy server.
  • the vendor extension is identified by a vendor-specific name under the Ext node.
  • the tree structure under the identified vendor is not defined and can therefore include one or more non-standardized sub-trees.
  • the USD node is the starting point of the MBMS User Service Discovery/Announcement information definitions.
  • This leaf provides a URL to an aggregated service announcement document encapsulating all relevant metadata fragments for the demand-based MBMS user service, which the UE can fetch using the unicast channel. It may also be used by the network when the network redirects the UE to switch MBMS reception. Should a redirection message provide an alternative redirection link to service announcement information, it shall take precedence over the URL provided by the MO.
  • the Ext node is an interior node where vendor-specific information can be placed ( "vendor" may correspond to an application vendor, device vendor, etc. ) .
  • vendor may correspond to an application vendor, device vendor, etc.
  • the vendor extension is identified by a vendor-specific name under the Ext node.
  • the tree structure under the vendor identified is not defined and can therefore include one or more un-standardized sub-trees.
  • This leaf provides a location type for UE to report in the unicast content request.
  • Exactly one of the following entries: one or more serving cell-ID (s) (cell-ID in the form of CGI (Cell Global Identification) or ECGI (E-UTRAN Cell Global Identification) ) or MBMS SAI may be present.
  • CGI, ECGI and MBMS SAI are defined in 3GPP TS 23.003 [4] .
  • the serving cell-ID (s) should correspond to all cells from which the UE receives the service, i.e., the Primary Cell or P-Cell and any Secondary Cell (s) or S-Cell (s) , if Carrier Aggregation [96] is employed in the E-UTRAN.
  • the UE When present, the UE should send its location as part of the MooD header field together with the requests that it sends to a MooD proxy server. If the LocationType is set to MBMS SAI, the UE includes the SAIs present in SIB15 [97] .
  • the Ext node is an interior node where vendor-specific information can be placed ( "vendor" may correspond to an application vendor, device vendor, etc. ) .
  • vendor may correspond to an application vendor, device vendor, etc.
  • the vendor extension is identified by a vendor-specific name under the Ext node.
  • the tree structure under the identified vendor is not defined and can therefore include one or more non-standardized sub-trees.
  • a MooD-capable UE may include the MooD header field in the HTTP GET request if the MooD Configuration MO is not present in the UE, and is preconfigured with a rule (e.g. in compliance to the home service operator requirement) to indicate its MooD-capability.
  • the MooD header may be sent in one of two ways, in accordance to rules (b) and (c) in sub-clause 12.2.1.1, and shall follow the syntax defined in sub-clause 12.2.1.
  • the UE Once the UE receive a network proxy/server response containing the MooD header field, it shall follow the same procedure as defined in sub-clause 12.2.1.
  • This part of ISO/IEC 23009 does not define mechanisms for reporting metrics, however it does define a set of metrics and a mechanism that may be used by the service provider to trigger metric collection and reporting at the clients, should a reporting mechanism be available.
  • the trigger mechanism is based on the metrics element in the MPD.
  • the element contains the list of DASH Metrics for which the measurements are desired, the time interval and the granularity for the measurements, as well as the scheme according to which the metric reporting is desired.
  • the semantics of the attributes within the metrics element are provided in Table 23 of 5.9.2.
  • the XML syntax of metrics element is provided in 5.9.3.
  • FIGURE 19 illustrates a table comprising semantics of metrics elements, as included in Table 23 of ISO/IEC 23009-1.
  • DASH clients should collect metrics based on the metric element and report the collected metrics using one of the reporting schemes in the Reporting descriptor in the metrics element.
  • reporting scheme is specified in this part of ISO/IEC 23009. It is expected that external specifications may define formats and delivery for the reporting data. External specifications defining a reporting scheme should take specific care to respect privacy issues.
  • This Annex defines the ISO/IEC 23009-1 DASH Metrics.
  • the normative aspects of the Annex are defined in D. 4, namely the semantics of the metrics and the associated keys to be used for requesting the collection of the metrics.
  • the client reference model in D. 2 and the observation points in D. 3 serve as informative background information.
  • the DASH-Metrics client reference model is depicted in highlighting so-called observation points (OPs) as defined in FIGURE 20.
  • the DASH access client issues HTTP requests (for DASH data structures) , and receives HTTP request responses (containing DASH data structures) .
  • Data structures may typically be MPDs, Segments or partial Segments.
  • This input/output interface from the network towards the DASH client is referred to as observation point 1 (OP1) .
  • the DASH client delivers encoded media samples to the DASH-enabled application for further processing and may receive also commands from it.
  • This input/output interface of the DASH client towards the DASH-enabled application is referred to as observation point 2 (OP2) .
  • the DASH-enabled application delivers decoded media samples to the media output, which displays the media to the user.
  • This output interface towards the user is referred to as observation point 3 (OP3) .
  • the observation point 1 (0P1) is defined as:
  • N0TE The contents of the response body is fully defined by the contents of the request and response headers.
  • the observation point 2 (0P2) consists of encoded media samples.
  • Each encoded media sample is defined as:
  • the observation point 3 (0P3) consists of decoded media samples.
  • Each decoded media sample is defined as:
  • This subclause provides the general QoE metric definitions and measurement framework.
  • Each metric is defined as a named list of entries that logically contains the metric information for the entire Media Presentation. Reporting of these lists, whether done at the end of the Media Presentation or incrementally during the Media Presentation is out of scope of this specification.
  • Table D. 1 contains the metric defining the list of TCP connections.
  • the key in Table D. 1 shall be used to refer to the metric as defined in Table D. 1.
  • Table D. 2 contains the metric defining the List of HTTP Request/Response Transactions.
  • the key in Table D. 2 shall be used to refer to the metric as defined in Table D. 2.
  • the periods in Entry should be those periods where the client was actively reading from the TCP connections (i.e., they should not include periods where the TCP connection is idle due to zero receive window) .
  • the end of the last measurement period in the trace shall be the time at which the last byte of the response was received.
  • the interval and trace shall be absent for redirect and failure records.
  • HttpList (n, type) where n is a positive integer is defined for an HttpList with an interval of n ms and type is one of MPD, XLinkExpansion, InitializationSegment, MediaSegment, IndexSegment BitstreamSwitchingSegment or other. If type is not present, all HTTP transactions are requested to be collected. If type is present, it specifies that the HTTP transactions concerning a resource equal to type are requested to be collected. Multiple keys HttpList (n, type) with different values of n and type may be present for a single @metrics attribute value.
  • Table D. 3 as illustrated in FIGURE 23, defines the metric for Representation switch events.
  • the key in Table D. 3 shall be used to refer to the metric as defined in Table D. 3.
  • Table D. 4 defines the metric for buffer level status events.
  • the key in Table D. 4 shall be used to refer to the metric as defined in Table D.4.
  • the key is BufferLevel (p) , where n is a positive integer is defined to refer to the metric in which the buffer level is recorded every n ms.
  • Decoded samples are generally rendered in presentation time sequence, each at or close to its specified presentation time.
  • a compact Representation of the information flow can thus be constructed from a list of time periods during which samples of a single Representation were continuously rendered, such that each was presented at its specified presentation time to some specific level of accuracy (e.g., +/-10ms) .
  • Such a sequence of periods of continuous delivery is started by a user action that requests playout to begin at a specified media time (this could be a "play” , “seek” or “resume” action) and continues until playout stops either due to a user action, the end of the content, or a permanent failure.
  • Table D. 5 defines the play list event metric.
  • the key in Table D. 5 shall be used to refer to the metric as defined in Table D. 5.
  • the trace may include entries for different representations that overlap in time, because multiple representations are being rendered simultaneously, for example one audio and one video Representation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un procédé mis en œuvre par un dispositif sans fil consiste à recevoir, par l'intermédiaire d'un premier service de distribution de données, de données associées à un service d'utilisateur (1302). Des informations de qualité de service associées aux données distribuées par l'intermédiaire du premier service de distribution de données sont déterminées (1304). Un premier rapport de consommation de données est transmis à un nœud de réseau (1306). Le premier rapport de consommation de données comprend les informations de qualité de service associées aux données distribuées par l'intermédiaire du premier service de distribution de données. En réponse à la transmission du premier rapport de consommation de données, des données associées au service d'utilisateur sont reçues par l'intermédiaire d'un second service de distribution de données (1308).
PCT/CN2019/077915 2018-03-14 2019-03-13 Amélioration de qualité de service concernant un changement d'humeur basé sur un rapport de consommation WO2019174588A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP19766501.1A EP3766226A4 (fr) 2018-03-14 2019-03-13 Amélioration de qualité de service concernant un changement d'humeur basé sur un rapport de consommation

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2018/078985 2018-03-14
CN2018078985 2018-03-14

Publications (1)

Publication Number Publication Date
WO2019174588A1 true WO2019174588A1 (fr) 2019-09-19

Family

ID=67907405

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/077915 WO2019174588A1 (fr) 2018-03-14 2019-03-13 Amélioration de qualité de service concernant un changement d'humeur basé sur un rapport de consommation

Country Status (2)

Country Link
EP (1) EP3766226A4 (fr)
WO (1) WO2019174588A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022034281A1 (fr) * 2020-08-13 2022-02-17 Sony Group Corporation Dispositif terminal, équipement d'infrastructure et procédés
WO2024103163A1 (fr) * 2022-11-18 2024-05-23 Voiceage Corporation Procédé et dispositif de transmission discontinue dans un codec audio basé sur un objet

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1984056A (zh) * 2006-05-17 2007-06-20 华为技术有限公司 一种流媒体播放控制方法、装置及系统
CN101547108A (zh) * 2008-03-28 2009-09-30 华为技术有限公司 流媒体的业务切换方法、播放设备及服务器
CN101827306A (zh) * 2009-03-03 2010-09-08 中兴通讯股份有限公司 单播业务的切换方法与装置
US20130268577A1 (en) 2012-04-09 2013-10-10 Ozgur Oyman Quality of experience reporting for combined unicast-multicast/broadcast streaming of media content
US20170238148A1 (en) 2016-02-12 2017-08-17 Samsung Electronics Co., Ltd Methods and apparatus for enhanced mbms content provisioning and content ingestion

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9774465B2 (en) * 2014-12-24 2017-09-26 Intel Corporation Media content streaming

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1984056A (zh) * 2006-05-17 2007-06-20 华为技术有限公司 一种流媒体播放控制方法、装置及系统
CN101547108A (zh) * 2008-03-28 2009-09-30 华为技术有限公司 流媒体的业务切换方法、播放设备及服务器
CN101827306A (zh) * 2009-03-03 2010-09-08 中兴通讯股份有限公司 单播业务的切换方法与装置
US20130268577A1 (en) 2012-04-09 2013-10-10 Ozgur Oyman Quality of experience reporting for combined unicast-multicast/broadcast streaming of media content
CN103368940A (zh) * 2012-04-09 2013-10-23 英特尔公司 媒体内容的组合单播-多播/广播流的体验质量报告
US20170238148A1 (en) 2016-02-12 2017-08-17 Samsung Electronics Co., Ltd Methods and apparatus for enhanced mbms content provisioning and content ingestion

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3766226A4

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022034281A1 (fr) * 2020-08-13 2022-02-17 Sony Group Corporation Dispositif terminal, équipement d'infrastructure et procédés
GB2598102A (en) * 2020-08-13 2022-02-23 Sony Group Corp A terminal device, infrastructure equipment and methods
WO2024103163A1 (fr) * 2022-11-18 2024-05-23 Voiceage Corporation Procédé et dispositif de transmission discontinue dans un codec audio basé sur un objet

Also Published As

Publication number Publication date
EP3766226A4 (fr) 2021-12-08
EP3766226A1 (fr) 2021-01-20

Similar Documents

Publication Publication Date Title
US11606707B2 (en) Measurement reporting configuration for aiding the sorting of beam/cell level measurements
US11696278B2 (en) Methods, apparatus and computer-readable media related to semi-persistent scheduling configuration
US11889349B2 (en) Transport of data flows over cellular networks
US11863323B2 (en) Avoiding multiple retransmissions of signalling transported by 5G NAS transport
TW201933847A (zh) 傳送和接收資料單元
US12048054B2 (en) Handling of session context
US20240129383A1 (en) Methods and Apparatus for Transmitting Capability Information
US20200267632A1 (en) RNA Configuration Signalling Optimization
US11864247B2 (en) Data network name (DNN) manipulation
US20240155470A1 (en) Duplicated SIB Handling in Sidelink Relay
US20210345319A1 (en) Methods of signaling reserved resources for ultra-reliable low latency communication (urllc) traffic
WO2019174588A1 (fr) Amélioration de qualité de service concernant un changement d'humeur basé sur un rapport de consommation
US20230080510A1 (en) Change request with indication that no notification of subscribed data change is to be sent to requesting network function
US20230308968A1 (en) Adaptive communication channel leg switching
US20230276306A1 (en) Methods supporting a capability to modify session traffic in response to a handover and related network nodes
US20220131774A1 (en) Data volume reporting in 5gs
US20240064072A1 (en) Methods and Apparatuses for Supporting Quality of Experience Measurements
US20230308995A1 (en) User equipment positioning for new radio (nr)
WO2024030064A1 (fr) Procédés et appareils pour rapporter des mesures de qualité d'expérience pour un service de diffusion en multidiffusion
OA21010A (en) Individual user equipment management in RAN.
WO2024030057A1 (fr) Procédés et appareils de rapport de mesures de qualité d'expérience pour un service de diffusion-multidiffusion

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019766501

Country of ref document: EP

Effective date: 20201014