Tech-invite  3GPPspace  IETFspace
◀  ▶  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 26.247  Word version:  18.4.0

Top   Top   Up   Prev   Next
0f…   4   5…   6…   7…   8…   9…   10…   11…   12…   13…   14…   15   A…   B…   C…   D…   F…   K…   L…   M… 
F OMA DM QoE Management Object  G File format extensions for 3GP-DASH support  G.1 Introduction  H MIME type registration for MPD  H.1 MPD MIME type  H.2 MPD delta MIME type  I Signalling of DASH AVP values for QoS handling in the PCC  J MIME type registration for QoE reports  J.1 Introduction  J.2 MIME type and subtype 
...

 

F (Normative)  OMA DM QoE Management Object  p. 120

As an alternative to configuring the QoE reporting for each session via MPD, OMA-DM can be used to specify the QoE configuration. If such an OMA-DM QoE configuration has been specified, it shall be evaluated by the client for all subsequent sessions.
For the OMA-DM QoE configuration the parameters are specified according to the following Managed Object (MO), and represents the same information as specified in clauses 10.4 and 10.5. Version numbering is included for possible extension of the MO.
The Management Object Identifier shall be: urn:oma:mo:ext-3gpp-pss-dash-qoe:1.0.
Protocol compatibility: 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 [22].
The nodes and leaf objects as provided in Figure F.1 shall be contained under the 3GPP_PSS_DASH_QOE node if a client supports the feature described in this clause.
Copy of original 3GPP image for 3GPP TS 26.247, Fig. F.1: Nodes and leaf objects
Figure F.1: Nodes and leaf objects
(⇒ copy of original 3GPP image)
Up
Node: /<X>
This interior node specifies the unique object id of a QoE metrics management object. The purpose of this interior node is to group together the parameters of a single object.
  • Occurrence: ZeroOrOne
  • Format: node
  • Minimum Access Types: Get
The following interior nodes shall be contained if the client supports the QoE Management Object.
/<X>/Enabled
This leaf indicates if QoE reporting is requested by the provider.
  • Occurrence: One
  • Format: bool
  • Minimum Access Types: Get
/<X>/Servers
This leaf contains a space-separated list of servers to which the QoE reports are transmitted. It is URI addresses, e.g. http://qoeserver.operator.com. In case of multiple servers, the client randomly selects one of the servers from the list, with uniform distribution.
  • Occurrence: One
  • Format: chr
  • Minimum Access Types: Get
  • Values: URI of the servers to receive the QoE report.
/<X>/APN
This leaf contains the Access Point Name that should be used for establishing the PDP context on which the QoE metric reports will be transmitted. This may be used to ensure that no costs are charged for QoE metrics reporting. If this leaf is not defined then any QoE reporting is done over the default access point.
  • Occurrence: ZeroOrOne
  • Format: chr
  • Minimum Access Types: Get
  • Values: The Access Point Name
/<X>/Format
This leaf specifies the format of the report. If this leaf is not defined the QoE reports shall be sent uncompressed.
  • Occurrence: ZeroOrOne
  • Format: chr
  • Minimum Access Types: Get
  • Values: "uncompressed", "gzip"
/<X>/Interval
This leaf specifies how often QoE reports shall be sent. If this leaf is not defined only one QoE report shall be sent after the complete session.
  • Occurrence: ZeroOrOne
  • Format: int
  • Minimum Access Types: Get
  • Values: seconds
/<X>/SamplePercentage
This leaf specifies the percentage of sessions for which QoE metrics shall be reported. The client evaluates a random number at start of each session to determine if reporting shall be done for the specific session. If this leaf is not defined QoE reports are sent for every session.
  • Occurrence: ZeroOrOne
  • Format: float
  • Minimum Access Types: Get
  • Values: 0.0-100.0.
