hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
39654675b83791df5e95eafe093f127f | 102 822-5-2 | 8.3 Case of RMPI bound to scrambled content | |
39654675b83791df5e95eafe093f127f | 102 822-5-2 | 8.3.1 Prior to Domain Acquisition | For scrambled content, the proposed binding process is as follows: 1) Compute a Message Authentication MAC_B over RMPI-MB, the clear content scrambling keys (SK) and content identifier: MAC_MB = MAC{K_AP}(RMPI-MB||CID||SK) 2) Encipher scrambling keys SK using a proprietary key K_CP. 3) Build the content license CL_B th... |
39654675b83791df5e95eafe093f127f | 102 822-5-2 | 8.3.2 In the Acquisition Point | Once the CA/DRM hands over control of content to TVA RMP system, the Acquisition Point processes the license as follows: 1) Decipher the scrambling keys and check the MAC. If the verification fails, this means RMPI and or license has been tampered with. 2) Apply scrambling policy as specified in RMPI-MB. 3) Encipher th... |
39654675b83791df5e95eafe093f127f | 102 822-5-2 | 8.3.3 Post Domain Acquisition | To verify the binding, a device from the domain identified in the license processes the license as follows: 1) Decipher scrambling keys using K_CD. 2) Check MAC_MR using K_AD. A failed verification means the license has been tampered with. 3) Test the key to descramble the content. If descrambling is successful, bindin... |
39654675b83791df5e95eafe093f127f | 102 822-5-2 | 8.4 Other cases | 8.4.1 Case of content that is scrambled prior to domain acquisition and in the clear post domain acquisition Content has to be first watermarked with its content identifier CID. Watermarking is required to maintain the secure binding since the content is to be eventually transmitted in the clear. For example, this happ... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 1 Scope | The present document addresses RMPI for Broadcast Applications, made up of RMPI-Micro Broadcast and RMPI-Micro. The present document is a component of the TV-Anytime Rights Management and Protection system suite of specifications. The present document provides the semantics, syntax and encoding for the usage rights, co... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 822-1: "Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 1: Benchmark Features". [2] ETSI TS 102 822-2: "Broadcast and On-line Service... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 3 Definitions and abbreviations | |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: compliance body: legal entity that adopts the specification and enforces a compliance regime conditions: limitations on rights grant: combination of one principal, one or more rights and zero or more conditions principals: entities tha... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AES Advanced Encryption Standard bslbf bit string left bit first CA Conditional Access CCI Copy Control Information CSA Common Scrambling Algorithm DRM Digital Rights Management DVB The Digital Video Broadcasting Project HD High Definition HDC... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 4 Design principles and requirements | |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 4.1 Positive assertion of rights | In TV-Anytime RMPI-MB rights are positively asserted and never implied. These rights are granted to the RMP System and not to a person. When a right is exercised, asserted conditions are validated. If those asserted conditions are not met then the right cannot be exercised, e.g. a user could hit pause without asking fo... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 4.2 Operational approach | The RMPI-MB and RMPI-M focus on the usage of content as opposed to the movement of content. As a consequence there is no notion of copy within the secure RMP-compliant domain as only those principals that have been granted rights to use the content are given access to the content under the conditions expressed in RMPI-... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 4.3 Compliance | TV-Anytime RMP does not mandate specific implementations or compliance and robustness rules. There are certain parameters in the present document that are left for assignment by the compliance bodies; for example geographic control, RMP domain identifier, single point of control identifier and security level. It is ant... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 5 RMPI - Micro Broadcast and RMPI - Micro semantics | |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 5.1 Principals | Table 1 gives the principals that can be used by a broadcaster when granting rights with RMPI-MB and RMPI-M. Table 1: Principals being used by broadcasters Principal Definition Receiving Domain The receiving domain is the first TVA RMP-compliant domain that receives the content and associated RMPI-MB via broadcast. Onc... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 5.2 Rights | The set of rights listed in table 2, depending on their applied conditions, can be used to enable users to access content via a range of devices under a variety of different usage models. Note that terms PLAY and EXPORT below can both be used to enable content viewing, but under different consumption environments or co... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 5.3 Conditions | Table 3 gives the conditions that can be used by a broadcaster when granting rights with RMPI-MB and RMPI-M. Table 3: Conditions Condition Description Rights to which condition is applicable Geographical Control This condition limits the use of a right to within one or more specified territories. The granularity of ter... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 5.4 Ancillary RMPI-MB and ancillary RMPI-M | Ancillary RMPI-MB and ancillary RMPI-M (table 4) do not convey usage rules or conditions, but carry further information that is required when handling the content. Table 4: Ancillary RMPI-MB and ancillary RMPI-M Ancillary RMPI-MB and ancillary RMPI-M Information to be conveyed Intent Scrambling Control This is to contr... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 6 Syntax and encoding for RMPI-MB and RMPI-M | |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 6.1 Introduction | The syntax and encoding for the RMPI-MB and RMPI-M payload is given below. The payload describes the minimum set of usage rights and rules that can be conveyed alongside a digital television broadcast. It is composed of at most four grants including: • A grant for the "Receiving Domain" that signals the rights and cond... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 6.2 RMPI-MB and RMPI-M payload | Table 5 describes the fixed encoding of RMPI-MB and RMPI-M. ETSI ETSI TS 102 822-5-1 V1.7.1 (2012-12) 14 Table 5: RMPI-MB and RMPI-M codes Syntax No. of bits Identifier RMPI_MB_and_RMPI_M_payload (){ Ancillary RMPI RMPI_type_flag 1 bslbf Version_of_RMPI 15 bslbf Origin_of_RMPI 128 bslbf Scrambling_control 1 bslbf Ciphe... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 6.3 Ancillary RMPI | RMPI_type_flag: This 1-bit field indicates the type of RMPI carried (table 6). Table 6: RMPI_type_flag Value Meaning 0 RMPI-Micro Broadcast (RMPI-MB) 1 RMPI-Micro (RMPI-M) Version_of_RMPI: This 15-bit field is used to identify the version of RMPI for future-proofing purposes. 15 bits for version to be allocated by comp... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 6.4 Rights | Extend_rights_flag: This 1-bit field indicates whether the Extend Rights right is granted (table 9). Table 9: Extend_rights_flag Value Meaning 0 Extend Rights right is not granted. 1 Extend Rights right is granted. ETSI ETSI TS 102 822-5-1 V1.7.1 (2012-12) 16 Play_right_flag: This 1-bit field indicates whether the Play... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 6.5 Conditions and identifiers | Unless otherwise stated, conditions apply to Play, Analogue Export, Digital Export SD and Digital Export HD. If conditions are not asserted they do not apply. Security_level: This 2-bit field indicates the minimum security level required to exercise the right. Security levels are to be defined by the compliance body. N... |
100bcbf57916ac6b3774025b189b046e | 102 822-5-1 | 7 RMPI-MB and RMPI-M lifecycle | RMPI-MB is transmitted in conjunction with the broadcast signal. At the time of reception in the end user's TVA RMP Domain it is converted to RMPI-M. If RMPI-MB "scrambling_control" is set to 1, then transition from RMPI-MB to RMPI-M shall be synchronized with the rescrambling of the content. Rights that are granted to... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 1 Scope | RMPI for Broadcast Applications, made up of RMPI-Micro Broadcast and RMPI-Micro, is a component of the TV-Anytime Rights Management and Protection system suite of specifications. The present document provides the semantics, syntax and encoding for the usage rights, controls and permissions to be conveyed in RMPI-MB and... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • ... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 3 Definitions and abbreviations | |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: compliance body: legal entity that adopts the specification and enforces a compliance regime conditions: limitations on rights grant: combination of one principal, one or more rights and zero or more conditions principals: entities tha... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AES Advanced Encryption Standard bslbf bit string left bit first CA Conditional Access CCI Copy Control Information CSA Common Scrambling Algorithm DRM Digital Rights Management DVB The Digital Video Broadcasting Project HD High Definition HDC... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 4 Design principles and requirements | |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 4.1 Positive assertion of rights | In TV-Anytime RMPI-MB rights are positively asserted and never implied. These rights are granted to the RMP System and not to a person. When a right is exercised, asserted conditions are validated. If those asserted conditions are not met then the right cannot be exercised, e.g. a user could hit pause without asking fo... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 4.2 Operational approach | The RMPI-MB and RMPI-M focus on the usage of content as opposed to the movement of content. As a consequence there is no notion of copy within the secure RMP-compliant domain as only those principals that have been granted rights to use the content are given access to the content under the conditions expressed in RMPI-... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 4.3 Compliance | TV-Anytime RMP does not mandate specific implementations or compliance and robustness rules. There are certain parameters in the specification that are left for assignment by the compliance bodies; for example geographic control, RMP domain identifier, single point of control identifier and security level. It is antici... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 5 RMPI - Micro Broadcast and RMPI - Micro semantics | |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 5.1 Principals | Table 1 gives the Principals that can be used by a broadcaster when granting rights with RMPI-MB and RMPI-M. Table 1: Principals being used by broadcasters Principal Definition Receiving Domain The receiving domain is the first TVA RMP-compliant domain that receives the content and associated RMPI-MB via broadcast. Onc... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 5.2 Rights | The set of rights listed in table 2, depending on their applied conditions, can be used to enable users to access content via a range of devices under a variety of different usage models. Note that terms PLAY and EXPORT below can both be used to enable content viewing, but under different consumption environments or co... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 5.3 Conditions | Table 3 gives the Conditions that can be used by a broadcaster when granting rights with RMPI-MB and RMPI-M. Table 3: Conditions Condition Description Rights to which condition is applicable Geographical Control This condition limits the use of a right to within one or more specified territories. The granularity of ter... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 5.4 Ancillary RMPI-MB and ancillary RMPI-M | Ancillary RMPI-MB and ancillary RMPI-M (table 4) do not convey usage rules or conditions, but carry further information that is required when handling the content. Table 4: Ancillary RMPI-MB and ancillary RMPI-M Ancillary RMPI-MB and ancillary RMPI-M Information to be conveyed Intent Scrambling Control No scrambling Ma... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 6 Syntax and encoding for RMPI-MB and RMPI-M | |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 6.1 Introduction | The syntax and encoding for the RMPI-MB and RMPI-M payload is given below. The payload describes the minimum set of usage rights and rules that can be conveyed alongside a digital television broadcast. It is composed of at most four grants including: • A grant for the "Receiving Domain" that signals the rights and cond... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 6.2 RMPI-MB and RMPI-M payload | Table 5 describes the fixed encoding of RMPI-MB and RMPI-M. ETSI ETSI TS 102 822-5 V1.1.1 (2005-03) 14 Table 5: RMPI-MB and RMPI-M codes Syntax No. of bits Identifier RMPI_MB_and_RMPI_M_payload (){ Ancillary RMPI RMPI_type_flag 1 bslbf Version_of_RMPI 15 bslbf Origin_of_RMPI 128 bslbf Scrambling_control 1 bslbf Cipher ... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 6.3 Ancillary RMPI | RMPI_type_flag: This 1-bit field indicates the type of RMPI carried (table 6). Table 6: RMPI_type_flag Value Meaning 0 RMPI-Micro Broadcast (RMPI-MB) 1 RMPI-Micro (RMPI-M) Version_of_RMPI: This 15-bit field is used to identify the version of RMPI for future-proofing purposes. 15 bits for version to be allocated by comp... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 6.4 Rights | Extend_rights_flag: This 1-bit field indicates whether the Extend Rights right is granted (table 9). Table 9: extend_rights_flag Value Meaning 0 Extend Rights right is not granted. 1 Extend Rights right is granted. ETSI ETSI TS 102 822-5 V1.1.1 (2005-03) 16 Play_right_flag: This 1-bit field indicates whether the Play r... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 6.5 Conditions and identifiers | Unless otherwise stated, conditions apply to Play, Analogue Export, Digital Export SD and Digital Export HD. If conditions are not asserted they do not apply. Security_level: This 2-bit field indicates the minimum security level required to exercise the right. Security levels are to be defined by the compliance body. N... |
b2a32c5bf721d4f5a28f7bf78802fb26 | 102 822-5 | 7 RMPI-MB and RMPI-M lifecycle | RMPI-MB is transmitted in conjunction with the broadcast signal. At the time of reception in the end user's TVA RMP Domain it is converted to RMPI-M. If RMPI-MB "scrambling_control" is set to 1, then transition from RMPI-MB to RMPI-M must be synchronized with the rescrambling of the content. Rights that are granted to ... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 1 Scope | The present document defines mechanisms for the delivery of messages which are used by the IPDC over DVB-H network to provide information about forthcoming events; such messages are referred to as Notification messages. The present document specifies the message format, transport and access mechanisms of Notification m... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 102 472: "Digital Video Broadcasting (DVB); I... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI EN 302 304: "Digital Video Broadcasting (DV... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 3 Definitions and abbreviations | |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: channel: end-to-end path over which the data composing the Service Component is delivered Default Notification Channel: channel from which a terminal can retrieve Notification Messages without prior user selection NOTE: A Default Notif... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CBMS Convergence of Broadcast and Mobile Services DVB Digital Video Broadcasting DVB-H DVB-Handheld EDN ESG Default Notification ESG Electronic Service Guide FDT File Delivery Table FLUTE File Delivery over Unidirectional Transport ID IDentifi... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 4 Overview | Notification is a function by which the network provides messages about forthcoming and not predictable events of interest to the terminal or the user. The Notification may lead to subsequent interaction from the user/the terminal. The information carried in the Notification messages can be related to the (DVB) network... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 4.1 Categories of Notification | Based on use case analysis, several Notification delivery mechanisms have been identified, leading to different methods to access them. |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 4.1.1 Default Notification | A Default Notification can be automatically accessed by terminals using the Default Notification Channel in a Broadcast network and should be able to receive these messages without any particular subscription. Registration may be required when the default Notification messages are available over the Interaction network... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 4.1.1.1 Network Default Notification (NDN) | The NDN category includes messages that are relevant at the DVB network level. No user selection is required. All terminals attached to the network can access the messages. Notification messages related to the network are carried over the PDN channels. Messages in NDN category are agnostic to the services described in ... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 4.1.1.2 Platform Default Notification (PDN) | The PDN category includes messages that are relevant in a particular IP Platform. All terminals attached to that IP Platform can receive the messages without user selection. Messages in PDN category are agnostic to the services described in the ESG. Examples of such messages could relate to change of platform configura... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 4.1.1.3 ESG Default Notification (EDN) | The EDN category includes messages that are related to the services described by a given ESG. All terminals using that ESG of a specific ESG provider can receive the EDN messages automatically without user selection. Such Notification messages can be delivered in (one of) the ESG carousels or in a dedicated channel. ED... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 4.1.2 User-selected Notification | User-selected Notifications are messages related to services discovered in the ESG. They are user selected in the sense that the user has to discover and select a service and related Notification components via the ESG. |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 4.1.2.1 Service Related Notification (SRN) | Service Related Notifications are messages related to a specific service described in an ESG (e.g. mobile TV channel). Such Notification messages, when delivered as part of the service session (and preferably in the same DVB-H burst) are referred to as in-band Service Related Notification messages (iSRN). When in-band ... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 4.1.2.2 Notification Service (NS) | A Notification Service is a service consisting in the delivery of Notification messages for consumption by the user. An example of such service is a News service. Such service is described in the ESG and discoverable by the user while searching the ESG. A NS service may require subscription and purchase. |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 4.2 Notification Framework | The Notification framework is the system configuration enabling the delivery of Notification messages according to the categories described in clause 4.1. Figure 1 depicts an instantiation of such framework. ETSI ETSI TS 102 832 V1.2.1 (2010-01) 11 User selected Default Services (examples) News Rich A/V Emergency Platf... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 4.3 Mapping of Notification messages on transport layer | |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 4.3.1 Structure of Notification messages | A Notification Message is an extensible structure composed of several parts needed to support Notification applications. The parts composing the Notification message are: • Generic Notification Message part (clause 6.1.1). • Notification payload. The Notification Message payload is further broken down into: • Applicati... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 4.3.2 Mapping of Notification messages on broadcast transport layer | Depending on the target Notification application and attributes (size, time and synchronization constraints, etc.), the Notification messages can be split and mapped on several transport protocols as described in the sequel. If Notification messages can be delivered without time constraints or with a time constraint co... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 4.3.3 Mapping of Notification messages on interactive transport layer | For services using Notification components not having real time requirements, or when the Broadcast network is not available, the Interaction network can be used to deliver Notification messages. In this case, the Notification messages are carried in the same structure as for the broadcast transport. Notification Messa... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 4.4 Dynamics of the Notification framework | In the Notification framework, a service component carrying Notification messages has a Component ID attached to it. The Component ID is used in the signalling of service components that may need to be consumed concurrently. In case a Notification component is shared among several services, Notification Types are used ... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 5 Architecture | The IP Datacast Architecture document [i.3] defines the reference architecture for Notification services delivered by IP Datacast [i.2] over DVB-H [i.1]. The reference architecture specification is provided to illustrate the way the different components (e.g. audio, video and Notification) in IP Datacast over DVB-H wor... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6 Notification message structure and transport | |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.1 Notification message elements | In this clause the different Notification message parts as well as their fields are described. |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.1.1 Generic Notification Message Part | The generic Notification message part includes information that is to be processed by the Notification framework. This information may also be passed further to the Notification application. The generic Notification message part consists of the following elements. ETSI ETSI TS 102 832 V1.2.1 (2010-01) 17 Table 1: Gener... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.1.2 Notification Message payload | The Notification Message payload is composed of an Application-specific Notification message part and possibly Media objects. The Notification Message payload is intended to be consumed by the target application, resolved from the NotificationType value. |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.1.3 Encapsulation and Aggregation of Notification Messages | Notification messages may be composed of multiple parts. The transport of the Notification message parts may be done separately or as a single object. For the encapsulation of Notification message parts into a single transport object the Multipart/Related MIME format RFC 2387 [3] shall be used. Multiple Notification me... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2 Mapping on transport protocols | A Notification message may be transported in different formats, depending on its size, its components, and on the transport channel in use. Table 5 represents the different formats of the Notification payload as well as the corresponding mappings to the transport protocol. ETSI ETSI TS 102 832 V1.2.1 (2010-01) 21 Table... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.1 Mapping on FLUTE | Notification messages or parts thereof may be transported over FLUTE as transport objects. A FLUTE transport object may also carry several Notification messages aggregated together as defined in clause 6.1. When used FLUTE [i.4] shall be based on TS 102 472 [1] When the Notification message is transported over FLUTE, t... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.1.1 Notification Message description | Upon reception of the FDT, the receiver is able to identify transport objects that carry Notification messages or parts thereof based on the indicated Content-Type as described in table 5. If compression, e.g. gzip, is applied to the transport object then it is indicated by the "Content-Encoding" field in the FDT, as s... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.1.2 Selection and Filtering of Notification Messages | In order to increase efficiency of Notification delivery, the FDT may include information related to a Notification message (or several Notification messages) carried in a transport object. The information in the FDT that can be used to filter and select desired Notification messages are presented: • Service Reference ... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.1.3 Timing Information | The Timing information extension shall conform to the definition given in clause 6.1.1. Table 8: Semantics of timing information when mapping over FLUTE Field Semantics launch_time A value that specifies the NTP value of the intended presentation time of the Notification message. This time may be in the past when a mes... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.2 Mapping on RTP | Notification messages that are tightly synchronized with media streams of a service shall be transported using RTP. When the Notification message is transported over RTP, the generic message elements may be transported in the payload format header, extension header or payload according to table 9. ETSI ETSI TS 102 832 ... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.2.1 RTP Header | Figure 10 describes the RTP packet header as defined by RFC 3550 [4]. The fields of the RTP packet header are used as described in RFC 3550 [4]. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |V=2|P|X| CC |M| PT | sequence number... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.2.2 RTP Payload Format Header | The RTP payload format header has the following format. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | NT | ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | VN | ACT |C| R | NPF | T | HL | +-+-+-+-+-+-+-... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.2.3 Extension headers | The RTP payload format header is extensible and allows for additional information to be included in form of extension headers. The generic format of an extension header is as follows. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.2.4 Fragmentation Packets | Objects that exceed the networks maximum transmission unit (MTU) need to be fragmented before transmission. By fragmenting at the RTP level one need not rely on lower layer fragmentation, e.g. IP. The payload format defines fragmentation of objects into two or more RTP packets. NOTE: Fragmentation on the RTP level shou... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.2.5 SDP Parameters | The Notification component transported over RTP shall be described in the session description (SDP) of the session by a dedicated media line. The Session Description specifies the destination port, media type, clock rate, and other initialization information. The fields in the Session Description Protocol (SDP) are def... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.3 Mapping on Interaction Network protocols | Delivery of Notification messages over the Interaction Network is performed according to the following steps: 1) Discovery: the terminal discovers the access to the desired Notification type . The terminal gets all the necessary information to register and get access to Notification messages of the desired type. 2) Reg... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.3.1 Discovery of Notification access over the Interaction Network | Discovery of Notification access over the Interaction Network follows different mechanisms depending on whether the Notification channels are default ones or user-selected ones. • In case of Default Notification channels, the Notification access over the Interaction Network is signalled in the DefaultNotificationAccess... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.3.2 Registration | When required, the terminal shall perform a registration procedure to enable delivery over the Interaction Network. To cancel the registration the terminal shall perform a De-registration procedure. The registration expires automatically at the indicated expiry time. The registration procedure is performed using HTTP 1... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.3.2.1 Registration and Deregistration Request | The request is directed to the access point indicated by the RegistrationURL discovered from the discovery process. The MIME type of the request shall be "application/vnd.dvb.notif-ia-registration-request+xml". The body of the request contains the following information: a) the registration operation required (e.g. Regi... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.3.2.2 Registration and Deregistration Response | The response to a successful registration or deregistration request shall be an HTTP 200 OK message. In case of a registration request, the response shall include a registration identifier and the expiry time of the registration. The content type of the body shall be "application/vnd.dvb.notif-ia-registration-response+... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.3.3 Delivery of the Notification Message List | In case of Interaction Network delivery, the terminal receives a message that contains either a list of one or more Notification messages that are available for retrieval or a pointer to such a list. The latter configuration can be used in situations where the message is constrained to a maximum size by the transport l... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.3.3.1 Format of Notification Message List | The information provided in the message list is given by table 14. Table 14: Message list fields Field Level Semantics FilterInformation Message list and Message Base64 encoded filter list as described by clause 6.4. StartTime Message list NTP timestamp. Indicates that the delivery list contains Notifications messages ... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.3.3.2 Query format | The parameters associated with the HTTP POST request shall be communicated as key-value pairs following the conventions defined in section 17.13 of HTML 4.01 [10] for submitting HTML form data by the "POST" method using the "application/x-www-form-urlencoded" encoding type. More specifically, once encoded as "applicati... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.3.3.3 Push delivery | When registering to a Notification service, the terminal indicates the type of delivery it wants to have. If the delivery type is supported by the service provider, the registration is performed successfully. For the push delivery, the terminal registers as a receiver and provides its device address. The service provid... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.3.3.4 Poll delivery | In the case the Notification service is available over Poll delivery channel, HTTP POST shall be used for requesting the message list as described in clause 6.2.3.3. The time interval between two consecutive polls shall not be less than the indicated poll period. The Notification service provider may overwrite the poll... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.2.3.4 Retrieval of Notification Messages | After processing the message list, the Notification messages of interest can be retrieved by using the AccessURL available in the acquisition fragment or signalled in a successful registration. In the case the Broadcast content location is signalled in the message list, the terminal may tune into the related Broadcast ... |
db30e140866294d6bd7a32b9baf6f78c | 102 832 | 6.3 Notification object lifecycle | Notifications can be used for various purposes, from simple display of messages (e.g. emergency messages) over software updates to the transport, launch and control of entire interactive applications (e.g. voting buttons). The detailed behaviour of a given Notification application inside the terminal is out of scope of... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.