hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 7 Modes of system operation | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 7.0 Introduction | Two modes of operation are depicted in the following clauses allowing the support of HTTPS and the support of unidirectional deployment: • In a regular deployment (clause 7.1), the Multicast rendezvous service is located in the Network and managed by the system operator. • In a co-located deployment (clause 7.2), the M... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 7.1 Regular deployment | The different functional entities involved in a regular deployment are shown in figure 7.1-1 below and conform to the reference architecture specified in clause 5. Figure 7.1-1: Regular deployment workflow The following activities may occur asynchronously at any time: • The Provisioning function may be configured with ... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 7.2 Co-located deployment | The Multicast rendezvous function is co-located with the Multicast gateway. This is depicted in figure 7.2-1 below. Figure 7.2-1: Co-located deployment workflow The following activities may occur asynchronously at any time: • The Multicast rendezvous service shall be configured with a set of basic parameters such as th... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 7.5 Multicast rendezvous service operational procedures | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 7.5.0 Introduction | This clause specifies the interaction at reference point B between the Content playback function and the Multicast rendezvous service (see clause 5.3.9). This is typically a request for a presentation manifest at the start of a presentation session. The presentation manifest URL is typically provided by the Application... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 7.5.1 Request URL format | The request URL shall comply with the following syntax: http[s]://<Host>/<ManifestPath>[?<field>=<value>[&<field>=<value>]*] The elements of the URL are specified in table 7.5.1-1 below. The query parameters carry various optional information useful for the Multicast rendezvous service when redirecting a request from t... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 7.5.2 Operation of Multicast rendezvous service | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 7.5.2.0 General | After receiving the presentation manifest request from the Content playback function (possibly following a third-party CDN broker redirection) the Multicast rendezvous service shall first check that the authentication token AToken is valid (if present). Secondly, the Multicast rendezvous service shall identify the appr... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 7.5.2.1 Redirecting the request to a Multicast gateway | In the case where it accepts a request, the Multicast rendezvous service shall return a 307 Temporary Redirect response. The Location HTTP response header shall be a URL that may include a session identifier and/or a query parameter "piggybacking" a multicast gateway configuration instance document containing the multi... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 7.5.2.2 Refusing the request | In the case where it refuses a request, the Multicast rendezvous service shall respond with one of the following HTTP response status codes: Table 7.5.2.2-1: Multicast rendezvous service error responses HTTP status code and reason phrase Description 401 Unauthorized The requesting Content playback function is not permi... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 7.6.0 Introduction | In some deployments, the presence and details of Multicast gateway instances are not known to the Provisioning function in advance nor, by extension, to the Multicast rendezvous service. In such cases, a Multicast gateway may perform dynamic registration with the Provisioning function as a side-effect of requesting its... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 7.6.1 Request URL format | The request URL at reference point CMR may include a query string that carries extra information, in the form of parameter=value pairs, to facilitate the Multicast rendezvous service redirecting Content playback functions to the appropriate Multicast gateway. This allows dynamic Multicast gateway instances to register ... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8 Data plane operations | 8.0 Introduction |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.0.0 General | This clause describes operation of the data plane of relevant logical functions in the reference architecture, namely at reference points Pin′, Oin, M, A, A′, A″ and L. |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.0.1 Low-latency operation (informative) | Special provision is made in the following clauses to support low-latency operation in the data plane: • When content is pushed into a Multicast server at reference point Pin′, the upload of an ingest object may commence before it has been completely encoded, encrypted and packaged by the sending Content preparation fu... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.1 Operation of Content preparation function | When the multicast server configuration indicates the push content ingest method (see clause 10.2.3.4) for a particular multicast transport session, the Content preparation function shall deliver ingest objects to the Multicast server at reference point Pin′ in a timely manner with respect to the presentation timeline ... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.2 Operation of Content hosting function | The Content hosting function shall make media objects available for retrieval by the Multicast server at reference point Oin in accordance with the DVB DASH profile [10], the HTTP Live Streaming specification [i.5] or equivalent. The Content hosting function shall also make media objects available on an identical basis... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.3 Operation of Multicast server function | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.3.0 Introduction | The primary data plane function of a Multicast server is to receive ingest objects at a Content ingest subfunction and to produce multicast transport objects from a Multicast transmission subfunction. The Content ingest subfunction shall support the reception of each ingest object in the body of an HTTP message at refe... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.3.1 Push-based content ingest | When the multicast server configuration indicates the push content ingest method (see clause 10.2.3.4) for a particular multicast transport session, the Multicast server shall expect ingest objects (for example, MPEG-DASH initialization segments and media segments) to be delivered to it at reference point Pin′ for exam... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.3.2 Pull-based content ingest | When the multicast server configuration indicates the pull content ingest method (see clause 10.2.3.4) for a particular multicast transport session, the Multicast server shall be responsible for retrieving ingest objects (for example, MPEG-DASH initialization segments and media segments) using HTTP(S) via reference poi... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.3.3 Mapping of content ingest URL to multicast transport object URI | For each ingest object received by the Multicast ingest subfunction, the Multicast server shall map the ingest object URL to one or more multicast transport object URIs. Every multicast transport object URI shall be prefixed with the multicast transport object base URI specified for the target multicast transport sessi... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.3.4 Emission of multicast transport objects | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.3.4.0 General | The Multicast transmission subfunction is responsible for formatting received ingest objects into multicast transport objects according to one (or more) multicast media transport protocols and transmitting them as multicast packets at reference point M. The multicast media transport protocol used on each resulting mult... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.3.4.1 Multicast transmission mode | Two multicast transmission modes are defined by the present document and the mode in use for a particular multicast transport session is signalled in the multicast transport session parameters of the multicast server configuration (see clause 10.2.3.5). • In resource transmission mode, one ingest object shall be mapped... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.3.4.2 Forward Error Correction | A multicast media transport protocol may specify the use (optional or otherwise) of Application Level Forward Error Correction (AL-FEC) to assist with the recovery of data carried in the payloads of multicast packets lost by the network in transit. The multicast media transport protocol may specify that AL-FEC repair p... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.3.4.3 Marking of Random Access Points in multicast transport objects | Some multicast transport objects begin with a Random Access Point and are therefore suitable points for a Content playback function to begin decoding the service component. A multicast media transport protocol may specify a means of marking such multicast transport objects, either in the protocol syntax itself, or else... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.3.4.4 In-band carriage of ancillary multicast transport objects | Especially in the case of unidirectional operation mode, certain media objects (including, but not limited to, the presentation manifest and MPEG-DASH initialization segments) may be transmitted repeatedly on one or more multicast transport sessions according to a carousel schedule. For example, this may be used to fac... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.3.4.5 Integrity protection of multicast transport objects | When a multicast transport session is configured to provide an integrity check for multicast transport objects as specified in clause 10.2.3.6, the Multicast server shall provide an integrity check for every multicast transport object that is delivered by that multicast transport session. Generic aspects of integrity p... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.3.4.6 Authenticity assertion of multicast transport objects | When a multicast transport session is configured to provide an authenticity assertion for multicast transport objects as specified in clause 10.2.3.6, the Multicast server shall provide an authenticity assertion for every multicast transport object that is delivered by that multicast transport session. Generic aspects ... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.3.5 Multicast gateway configuration transport session | The Multicast server may generate a special multicast transport session at reference point M to convey metadata and certain types of media objects to a population of Multicast gateway instances. The multicast transport objects conveyed in this multicast gateway configuration transport session may include (but are not l... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.4 Operation of Multicast gateway function | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.4.0 Introduction | The main purpose of a Multicast gateway is to convert multicast transport objects received at reference point M into playback delivery objects, as specified in clause 8.4.3 below. In order to do this, the multicast transport URI is mapped to a playback delivery URL, as specified in clause 8.4.4. The presentation manife... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.4.1 Handling of presentation manifest | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.4.1.0 General | When a Multicast gateway receives an HTTP request for a presentation manifest from the Content playback function at reference point L it may need to acquire a copy of the corresponding HTTP resource if it does not already have a valid, unexpired copy cached locally, either from a multicast transport session (via refere... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.4.1.1 MPEG-DASH presentation manifest manipulation (informative) | The Multicast gateway may reduce the value of MPD/@timeShiftBufferDepth in the presentation manifest if it exceeds the capacity of its internal cache. To ensure that any HTTP redirection from the Multicast rendezvous service is "sticky" for the duration of the presentation session (as described in clause 8.4.1.0 above)... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.4.2 Acquisition of multicast transport objects | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.4.2.0 General | A Multicast gateway may begin acquiring multicast transport objects from a multicast transport session before or after a request for a presentation manifest has been received from a Content playback function at reference point L. To start acquiring multicast transport objects from a particular multicast transport sessi... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.4.2.1 Acquisition of DASH initialization segments | When a Multicast gateway receives an HTTP request for an initialization segment from the Content playback function at reference point L it may need to acquire a copy of the corresponding HTTP resource if it does not already have a valid, unexpired copy cached locally. Initialization segments shall be made available fro... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.4.3 Construction of playback delivery objects | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.4.3.0 General | A Multicast gateway shall attempt to reconstruct playback delivery objects from unicast acquisition at reference point A and/or the multicast data packets it receives at reference point M according to the specification of the multicast media transport protocol signalled in the multicast media transport protocol paramet... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.4.3.1 Fast acquisition of playback session (informative) | To facilitate fast acquisition of a multicast transport session by a Multicast gateway, a Multicast transmission subfunction may mark some multicast transport objects with a Random Access Point marker, as specified in clause 8.3.4.3 above. In such cases, the Multicast gateway may construct a partial playback delivery o... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.4.5 Serving of playback delivery objects | When a Multicast gateway receives an HTTP request for a playback delivery object from the Content playback function at reference point L, it shall ensure that the request corresponds to a service declared in the current multicast gateway configuration document. NOTE 1: The means to determine which service a playback de... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 8.5 Operation of Content playback function | The purpose of a Content playback function is to retrieve and subsequently render media objects from the Content hosting function (via reference point B), some of which may be redirected to a Rendezvous service (also reference point B) and/or a Multicast gateway (via reference point L). Where these interactions comply ... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 9 Unicast repair | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 9.0 Introduction | In cases where a multicast transport object is not received intact by the Multicast reception subfunction by the required deadline and the multicast packet loss could not be repaired by the Multicast gateway using Forward Error Correction, repair of the media object should be attempted using one of the unicast repair p... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 9.1 Triggering unicast repair | The unicast repair procedure may be triggered by the Multicast gateway when any of the following conditions occur: • As soon as packet loss is detected, in the case where no Forward Error Correction is provided as part of the multicast transport session, or when FEC is not used by the Multicast gateway. • If no multica... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 9.2 HTTP-based repair protocol | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 9.2.0 General | The Multicast gateway and the Content hosting function shall support the use of HTTP/1.1 [1] as the unicast repair protocol at reference point A. The Multicast gateway and the Content hosting function may additionally support the use of HTTP/2 as specified in IETF RFC 9113 [34] and/or HTTP/3 as specified in IETF RFC 91... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 9.2.1 Selection of unicast repair base URL | Where more than one unicast repair base URL prefix is indicated for a multicast transport session, the Multicast gateway shall select exactly one of these to perform the unicast repair operation. The basis on which this selection is made is implementation-specific. For example, the following algorithm describes one pos... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 9.2.2 Mapping of multicast transport object URI to unicast repair URL | In order to construct the unicast repair URL for a given multicast transport object, the Multicast gateway shall perform the following operations on the multicast transport object URI: 1) Remove the prefix (if any) indicated by the multicast transport object base URI specified in clause 10.2.3.13. 2) Prepend the unicas... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 9.2.4 Message format | To request a complete media object, the Multicast gateway should use a conventional HTTP GET request. The request URL shall be constructed according to clause 9.2.2 or clause 9.2.3, as appropriate. To request the missing portion(s) of the media object, the Multicast gateway should use the partial HTTP GET request with ... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10 Multicast session configuration | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.0 Introduction | The Multicast server and the Multicast gateway need to have a common view on the set of multicast transport sessions that are currently defined in a deployed system so that the latter knows which multicast transport sessions it can subscribe to, as specified in clause 8.4.2. The concrete embodiment of this logical stat... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.1 Control system arrangement | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.1.1 Configuration of Multicast server | A Multicast server shall be configured using exactly one of the two following methods: 1) Out-of-band pushed configuration method whereby the Network control function delivers a multicast server configuration instance document instance to the Multicast server across reference point CMS. The procedure for this method is... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.1.2 Configuration of Multicast gateway | In a given deployed system, all Multicast gateway instances shall be configured using one or more of following methods: 1) Out-of-band pushed configuration method whereby the Network control function delivers a multicast gateway configuration document instance across reference point CMR. The procedure for this method i... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.0 Overview | NOTE: Only principal elements and selected attributes are depicted. Dotted lines indicate optional elements. Parenthesized italics denote optional attributes. Items in grey are passed through from the multicast server configuration to the multicast gateway configuration but are not used by the Multicast server. Figure ... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.1 Document root element | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.1.0 General | A multicast session configuration instance document describes an intended configuration of multicast sessions and multicast transport sessions in a deployed system. Multicast session configuration instance documents shall comply with the XML schema definitions in annex A. Documents complying with this version of the pr... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.1.1 MulticastServerConfiguration root element | The syntax of the MulticastServerConfiguration element (the root element of a multicast server configuration instance document) is specified in table 10.2.1.1-1 below. Table 10.2.1.1-1: MulticastServerConfiguration element syntax Element or attribute name Use Data type Clause Description MulticastServerConfiguration 10... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.1.2 MulticastGatewayConfiguration root element | The syntax of the MulticastGatewayConfiguration element (the root element of a multicast gateway configuration instance document) is specified in table 10.2.1.2-1 below. Table 10.2.1.2-1: MulticastGatewayConfiguration element syntax Element or attribute name Use Data type Clause Description MulticastGatewayConfiguratio... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.2 Multicast session parameters | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.2.0 General | A multicast session describes a set of multicast transport sessions (specified in clause 10.2.3 below) that convey components of a particular linear service. The multicast session parameters are used by a Multicast server to configure its Multicast transmission subfunction. The multicast session parameters are used by ... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.2.1 MulticastSession element | The syntax of the MulticastSession element is specified in table 10.2.2.1-1 below: Table 10.2.2.1-1: MulticastSession element syntax Element or attribute name Use Data type Clause Description MulticastSession 10.2.2 @serviceIdentifier 1 URI string 10.2.2.0 Service identifier for the logical service with which this sess... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.2.2 Presentation manifest locator | The URLs of presentation manifests related to the linear service shall be conveyed in one or more PresentationManifestLocator child elements of MulticastSession. NOTE 1: This plurality allows presentation manifests of different types that reference a common stream of media objects to be associated with a single set of ... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.2.3 Multicast gateway session reporting parameters | A Multicast gateway may be configured to report metrics for a single multicast session to one or more external Service reporting capture subfunctions. NOTE 1: Reporting on an individual multicast session may be declared independently of reporting for all multicast sessions (see clause 10.2.1.0) and the two levels of re... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3 Multicast transport session parameters | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3.0 General | The parameters of each multicast transport session are captured in a separate MulticastTransportSession child element of MulticastSession. Each such multicast transport session is explicitly associated with service component(s) in the presentation manifest(s), as described in clause 10.2.4 below. ETSI ETSI TS 103 769 V... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3.1 MulticastTransportSession element | The syntax of the MulticastTransportSession element is specified in table 10.2.3.1-1 below: Table 10.2.3.1-1: MulticastTransportSession element syntax Element or attribute name Use Data type Clause Description MulticastTransportSession 10.2.3 Container for multicast transport session parameters. @id 1 Name Token string... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3.2 Multicast transport session identifier | Every multicast transport session shall be assigned an identifier, indicated using the @id attribute of the MulticastTransportSession element. This identifier shall be unique within the scope of the enclosing multicast session. NOTE: This identifier is used, in combination with the @serviceIdentifier attribute of the p... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3.2A Service Class | The type of content carried by a multicast transport session should be signalled using the optional @serviceClass attribute of the MulticastTransportSession element. DVB-I service instances shall be signalled according to clause 9 of [41]. A Multicast gateway should ignore multicast transport sessions described using a... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3.3 Multicast transport session timing | The start time and duration of the multicast transport session may be specified using the @start and @duration attributes respectively of the MulticastTransportSession element. The values of these attributes shall be set in accordance with clause 10.3.1. If desired, the multicast transport session start time shall be i... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3.4 Content ingest method | The means by which ingest objects are to be acquired by the Multicast server may be indicated in a multicast server configuration instance document using the @contentIngestMethod attribute of the MulticastTransportSession element as follows: • Push content ingest method. If ingest objects are to be pushed to the Conten... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3.5 Multicast transmission mode | The means by which a Multicast server is to map ingest objects to multicast transport objects may be indicated in a multicast server configuration instance document using the @transmissionMode attribute of the MulticastTransportSession element as follows: • Resource transmission mode. If one ingest object is mapped to ... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3.6 Multicast transport security mode | The Multicast transmission subfunction may add metadata to each multicast transport object in order to preserve the integrity and/or authenticity of media objects in transit. The transport security mode is indicated using the @transportSecurity attribute of the MulticastTransportSession element as follows: • No securit... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3.7 Multicast transport session idle timeout | The maximum expected inter-packet time interval for a multicast transport session shall be specified in the @sessionIdleTimeout attribute of the MulticastTransportSession element. The value of the attribute shall be expressed in milliseconds. This attribute takes precedence over any other timeout value for the multicas... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3.8 Multicast media transport protocol parameters | The multicast media transport protocol used for this multicast transport session shall be specified using the TransportProtocol child element of the MulticastTransportSession element. This information enables a Multicast gateway to determine whether it can consume the multicast transport session. • The @protocolIdentif... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3.9 Multicast transport endpoint address | The transport endpoint address(es) used for a multicast transport session shall be specified using the EndpointAddress child element of the MulticastTransportSession element. NOTE: Certain multicast media transport protocols may permit a service component to be transmitted on more than one transport address, as specifi... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3.14 In-band carousel of ancillary multicast transport objects | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3.14.0 General | The presence of the optional ObjectCarousel child element of the MulticastTransportSession element indicates that the Multicast server shall compile and transmit a carousel of ancillary multicast transport objects as part of a multicast transport session, as specified in clause 8.3.4.4. The total size of the transport ... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3.14.1 In-band carousel parameters for presentation manifests | If the optional PresentationManifests child element is present, the presentation manifests for all service components declared in this multicast transport session shall be carouselled. • For DASH service components (configured per clause 10.2.4.1), the referenced Media Presentation Description shall be carouselled. • F... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3.14.2 In-band carousel parameters for initialization segments | If the optional InitSegments child element is present, the initialization segments for all service components declared in this multicast transport session shall be carouselled. • For DASH service components (configured per clause 10.2.4.1), only the initialization segment(s) for the currently active Period of the Repre... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.3.14.3 In-band carousel parameters for other resources | If the optional ResourceLocator child element is present, the resource at the URL indicated in the content of that child element shall be carouselled. If the optional @revalidationPeriod attribute is present, the Content ingest subfunction shall revalidate the ancillary ingest object with the Content hosting function a... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.4.0 General | Every multicast transport session shall be associated with one or more service components in a presentation manifest associated with the parent multicast session. Each such association shall be realized by means of a separate ServiceComponentIdentifier child element. The presentation manifest shall be referenced by ass... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.4.1 Service component identification for DASH presentations | In the case where the referenced presentation manifest is a DASH Media Presentation Description (MPD) [i.2], the @xsi:type attribute of the ServiceComponentIdentifier element shall be set to the value DASHComponentIdentifier Type. The syntax of this schema type is specified in table 10.2.4.1-1 below. Table 10.2.4.1-1: ... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.4.2 Service component identification for HLS presentations | In the case where the referenced presentation manifest is an HLS Master Playlist (.m3u8) [i.5], the @xsi:type attribute of the ServiceComponentIdentifier element shall be set to the value HLSComponentIdentifierType. The syntax of this schema type is specified in table 10.2.4.2-1 below. Table 10.2.4.2-1: HLSComponentIde... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.5 Multicast gateway configuration transport session parameters | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.5.0 General | In the case where the population of Multicast gateway instances is configured using the in-band configuration method at reference point M specified in clause 8.3.5 and clause 10.4.5, one or more MulticastGatewayConfiguration TransportSession elements shall be present in the multicast server configuration instance docum... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.5.1 MulticastGatewayConfigurationTransportSession element | The syntax of the MulticastGatewayConfigurationTransportSession element is specified in table 10.2.5.1-1 below. The semantics of the attributes and child elements are identical to the corresponding attributes and child elements of the MulticastTransportSession element specified in clause 10.2.3. Table 10.2.5.1-1: Multi... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.2.5.2 Multicast session configuration macro expansion | In the case where the Multicast gateway is configured by means of the in-band configuration method specified in clause 10.1.2, the Multicast server is responsible for generating one or more multicast gateway configurations based on its current multicast server configuration. In some deployments, the URLs of objects req... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.3 Life-cycle of multicast transport sessions | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.3.0 General | Individual multicast transport sessions in the multicast session configuration are in one of two states: • In the active state, multicast media transport protocol packets may be transmitted by the Multicast server according to the current set of parameters specifying that multicast transport session. • In the inactive ... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.3.1 Timed activation of multicast transport session | A multicast session configuration document may include parameters specifying a start time and/or duration for any of the multicast transport sessions it describes, as specified in clause 10.2.3.3. In the general case, a multicast transport session shall become active in the deployed system at the indicated start time. ... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.3.2 Manual (de)activation of multicast transport session | Regardless of whether a start time and duration has been specified in the current multicast session configuration document, a multicast transport session may be activated by the procedure specified in clause 10.4.3.1 and deactivated by the procedure specified in clause 10.4.3.2. In both cases, the multicast transport s... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.4 Configuration and control procedures | |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.4.0 General | The procedures for configuring and controlling system functions at reference points CMS and CMR shall use HTTP request and response messages, as specified in IETF RFC 9110 [2]. The use of TLS [7] to secure the interactions is recommended. Implementations shall support at least HTTP/1.1 [1] and may additionally support ... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.4.1 Error responses | When an error occurs as the result of a request at reference point CMS or CMR, the most appropriate status code from table 10.4.1-1 below shall be returned to the requestor: Table 10.4.1-1: HTTP error response status codes Response status code and reason phrase Applicable methods Summary description Normative specifica... |
890aa8b91864c4a2d64f76c40ff5f123 | 103 769 | 10.4.2 Multicast server configuration procedures |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.