/<X>/StartTime
This leaf specifies when collection of QoE metrics shall start. It is specified in seconds and is relative to the start of the session. If this leaf is not defined, the QoE collection shall be done from the start of the session.
  • Occurrence: ZeroOrOne
  • Format: int
  • Minimum Access Types: Get
  • Values: seconds
/<X>/Duration
This leaf specifies for how long QoE collection shall be done. It is specified in seconds and is relative to the start time of QoE collection. If this leaf is not defined QoE collection shall be done until the end of the session.
  • Occurrence: ZeroOrOne
  • Format: int
  • Minimum Access Types: Get
  • Values: seconds.
/<X>/Metrics
This leaf specifies a list of white-space separated metrics which shall be reported, and follows the same syntax as specified for the "@metrics" attribute in Table 32. If this leaf is not defined no QoE reporting shall be done.
  • Occurrence: ZeroOrOne
  • Format: chr
  • Minimum Access Types: Get
  • Values: Metrics as specified in clause 10.4.
/<X>/StreamingSourceFilter
This leaf controls the Media Presentations for which QoE metrics are collected and reported. The filter is defined as a URL pattern. Each URL pattern is represented by a POSIX regular expression as specified by IEEE Std 1003.1-2008 [52].
If the MPD URL of a Media Presentation does not match any of the regular expressions as provided by the URL patterns in the StreamingSourceFilter values, then reporting is disabled and the DASH client shall not report the requested QoE metrics for that Media Presentation. If no StreamingSourceFilter leaf is present, then reporting is enabled for any Media Presentation.
  • Occurrence: ZeroOrMore
  • Format: chr
  • Minimum Access Types: Get
  • Values: a POSIX regular expression providing the URL pattern.
/<X> /<LocationFilter>
This interior node specifies any location filters.
  • Occurrence: ZeroOrOne
  • Format: node
  • Minimum Access Types: Get
/<X>/<LocationFilter>/CellList
This leaf specifies a list of cellIDs.
  • Occurrence: ZeroOrOne
  • Format: chr
  • Minimum Access Types: Get
  • Values: a list of ECGI or CGI.
/<X>/<LocationFilter>/PolygonList
This leaf specifies a list of shapes defined as 'Polygon' by OMA MLP [51].
  • Occurrence: ZeroOrOne
  • Format: chr
  • Minimum Access Types: Get
  • Values: a list of 'Polygon' defined by OMA MLP [51].
/<X>/<LocationFilter>/Polygon_Conf_Level
This leaf indicates the probability in percent that the DASH client is located in the corresponding polygon area specified by leaf 'PolygonList'. It is defined as 'lev_conf' by OMA MLP. If not present, it has default value of 60.
  • Occurrence: ZeroOrOne
  • Format: int
  • Minimum Access Types: Get
  • Values: 'lev_conf' defined by OMA MLP [51].
/<X>/<LocationFilter>/CircularAreaList
This leaf specifies a list of shapes defined as 'CircularArea' by OMA MLP [51].
  • Occurrence: ZeroOrOne
  • Format: chr
  • Minimum Access Types: Get
  • Values: a list of 'CircularArea' defined by OMA MLP [51].
/<X>/<LocationFilter>/Circular_Conf_Level
This leaf indicates the probability in percent that the DASH client is located in the corresponding circular area specified by leaf 'CircularAreaList'. It is defined as 'lev_conf' by OMA MLP. If not present, it has default value of 60.
  • Occurrence: ZeroOrOne
  • Format: int
  • Minimum Access Types: Get
  • Values: 'lev_conf' defined by OMA MLP [51].
/<X>/Ext
The Ext node is an interior node where the vendor specific information can be placed (vendor includes application vendor, device vendor etc.). Usually the vendor extension is identified by 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.
  • Occurrence: ZeroOrOne
  • Format: node
  • Minimum Access Types: Get
Up

G (Normative)  File format extensions for 3GP-DASH support  p. 125

G.1  Introduction  p. 125

