hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 5.3.11 memberOfType | <!-- ##################################################################### --> <!-- Definition of memberOfType --> <!-- ##################################################################### --> <xs:complexType name="memberOfType"> <xs:attribute name="shortId" type="shortCRIDType" use="required"/> <xs:attribute name="id... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 5.3.12 messageType | <!-- ##################################################################### --> <!-- Definition of messageType --> <!-- ##################################################################### --> <xs:complexType name="messageType" abstract="true"> <xs:simpleContent> <xs:extension base="xs:string"> <xs:attribute ref="xml:l... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 5.3.13 programmeType | <!-- ##################################################################### --> <!-- Definition of programmeType --> <!-- ##################################################################### --> <xs:complexType name="programmeType"> <xs:sequence> <xs:group ref="scheduleNameGroup" maxOccurs="unbounded"/> <xs:element nam... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 5.3.14 shortDescriptionType | <!-- ##################################################################### --> <!-- Definition of shortDescriptionType --> <!-- ##################################################################### --> <xs:complexType name="shortDescriptionType"> <xs:simpleContent> <xs:restriction base="messageType"> <xs:maxLength valu... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 5.3.15 shortNameType | <!-- ##################################################################### --> <!-- Definition of shortNameType --> <!-- ##################################################################### --> <xs:complexType name="shortNameType"> <xs:simpleContent> <xs:restriction base="messageType"> <xs:maxLength value="8"/> </xs:r... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 5.3.16 simulcastType | <!-- ##################################################################### --> <!-- Definition of simulcastType --> <!-- ##################################################################### --> <xs:complexType name="simulcastType"> <xs:attribute name="system" type="systemType" use="required"/> <xs:attribute name="id" ... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 5.4 Schema groups | |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 5.4.1 descriptionGroup | <!-- ##################################################################### --> <!-- Definition of descriptionGroup --> <!-- ##################################################################### --> <xs:group name="descriptionGroup"> <xs:sequence> <xs:element name="shortDescription" type="shortDescriptionType" minOccurs... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 5.4.2 scheduleNameGroup | <!-- ##################################################################### --> <!-- Definition of scheduleNameGroup --> <!-- ##################################################################### --> <xs:group name="scheduleNameGroup"> <xs:sequence> <xs:element name="shortName" type="shortNameType" minOccurs="0" maxOccu... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 5.4.3 serviceNameGroup | <!-- ##################################################################### --> <!-- Definition of serviceNameGroup --> <!-- ##################################################################### --> <xs:group name="serviceNameGroup"> <xs:sequence> <xs:element name="shortName" type="shortNameType" maxOccurs="unbounded"/>... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 6 Schedules | |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 6.1 Schema types | |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 6.1.1 programmeGroupTypeType | <!-- ##################################################################### --> <!-- Declaration of type programmeGroupTypeType --> <!-- ##################################################################### --> <xs:simpleType name="programmeGroupTypeType"> <xs:restriction base="xs:NMTOKEN"> <xs:enumeration value="series... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 6.1.2 programmeGroupType | <!-- ##################################################################### --> <!-- Declaration of type programmeGroupType --> <!-- ##################################################################### --> <xs:complexType name="programmeGroupType"> <xs:sequence> <xs:group ref="epg:scheduleNameGroup" maxOccurs="unbounde... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 6.1.3 programmeGroupsType | <!-- ##################################################################### --> <!-- Declaration of type programmeGroupsType --> <!-- ##################################################################### --> <xs:complexType name="programmeGroupsType"> <xs:sequence> <xs:element name="programmeGroup" type="programmeGroupT... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 6.1.4 scheduleType | <!-- ##################################################################### --> <!-- Declaration of type scheduleType --> <!-- ##################################################################### --> <xs:complexType name="scheduleType"> <xs:sequence> <xs:element name="scope" minOccurs="0"> <xs:complexType> <xs:sequence... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 6.1.5 alternateSourceType | <!-- ##################################################################### --> <!-- Declaration of type alternateSourceType --> <!-- ##################################################################### --> <xs:complexType name="alternateSourceType"> <xs:attribute name="protocol" default="URL"> <xs:simpleType> <xs:rest... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 6.2 epg | <!-- ##################################################################### --> <!-- Declaration of element epg --> <!-- ##################################################################### --> <xs:element name="epg"> <xs:complexType> <xs:choice minOccurs="0" maxOccurs="unbounded"> <xs:element name="programmeGroups" ty... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 7 Service Information | |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 7.1 Schema types | |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 7.1.1 frequencyType | <!-- ##################################################################### --> <!-- Declaration of type frequencyType --> <!-- ##################################################################### --> <xs:complexType name="frequencyType"> <xs:attribute name="type" default="primary"> <xs:simpleType> <xs:restriction base... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 7.1.2 formatType | <!-- ##################################################################### --> <!-- Declaration of type formatType --> <!-- ##################################################################### --> <xs:simpleType name="formatType"> <xs:restriction base="xs:NMTOKEN"> <xs:enumeration value="audio"/> <xs:enumeration value... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 7.1.3 extFormatType | <!-- ##################################################################### --> <!-- Declaration of type extFormatType --> <!-- ##################################################################### --> <xs:simpleType name="extFormatType"> <xs:restriction base="xs:string"> <xs:whiteSpace value="collapse"/> <xs:pattern va... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 7.1.4 serviceIDType | <!-- ##################################################################### --> <!-- Declaration of type serviceIDType --> <!-- ##################################################################### --> <xs:complexType name="serviceIDType"> <xs:attribute name="id" type="epg:contentIDType" use="required"/> <xs:attribute n... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 7.1.5 serviceType | <!-- ##################################################################### --> <!-- Declaration of type serviceType --> <!-- ##################################################################### --> <xs:complexType name="serviceType"> <xs:sequence> <xs:element name="serviceID" type="serviceIDType" maxOccurs="unbounded"... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 7.1.6 ensembleType | <!-- ##################################################################### --> <!-- Declaration of type ensembleType --> <!-- ##################################################################### --> <xs:complexType name="ensembleType"> <xs:sequence> <xs:group ref="epg:serviceNameGroup" maxOccurs="unbounded"/> <xs:elem... |
d017231ecb3d5f0c06e6ef89aba1f738 | 102 818 | 7.2 serviceInformation | <!-- ##################################################################### --> <!-- Declaration of element serviceInformation --> <!-- ##################################################################### --> <xs:element name="serviceInformation"> <xs:annotation> <xs:documentation xml:lang="en">Service information incl... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 1 Scope | The present document defines a modular extension to GEM [1] which defines how the recording and playback of digital video (and audio) content is integrated with the GEM platform. The present document is firstly intended to be used by entities writing terminal specifications and/or standards that extend a GEM terminal s... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 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... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 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 819: "Digital Video Broadcasting (DVB); G... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 3 Definitions and abbreviations | |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 102 819 [1] and the following apply: GEM recording specification: complete specification that extends the present document to create complete specification of how to integrate digital video (and audio) recording and playback with GEM termin... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in in ES 201 812 [2], TS 102 812 [3] and the following apply: AIT Application Information Table API Application Program Interface DSMCC Digital Storage Media Command and Control DVB Digital Video Broadcasting DVR Digital Video Recorder GEM Globally Execu... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 4 Conventions | Where modifications to other documents are defined by quoting text from those other documents and describing how the present document considers that text to be changed, text that the present document adds into the original document is shown underlined and text that the present document removes from the original documen... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 5 General considerations | |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 5.1 Purpose | The present document is not intended, and should not be used, as a complete specification of how to integrate digital video (and audio) recording and playback with GEM terminal specifications. It is a framework upon which such a complete specification (known as a GEM recording specification) can be created. ETSI ETSI T... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 5.2 Full conformance with the present document | To be fully conformant with the present document, it is required that GEM recording specifications be conformant with all normative requirements of one specification from each of the following two lists. Table 1: MHP and GEM terminal specifications Reference Name ES 201 812 [2] MHP 1.0 TS 102 812 [3] MHP 1.1 TS 102 819... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 6 Recording and playback process | Implementations of the present document shall perform the following as part of their process for recording and playback. |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 6.1 Managing scheduled recordings | The process for managing scheduled recordings shall include the following activities: 1) Maintaining a list of recording requests which remain in the pending state (PENDING_WITH_CONFLICT_STATE or PENDING_WITHOUT_CONFLICT_STATE). NOTE 1: GEM recording specifications may define mechanisms for automatically removing reque... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 6.2 The recording process | The recording process shall include the following activities: 1) Identifying which recordable streams shall be recorded. If the specification of the recording request identifies specific streams then those are the ones which shall be recorded. If the specification of the recording request does not identify specific str... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 6.2.1 Segmented Recordings | GEM recording terminal devices shall make a best effort to record as much of a recording as possible. If a recording is interrupted, the request shall not transition into FAILED_STATE while content which could be recorded remains available. The device shall start the recording whenever the reason for failure is removed... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 6.2.1.1 Recording without interruption | When a recording begins at a scheduled start time and records through-out all the scheduled content without interruption it is a complete recording. The state transitions of a LeafRecordingRequest associated with a completed recording are as follows: • PENDING_WITH_CONFLICT_STATE or PENDING_WITHOUT_CONFLICT_STATE befor... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 6.2.1.2 Recording with resource interruption | When a recording starts from impulse record key press or the recording request is in the PENDING_WITH_CONFLICT_STATE and one or more resources for the recording are not available, the implementation shall execute the following steps: 1) Set the state to IN_PROGRESS_WITH_ERROR_STATE. 2) Set the value in an Exception to ... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 6.2.1.3 Recording with power interruption | When a scheduled recording starts when the GEM recording terminal device is powered off, but then the device is powered on while the scheduled recording is still in effect the implementation shall execute the following steps: 1) Set the state of the LeafRecordingRequest in accordance with available resources as per cla... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 6.2.1.4 Recording with elementary stream change | When a service is being recorded and an elementary stream changes (e.g. PID), the preferred behavior is for the GEM recording terminal device to follow the change without interrupting the recording. However, this is not a requirement and devices that are not capable of this behaviour are allowed to segment the recordin... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 6.2.1.5 Recording failure | If no part of a recording can be recorded and the LeafRecordingRequest remains in the IN_PROGRESS_WITH_ERROR_STATE throughout the duration of the recording, the device shall execute the following steps: 1) The LeafRecordingRequest is placed in the FAILED_STATE. 2) Set the value in an Exception to be returned by the Lea... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 6.3 Managing completed recordings | The process for managing completed recordings shall include the following activities: 1) maintaining with all completed recordings (COMPLETED_STATE or INCOMPLETE_STATE) the following information as long as the content is retained: - whether the recording is known to be complete or incomplete or whether this is unknown;... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 6.4 Playback of scheduled recordings | |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 6.4.1 Process for playback | Except when the initiating_replay_flag in the Application recording description of any application in the recording is set to "1", the process for playing back scheduled recordings shall include the following activities: 1) starting the playback of recordable streams; 2) starting the playback of recorded AUTOSTART appl... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 6.4.2 Events during playback | During the playback of content recorded as the result of a scheduled recording, the following behaviour shall be supported: • The events generated when playback reaches the start and end of the recorded content shall be specified by the GEM recording specification. ETSI ETSI TS 102 817 V1.1.1 (2007-09) 15 |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 6.5 Timeshift | |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 6.5.1 The recording process | The process for timeshift recording shall include the following activities: 1) Identifying which recordable streams are to be recorded and recording them. NOTE 1: The definitions of which streams are to be recorded in timeshift recording is outside the scope of the present document and should be specified by GEM record... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 6.5.2 Playback | Playback of content recorded in timeshift mode requires a time-shift buffer to be associated with a JMF player or service context. The definition of how and when this association is made is outside the scope of the present document and should be specified by GEM recording specifications. During the playback of content ... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 7 Recording and playback APIs | |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 7.1 Recording and recording management | |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 7.1.1 Overview (informative) | The recording APIs enable applications to perform recordings in 2 different ways: 1) schedule a recording to be performed at some point in the future; 2) record broadcast events in real-time. This may also include the portion of the broadcast event that is in a time-shift buffer. The implementation maintains a database... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 7.1.2 Details | The org.ocap.shared.dvr and the org.ocap.shared.dvr.navigation package shall be supported. In ServiceContextRecordingSpec, GEM recording specifications may make mandatory the otherwise optional feature of storing and recording the contents of the time-shift buffer when the startTime is in the past. |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 7.2 Playback | |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 7.2.1 Overview (informative) | Playback of a recording can be performed in two ways depending on whether or not it is desired to start any applications which may form part of the recording. 1) Calling the select(Service) method of a ServiceContext passing in the RecordedService to be played will select all the service components in the service inclu... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 7.3 Other APIs | |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 7.3.1 Versioning | The properties listed in table 4 and table 5 shall be included in the property set of the java.lang.System class. Thus these properties can be retrieved using java.lang.System.getProperty(). Since this API returns a string, numeric return values shall be encoded as defined by java.lang.Integer.toString(int). Table 4: S... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 7.4.1 Unsigned applications | From RecordingPermission, only RecordingPermission ("read", "own") shall be granted to unsigned applications. 7.4.2 Signed applications Signed applications by default shall have the same permissions as unsigned applications. Signed applications can additionally request to get more permissions. These permissions are req... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 8 Application signalling | |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 8.1 Application recording description | GEM recording specifications shall define an application recording description sufficient to derive the following: Table 5: Application recording description Function Type scheduled_recording__flag boolean trick_mode_aware_flag boolean time_shift_flag boolean initiating_replay_flag boolean label_count unsigned integer ... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 9 Application model | |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 9.1 Application lifecycle and trick-mode playback | When playback of recorded content has been initiated by selecting a RecordedService, the application model and lifecycle shall be modified as follows: 1) Running applications not explicitly signalled as trick-mode aware (the trick_mode_aware_flag in the Application recording description is set to "1") shall be killed w... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 10 Security | |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 10.1 Introduction (informative) | The present document includes 2 security models governing the ability of applications to operate on recording requests and completed recordings. 1) One model is based on associating attributes with MHP/OCAP applications. These attributes are expressed as Java Permission classes. Certain method calls are protected and t... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 10.2 Permission request file | The DTD of the permission request file defined by the GEM terminal specification shall include at least the following element and associated attributes: <!ELEMENT recordingpermission EMPTY> <!ATTLIST recordingpermission create (true|false) "false" modify (true|false) "false" delete (true|false) "false" cancel (true|fal... |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 11 Minimum receiver requirements | The following requirements shall apply to all GEM recording terminals: 1) At least the following rates of variable speed playback shall be supported: -16x, -8x, -4x, -2x, -1x, 0, 0.5x, 1x, 2x, 4x, 8x, 16x. NOTE: For the -1x rate, it is allowed to only display i-frames. ETSI ETSI TS 102 817 V1.1.1 (2007-09) 23 |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 12 Registry of constants | |
819cc8d024a5b9226af2a5f8ccf885b4 | 102 817 | 12.1 System constants | Table 6 defines the values for the system properties identifying the version of the present document supported by an implementation. Table 6: System Property Values Field Value Major 1 Minor 0 Micro 2 ETSI ETSI TS 102 817 V1.1.1 (2007-09) 24 Annex A (normative): Application recording description GEM recording specifica... |
58fde85b540fade83201877213f2fc52 | 102 759 | 1 Scope | The present document gives the specification of the link between an AMSS generator and an AMSS modulator. |
58fde85b540fade83201877213f2fc52 | 102 759 | 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... |
58fde85b540fade83201877213f2fc52 | 102 759 | 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] ITU-R Radio Regulations. [2] ETSI ES 201 980: "Digita... |
58fde85b540fade83201877213f2fc52 | 102 759 | 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. Not applicable. ETSI Draft ETSI TS 102 759 V1.1.1 (200... |
58fde85b540fade83201877213f2fc52 | 102 759 | 3 Definitions, symbols, abbreviations and conventions | |
58fde85b540fade83201877213f2fc52 | 102 759 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Alternative Frequency Signalling (AFS): feature of the DRM multiplex which allows receivers to automatically re-tune to a frequency offering more reliable reception without a break in the decoded audio AMSS block: 47 bits containing AM... |
58fde85b540fade83201877213f2fc52 | 102 759 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: n An item that can be repeated multiple, n, times |
58fde85b540fade83201877213f2fc52 | 102 759 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AFS Alternative Frequency Signalling AM Amplitude Modulation AMSS AM Signalling System ASDI AMSS Distribution Interface BOOTP BOOT Protocol CRC Cyclic Redundancy Check DCP Distribution and Communication Protocol DEG Data Entity Group DHCP Dyna... |
58fde85b540fade83201877213f2fc52 | 102 759 | 3.4 Conventions | The order of bits and bytes within each description shall use the following notation unless otherwise stated: • in figures, the bit or byte shown in the left hand position is considered to be first; • in tables, the bit or byte shown in the left hand position is considered to be first; • in byte fields, the Most Signif... |
58fde85b540fade83201877213f2fc52 | 102 759 | 4 General description | The AM Signalling System (AMSS) [3] adds a limited amount of service information to analogue broadcasts in the frequency bands below 30 MHz in a complementary way to the Digital Radio Mondiale (DRM) [2] system. It is intended to be used by broadcasters in the transition to all digital transmission by providing labellin... |
58fde85b540fade83201877213f2fc52 | 102 759 | 4.1 System overview | The AMSS Distribution Interface (ASDI) carries a complete description of the AMSS information to be broadcast from the equipment generating the data (the AMSS generator) to the equipment generating an analogue representation of the AMSS data as phase modulation of an AM carrier (the AMSS modulator). It does this in suc... |
58fde85b540fade83201877213f2fc52 | 102 759 | 4.2 System architecture | The protocol stack provided by the Distribution and Communication Protocols (TS 102 821 [5]) is described in figure 1. The AMSS Distribution Interface as described in the present document builds upon the DCP stack, defining the TAG Items to be used and the format of the data carried. The result is a collection of TAG I... |
58fde85b540fade83201877213f2fc52 | 102 759 | 5 TAG Items | Each ASDI Packet consists of a number of TAG Items where each TAG Item carries a single piece of information. When combined, the TAG Items describe one or more AMSS blocks to be transmitted and information about how the data may be cached. Within a single ASDI Packet, each TAG Name shall be unique. No TAG Name may occu... |
58fde85b540fade83201877213f2fc52 | 102 759 | 5.1 Mandatory TAG Items | Every ASDI Implementation shall support the TAG Items detailed in table 1. Table 1: Mandatory TAG Items TAG Name (ASCII) TAG Length (bits) TAG Value *ptr 64 Control TAG Item "Protocol Type and Revision"; see the DCP definition (TS 102 821 [5]) for format and interpretation details assn 32 ASDI sequence number that iden... |
58fde85b540fade83201877213f2fc52 | 102 759 | 5.1.1 Protocol type and revision (*ptr) | This TAG Item shall be included in every ASDI Packet. TAG Value TAG Length TAG Name Protocol Minor Major A S D I * p r t 0016 0016 0016 0016 0016 0016 0016 4016 ASCII “*ptr” 64 bits 4 bytes 4 bytes 8 bytes Figure 2: Protocol type and revision Protocol: ASCII string "ASDI" (AMSS Distribution Interface). Major revision: ... |
58fde85b540fade83201877213f2fc52 | 102 759 | 5.1.2 ASDI Sequence Number (assn) | This TAG Item shall be included in every ASDI Packet. TAG Value TAG Length TAG Name ASDI Sequence Number a s s n 0000000016 … FFFFFFFF16 ASCII “assn” 32 bits 0016 0016 0016 2016 4 bytes 4 bytes 4 bytes Figure 3: ASDI sequence number ASDI Sequence Number: This value shall be incremented by one by the device generating t... |
58fde85b540fade83201877213f2fc52 | 102 759 | 5.1.3 AMSS block (ablk) | This TAG Item shall be included in every ASDI Packet. TAG Value TAG Length TAG Name Static/ Dynamic AMSS Block a b k l ASCII “ablk” 0 or 48n bits 4 bytes 4 bytes 6n bytes 1 bit 47 bits Figure 4: AMSS block The following fields can be repeated multiple, n, times within the TAG Item's TAG Value section in order to send m... |
58fde85b540fade83201877213f2fc52 | 102 759 | 5.1.4 ASDI asynchronous reset (arst) | This TAG Item is optional within an ASDI TAG Packet. TAG Length TAG Name a r t s ASCII “arst” 4 bytes 4 bytes 0016 0016 0016 0016 0 bits Figure 5: ASDI reset On reception of this TAG, the AMSS modulator is reset to its default state; the input buffer shall be cleared and its output muted (no phase modulation). An "ablk... |
58fde85b540fade83201877213f2fc52 | 102 759 | 5.2 Optional TAG Items | Every ASDI implementation may choose to support the following optional TAG Items. Where one or more of the optional TAG Items are supported, they shall behave as described below. When not supported by an implementation, the presence of these TAG Items shall be ignored. NOTE: Manufacturers should state clearly which opt... |
58fde85b540fade83201877213f2fc52 | 102 759 | 5.2.1 ASDI timestamp (atst) | This TAG Item is optional within an ASDI TAG Packet. See Annex D for more information on the ASDI timestamp. TAG Name TAG Value TAG Length UTCO 64 bits ASCII “atst” a t s t AMSS Timestamp 0016 0016 0016 4016 Milliseconds Seconds 4 bytes 4 bytes 8 bytes 14 bits 38 bits 10 bits Thirds of Milliseconds 2 bits Figure 6: ASD... |
58fde85b540fade83201877213f2fc52 | 102 759 | 5.3 Revision history | Table 4 contains the history of the TAG Item changes of the ASDI Protocol for each new revision. Table 4: Revision history Major revision Minor revision Date Changes from previous to new revision 0 00016 0 00016 2008-02-06 Initial revision Changes to the protocol which will allow existing decoders to still function wil... |
ef04bec73cb659546d832513e1b1ee66 | 102 814 | 1 Scope | The present document defines a wired Home Network Segment (HNS) based on Ethernet 100BASE-T, as described in TR 102 033 [1]. The present document defines how IP traffic for DVB services will be carried over the 100BASE-T Ethernet HNS, and describes how IP QoS is mapped to the Ethernet layer. All the IP related function... |
ef04bec73cb659546d832513e1b1ee66 | 102 814 | 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. • ... |
ef04bec73cb659546d832513e1b1ee66 | 102 814 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CD Collision Detection CoS Class of Service CSMA Carrier-Sense Multiple Access DHCP Dynamic Host Configuration Protocol DIX Digital, Intel and Xerox DNG Delivery Network Gateway DSCP DiffServ CodePoint DVB Digital Video Broadcasting HNCD Home ... |
ef04bec73cb659546d832513e1b1ee66 | 102 814 | 5 Carriage of IP-based traffic | Within the context of the architectural framework specification [1], all the IP-based traffic will transparently be carried over a 100BASE-T Ethernet network. Therefore, the interfaces IPI-1, IPI-2 and IPI-3 on a 100BASE-T Ethernet HNS shall comply with the IETF specification IETF RFC 1042 [6]. The Address Resolution P... |
ef04bec73cb659546d832513e1b1ee66 | 102 814 | 6 Quality of Service (QoS) | The interfaces IPI-1, IPI-2 and IPI-3 on the Ethernet 100BASE-T HNS shall support IEEE 802.1p [3], with defined user priority classes. The IEEE 802.1p field [3] shall be supported in an IEEE 802.1Q [8] compliant Ethernet frame. The marking shall be based on the DiffServ CodePoint (DSCP) marking method [9] as shown in t... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 1 Scope | The present document is one in a series of Technical Specifications produced by the TV-Anytime Forum. These documents establish the fundamental specifications for the services, systems and devices that will conform to the TV-Anytime standard, to a level of detail that is implementable for compliant products and service... |
d209bd456ab8df06bc82ee7012cd4001 | 102 822-3-1 | 2 References |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.