This clause documents extensions to the ISO Base Media File Format [11] for the support of 3GPP DASH.
All extensions are documented in [11].

G.2  Void

G.3  Void

G.4  Void

G.5  Void

G.6  Void

H (Normative)  MIME type registration for MPD  p. 126

H.1  MPD MIME type  p. 126

H.1.1  Introduction  p. 126

The MIME type of the MPD is registered and available at the registry at http://www.iana.org/assignments/media-types/application. For formal registration, refer to Annex C of ISO/IEC 23009-1 [43].

H.1.2  Void

H.1.3  Void

H.2  MPD delta MIME type  p. 126

H.2.1  Introduction  p. 126

This clause provides the formal MIME type registration for the MPD delta. The MIME type is registered with IANA and available at http://www.iana.org/assignments/media-types/application/dashdelta.

H.2.2  MIME type and subtype  p. 126

The MIME type and subtype are defined as follows:
Up

I  Signalling of DASH AVP values for QoS handling in the PCC  p. 128

The PCC architecture is defined in TS 23.203 and provides the Rx reference point, which enables the application layer to authorize a specific usage. In this architecture the DASH HTTP streaming server or any other function in the HTTP streaming path (e.g. an HTTP proxy) can act as Application Function and interact with the PCRF via the Rx reference point for QoS control. It is assumed here that the AF has knowledge of the application type and of the MPD.
The relevant AVPs are the ones enabling the PCRF to establish bearers with correct characteristics for DASH users. The AVPs are defined in TS 29.214. The further PCRF mapping from AVP to IP QoS parameter mapping is defined in TS 29.213.
AVP Value Comment
AF-Application-Identifier"DASH"Allows to signal the DASH based application hence giving the opportunity to enforce application specific policies.
Max-Requested-Bandwidth-DL
(NOTE 1)		B1B1 = sum of all MPD@maxBandwidth (see clause 8.4.3.3) of all media components simultaneously (not mutually exclusive) selectable by the DASH client plus HTTP/TCP/IP overhead and TCP messages for flow control.
If this attribute is not present then B1 = sum of MPD@bandwidth attributes of all media components of the available media presentation corresponding to representations or subrepresentations with highest bandwidth simultaneously selectable (not mutually exclusive) by the DASH client plus HTTP/TCP/IP overhead and TCP messages for flow control.
Max-Requested-Bandwidth-UL
(NOTE 1)		FFSFor Further Study. If included, should be greater than or equal to Min-Requested-Bandwidth-UL.
Min-Requested-Bandwidth-DL
(NOTE 1)		B2B2 = sum of all MPD@minBandwidth (see clause 8.4.3.3) of all media components simultaneously (not mutually exclusive) selectable by the DASH client plus HTTP/TCP/IP overhead and TCP messages for flow control.
If this attribute is not present then
B2 = sum of MPD@bandwidth attributes of all media components of the available media presentation corresponding to representations or subrepresentations with lowest bandwidth simultaneously (not mutually exclusive) selectable by the DASH client plus HTTP/TCP/IP overhead and TCP messages for flow control.
Min-Requested-Bandwidth-UL
(NOTE 1)		FFSFor Further Study. Enough bitrate to cover TCP and HTTP GET requests.
Flow-Description AVP
(NOTE 1)		IP addresses and ports
NOTE 1:
AVPs provided within the Media-Component-Description AVP, except Flow-Description AVP that is included within the Media-Sub-Component AVP. Omitted AVPs are not relevant for this functionality.
Up

J (Normative)  MIME type registration for QoE reports  p. 129

J.1  Introduction  p. 129

This Annex provides the formal MIME-type registration for "application/3gpdash-qoe-report+xml" that identifies XML documents following the schema "urn:3gpp:metadata:2011:HSD:receptionreport" defined in clause 10.6.2. It is referenced from the registry at http://www.iana.org/.

J.2  MIME type and subtype  p. 129

Up

Up   Top   ToC