hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 6.2.6 Format for response | Responses shall be given as a Delivery object as defined in ETSI TS 103 120 [6], clause 10, with JSON-encoded contents as described in table 6.2.6-1 below. ETSI ETSI TS 103 976 V1.5.1 (2025-11) 12 Table 6.2.6-1: ResultRecords Field Format Description M/ C/ O VINtoCommsIDRecord See clause 7.2.3 Used to provide results t... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7 Details for the supported questions | |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.1 Overview | Clause 7 gives a list of questions which are supported by the present document. Clause 7 gives the details that are specific to each of the supported questions. The present document follows the terminology of the ISO 20077 and ISO 20078 series ([1], [2], [3], [4] and [5]) as follows: • The term supported question (in t... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.2 VINtoCommsID request | |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.2.1 Definition | This request provides the communications identifier(s) associated with a given Vehicle Identification Number (VIN). NOTE 1: This question is only applicable to vehicles with manufacturer-issued VINs. NOTE 2: It is sometimes easy to change the IMSI(s) present in a particular vehicle. It is important to take this into ac... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.2.2 Definition of request | The LDTaskObject RequestValues field shall contain a single RequestValue (see ETSI TS 103 120 [6], clause 8.3.5.3) populated as described in table 7.2.2-1 below. Table 7.2.2-1: RequestValue for VINtoCommsID request Field Format FormatType Given as VIN (defined in ETSI TS 103 280 [7], clause 6.57). Value VIN of interest... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.2.3 Definition of response | The response shall provide all communications identifiers which the RPS knows are installed in the vehicle with the given VIN. If StartTime and EndTime were not included in the request, the response indicates current associations. If StartTime and EndTime are both included in the request, the RPS shall provide the comm... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.3 CommsIDtoVIN request | |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.3.1 Definition | This request provides the VIN(s) associated with a given communications identifier. |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.3.2 Definition of request | The LDTaskObject RequestValues field shall contain a single RequestValue (see ETSI TS 103 120 [6], clause 8.3.5.3) populated as described in table 7.3.2-1 below. ETSI ETSI TS 103 976 V1.5.1 (2025-11) 15 Table 7.3.2-1: RequestValue for CommsIDtoVIN request Field Format FormatType One item from table 7.2.3-2. Value Commu... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.3.3 Definition of response | Successful responses shall set the Manifest Specification field (see ETSI TS 103 120 [6], clause 10.2.2) to "TS103976" and provide the response in JSON format within the JSONData field (see ETSI TS 103 120 [6], clause 10). The response shall contain zero or more instances of CommsIDtoVINRecord as shown in table 7.3.3-1... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.4 VINtoLocation request | |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.4.1 Definition | This request gives the location(s) associated with a given VIN at a given time or time range. |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.4.2 Definition of request | The LDTaskObject RequestValues field shall contain a single RequestValue (see ETSI TS 103 120 [6], clause 8.3.5.3) populated as described in table 7.4.2-1 below. Table 7.4.2-1: RequestValue for VINtoLocation request Field Format FormatType Given as VIN, as defined in ETSI TS 103 280 [7], clause 6.57; see also clause 7.... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.4.3 Definition of response | Successful responses shall set the Manifest Specification field (see ETSI TS 103 120 [6], clause 10.2.2) to "TS103976" and provide the response in JSON format within the JSONData field (see ETSI TS 103 120 [6], clause 10). The response shall contain zero or more instances of VINtoLocationRecord that match the query, po... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.5 VINtoUniquePartNumber | |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.5.1 Definition | The request provides the Unique Part Numbers (see clause 3.1) associated with a given VIN, matching the specified Part Type if provided. |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.5.2 Definition of request | The LDTaskObject RequestValues field shall contain a RequestValue (see ETSI TS 103 120 [6], clause 8.3.5.3) populated as described in table 7.5.2-1 below. Table 7.5.2-1: VIN RequestValue Field Format Description M/C/O FormatType FormatType (ETSI TS 103 120 [6], clause 8.3.5.4) Set to indicate the VIN FormatType as defi... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.5.3 Definition of response | The Response shall provide a list of VINtoUniquePartNumberRecords, one for each unique part number associated with that VIN. If the PartType was specified as part of the request, only records matching that PartType shall be returned. If the value "Other" is used, then the field PartTypeFreeText shall be populated. Succ... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.6 UniquePartNumbertoVIN | |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.6.1 Definition | The request is for the VIN(s) which is/are associated with a specified unique part number (and which match the PartType where it is present in the request). ETSI ETSI TS 103 976 V1.5.1 (2025-11) 18 |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.6.2 Definition of request | |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.6.2.1 UniquePartNumber | The LDTaskObject RequestValues field shall contain a RequestValue (see ETSI TS 103 120 [6], clause 8.3.5.3) populated as described in table 7.6.2-1 below. Table 7.6.2-1: UniquePartNumber RequestValue Field Format Description M/C/O FormatType FormatType (ETSI TS 103 120 [6], clause 8.3.5.4) Set to indicate the UniquePar... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.6.2.2 PartType | Optionally, the LDTaskObject RequestValues field may also contain a PartType RequestValue populated as described in table 7.5.2-2. If the PartType is present, results shall only be returned where the relevant Part also matches the specified PartType. |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.6.3 Definition of response | The Response shall provide a list of UniquePartNumbertoVINRecords NOTE: If all systems are functioning correctly, there would only be one VIN associated with a unique part number. However, the request may be used in situations where parts are being cloned or part numbers are not being handled correctly, so it is not co... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.7 VINtoSubscribedServices | |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.7.1 Definition | This request is relating to the subscribed services associated with the VIN. The request is asking about payments made to the RPS for services within a specified time range. If a service was bought as part of the original purchase of the vehicle, then the purchase of the vehicle counts as a the RPS receiving a payment ... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.7.2 Definition of request | The LDTaskObject RequestValues field shall contain a single RequestValue (see ETSI TS 103 120 [6], clause 8.3.5.3) populated as described in table 7.7.2-1 below. Table 7.7.2-1: RequestValue for VINtoSubscribedServices request Field Format Description M/C/O FormatType FormatType (ETSI TS 103 120 [6], clause 8.3.5.4) Set... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.7.3 Definition of response | List of payments for paid-for services, where the RPS is receiving the payment for the service, which are associated with that VIN and where the payment was made during the specified time range. Successful responses shall set the Manifest Specification field (see ETSI TS 103 120 [6], clause 10.2.2) to "TS103976" and pr... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.8 VINtoConnectedDevices | |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.8.1 Definition | This request provides a list of devices that have connected to the vehicle within the given time range. |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.8.2 Definition of request | The LDTaskObject RequestValues field (see ETSI TS 103 120 [6] clause 8.3.5.3) shall contain a VIN RequestValue populated as described in table 7.8.2-1 below. Table 7.8.2-1: VIN RequestValue for VINtoConnectedDevices request Field Format FormatType Given as VIN, as defined in ETSI TS 103 280 [7] clause 6.57; see also cl... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.8.3 Definition of response | The response shall provide a list of any connections made to the vehicle that overlaps with the given time range and shall be provided using the VINtoConnectedDeviceRecord described in table 7.8.3-1. One record shall be made for each connection (i.e. if a device connected multiple times, then multiple records shall be ... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.9 VINtoAllocatedUserAccounts | |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.9.1 Definition | The request is for user account details which are linked to the specified VIN. A user account is defined to be a set of information which is relating to a specific person (who might or might not be the owner of the vehicle) rather than data which relates to a specific vehicle or device. NOTE: There may be one or more u... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.9.2 Definition of request | The LDTask object RequestValues field shall contain a single RequestValue (see ETSI TS 103 120 [6], clause 8.3.5.3) populated as described in table 7.9.2-1 below. Table 7.9.2-1: RequestValue for VINtoAllocatedUserAccount request Field Format Description M/C/O FormatType FormatType (ETSI TS 103 120 [6], clause 8.3.5.4) ... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.9.3 Definition of response | The response is a list of user accounts which are associated with that VIN. If StartTime and EndTime were not included in the request, the response indicates current account information associated with the VIN, if any. If StartTime and EndTime are both included in the request, the RPS shall provide details of accounts ... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.10 VINtoLocationPush request | |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.10.1 Definition | This request gives the location(s) associated with a given VIN. The results are pushed by the RPS to the AO i.e. the delivery of results is initiated by the RPS (not the AO). The results are sent in accordance with these criteria: • The request shall specify a time range. • There are also other criteria which specify w... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.10.2 Definition of request | The LITaskObject structure shall populate the TargetIdentifier field (see ETSI TS 103 120 [6], clause 8.2.6) with a VIN, see table 7.10.2-1 below. The remaining details for populating the LITaskObject are as specified in the workflow profile (ETSI TS 103 120 [6], clause H.5). ETSI ETSI TS 103 976 V1.5.1 (2025-11) 23 Ta... |
7efb7f2865dcd7b22a07b5ce9de12568 | 103 976 | 7.10.3 Definition of response | Successful responses shall set the Manifest Specification field (see ETSI TS 103 120 [6], clause 10). Each response shall contain zero or more instances of VINtoLocationRecord that provide the relevant location information, populated as shown in table 7.4.3-1. ETSI ETSI TS 103 976 V1.5.1 (2025-11) 24 Annex A (normative... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 1 Scope | The present document specifies a Coded Multisource Media Format (CMMF) container. This format is used to support storage and delivery of linear, network or channel coded multisource audio/video media over networks. It also specifies the xCD-1 linear coding type. The present document also includes examples. |
630bb3779e33ebc8586024227b48f59f | 103 973 | 2 References | |
630bb3779e33ebc8586024227b48f59f | 103 973 | 2.1 Normative 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 referenced document (including any amendments) applies. Referenced documents which a... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 2.2 Informative 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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 3 Definition of terms, symbols and abbreviations | |
630bb3779e33ebc8586024227b48f59f | 103 973 | 3.1 Terms | For the purposes of the present document, the following terms apply: bitstream: sequence of bits block: unit of data on which a block-based code is applied NOTE: All coding operations (encoding and decoding) on one block are independent of all coding operations on another block. block coding: coding technique where the... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: ^ Exponentiation: a^b is equivalent to ab ETSI ETSI TS 103 973 V1.2.1 (2026-03) 23 |
630bb3779e33ebc8586024227b48f59f | 103 973 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: Ad-ID Advertising digital Identifier AES Advanced Encryption Standard ASCII American Standard Code for Information Interchange CBC Cipher Block Chaining CDN Content Delivery Network CDP Content Delivery Protocol CFB Cipher FeedBack CI Configur... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 4 Overview | |
630bb3779e33ebc8586024227b48f59f | 103 973 | 4.0 Introduction | Media delivery over the internet today relies on using a single representation for coded media across storage, distribution, and delivery systems. Within a server-client single-path streaming model, traditional source coding techniques are applied to the media and segment-based media formatting is utilized for storage ... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 4.1 Source data | Source data is used to create multiple CMMF encoded versions. CMMF can be applied to any media object type, such as a WAV audio clip, an MPEG-4 video clip, an MPEG Dynamic Adaptive Streaming over HTTP (DASH) [i.2] video segment, or an MPEG Common Media Application Format (CMAF) [i.3] addressable resource. In a common p... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 4.2 CMMF bitstream creation | |
630bb3779e33ebc8586024227b48f59f | 103 973 | 4.2.1 Encoding CMMF | Generating a CMMF encoded version can be either a real-time process, or a file-based process depending on the application. In this process, the application of linear, network or channel coding to source coded and packaged audio-visual media (i.e. the source data) typically follows these basic steps: 1) Partitioning of ... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 4.2.2 Symbol groups in CMMF | Coded/repair symbols (including systematic or source symbols) can be grouped and packaged in different ways within the CMMF bitstream. The symbol grouping can be chosen to best fit the needs of a given application. Example symbol groups include: • Individual symbol group (i.e. not grouped): Each coded/repair symbol is ... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 4.2.3 Decoding CMMF | The CMMF bitstream specifies and enables carriage and signalling of essential coding parameters required for reconstruction of the original source symbols in a decoder. The basic steps for decoding include: 1) For each block, decode the received coded symbols yn,j recreating the source symbols xn,i. 2) Concatenate each... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 4.2.4 Mapping to/from CMMF | The coding CMMF employs is essentially a mapping of information from one form to another to enable additional methods and approaches to communicate or store that information across a network. CMMF supports multiple code types to help ensure applicability in different use cases. A CMMF encoder and decoder may include na... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 4.3 Media delivery using CMMF | |
630bb3779e33ebc8586024227b48f59f | 103 973 | 4.3.1 Overview | CMMF supplements existing methods to stream/deliver media across networks by enabling content to be delivered from multiple sources and/or across multiple network paths. In general, CMMF can be integrated into existing workflows through the addition of a minimal set of new components. All that is required is a CMMF bit... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 4.3.2 CMMF transport objects and transport sessions | Objects to be delivered using CMMF in the context of the present document may be organized using transport objects where transport objects are organized in a delivery session composed of one or more transport sessions: • A transport session consists of one or multiple transport objects. Each transport object can be uni... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 4.3.3 CMMF delivery architecture reference points | CMMF provides a general framework for multisource-coded media that can be utilized across many different media delivery architectures and use cases. While many of these architectures and scenarios differ in one way or another, many common concepts and approaches are often shared. Figure 9 provides a notional reference ... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 4.3.4 CMMF delivery procedure | The procedure for delivering source media using CMMF is highly dependent on the use case, delivery architecture, and network protocols utilized. As a result, defining one generic procedure is not possible. However, Figure 10 provides an example delivery procedure for HTTP-based adaptive streaming scenarios. NOTE: Other... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 4.3.5 CMMF Configuration Information | Additional information may need to be communicated between components of the reference CMMF delivery architecture shown in clause 4.3.3 to enable multi-source delivery using CMMF. In general, this information is specific to the operation of CMMF and intended to supplement existing information defined for the media deli... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 4.3.6 CMMF as a Content Delivery Protocol | As described in clause 4.3.1, CMMF provides a means to generate coded/repair transport objects for transport/delivery sessions and can be implemented as a Content Delivery Protocol (CDP). In one instantiation, the CMMF coded/repair framework can be based on the Forward Error Correction (FEC) Building Block as defined i... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 4.4 Overview of the specification | The remainder of the present document defines a bitstream syntax for communicating multi-source encoded media and provides examples of delivery architectures that utilize CMMF for multi-source delivery: • Clauses 5 and 6 provide the bitstream's syntax and semantics respectively. These clauses define the syntax used on ... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5 Bitstream syntax | |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.0 Bitstream organization | The syntax specification presented in clause 5.2 shows how the CMMF bitstream (cmmf_bitstream()) is the top-level structure of a bitstream. Every bitstream begins with a sync() structure, and contains one or more subatom (subatom()) structures. A subatom is a generic container that can be populated with different types... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.1 Semantics of syntax specification | |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.1.1 Pseudocode syntax | The following pseudocode within syntax boxes describes the order of arrival of information within the CMMF bitstream. This pseudocode is roughly based on C language syntax, but simplified for ease of reading. For bitstream elements that are larger than one bit, the order of the bits in the serial bitstream is either mo... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.1.2 Bitstream variable syntax | The variable syntax is described in the format of a three-column table in the present document. In these tables, first column entries in bold signify the occurrence of the corresponding variable in the bitstream; the second column specifies the bit-field length and way of encoding (according to the notation in clause 5... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.1.3 Bitstream structure syntax | Bitstream structures (also referred to as elements) are defined using the C procedure syntax. The substructure is expanded by the C call syntax name (<arguments>). Table 3 shows an example of the bitstream structure syntax format. Table 3: Example of bitstream structure Syntax Encoding Clause name(<optional arguments>)... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.1.4 Iteration and conditional operators | Iteration is expressed using the usual C statements for, while, and do...while. Conditional expansion uses these constructs: • if (…) ... • if (…) ... else ... • if (…) ... else if () ... These examples demonstrate the procedure of reading a flag from the stream and performing an <action> if the flag is set (binary 1).... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.1.5 Boolean operations | The Boolean operators && and || follow normal C conventions. For example, for an && operation, the right-hand side is not evaluated if the left-hand side is FALSE, as listed in Table 6. Table 6: Example of Boolean operation syntax format Syntax Encoding Clause if (paramA && paramB) { b(1) <action> } |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.1.6 Labels and comments | Labels are flush against the left margin and are indicated as comments in the code. Table 7 shows an example label: Table 7: Example of bitstream label Syntax Encoding Clause /* Label */ Labels are regarded as markers within the expanded bitstream, not as textual markers within the syntax description. Comments are inde... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.1.7 Operational variables not in the bitstream | Some operational variables that are not present in the bitstream but are useful for performing certain operations (such as parsing the bitstream) are presented in not bold, as shown in the example in Table 9. Table 9: Example of operational variable format Syntax Encoding Clause block_count = block_count_minus1 + 1 |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.1.8 Arrays | Some bitstream elements naturally form arrays. Even if bitstreams are naturally included in arrays, this syntax specification treats all bitstream elements individually. Where appropriate, arrays are described as multiple elements (for example, block_header_subatom_offset[blk]) within control structures, such as for lo... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.1.9 Bit field encoding | The encoded data can be thought of as a serial bitstream containing items of data that occupy fields of varying length (for example, three bits to specify a number in the range [0…7]). The bits occupying each field are presented with the most-significant bit first. Because fields can be of variable length, they can gen... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2 Syntax specification | |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.1 cmmf_bitstream() | Table 11: Syntax of cmmf_bitstream() Syntax Encoding Clause cmmf_bitstream() 6.1.1 { sync() 5.2.3 while (true) { subatom() 5.2.2 } } |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.2 subatom() | Table 12: Syntax of subatom() Syntax Encoding Clause subatom() 6.1.2 { /* subatom header start */ subatom_id u(4) 6.1.2.1 if (subatom_id == 0xF) { subatom_id_ext u(8) 6.1.2.1 subatom_id = subatom_id + subatom_id_ext } b_bitstream_id_present b(1) 6.1.2.2 reserved v(1) sas_bits = num_bits_code() 6.1.2.3, 5.2.23 if (b_bit... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.3 sync() | Table 13: Syntax of sync() Syntax Encoding Clause sync() 6.1.3 { syncword v(64) 6.1.3.1 version v(4) 6.1.3.2 b_content_encode_uuid b(1) 6.1.3.3 reserved v(3) if (b_content_encode_uuid) { content_encode_uuid v(128) 6.1.3.4 } } |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.4 bitstream_header() | Table 14: Syntax of bitstream_header() Syntax Encoding Clause bitstream_header() { 6.1.4 content_source_size u(64) 6.1.4.1 content_source_type v(3) 6.1.4.2 reserved v(1) b_content_source_split b(1) 6.1.4.3 if (b_content_source_split) { content_source_split_start u(64) 6.1.4.4 content_source_split_end u(64) 6.1.4.4 } co... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.5 block_header() | Table 15: Syntax of block_header() Syntax Encoding Clause block_header() 6.1.5 { block_index = block_index_or_count_value() 6.1.5.1, 5.2.24 block_size u(32) 6.1.5.2 block_symbol_size u(32) 6.1.5.3 bns_bits = num_bits_code() 6.1.5.4, 5.2.23 block_num_symbols u(bns_bits) 6.1.5.5 b_block_max_symbol_index_present b(1) 6.1.... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.6 addl_cce_parameters() | Table 16: Syntax of addl_cce_parameters() Syntax Encoding Clause addl_cce_parameters() 6.1.5.24.8 { num_addl_cce_params_minus1 u(2) 6.1.5.24.8.1 for (eprm = 0; eprm < (num_addl_cce_params_minus1 + 1); eprm++) { cce_parameter_type v(3) 6.1.5.24.8.2 cce_parameter_size_exp u(4) 6.1.5.24.8.3 ccep_bits = 2 ^ cce_parameter_s... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.7 prng_parameters() | Table 17: Syntax of prng_parameters() Syntax Encoding Clause prng_parameters() 6.1.5.25 { prng_type v(3) 6.1.5.25.1 prng_seed_bits_code v(2) 6.1.5.25.2 ps_bits = 2 ^ (prng_seed_bits_code + 4) /* prng_parameters() encryption info start */ prng_seed u(ps_bits) 6.1.5.25.3 prng_density_percentage u(7) 6.1.5.25.4 reserved v... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.8 packet() | Table 18: Syntax of packet() Syntax Encoding Clause packet() 6.1.6 { if (block_count > 1) { packet_block_index = block_index_or_count_value() 6.1.6.1, 5.2.24 } else { packet_block_index = 0 6.1.6.1 } packet_header() 5.2.9 ETSI ETSI TS 103 973 V1.2.1 (2026-03) 49 Syntax Encoding Clause coded_symbol v(css_bits) 6.1.6.2 } |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.9 packet_header() | Table 19: Syntax of packet_header() Syntax Encoding Clause packet_header() 6.1.7 { b_systematic_symbol b(1) 6.1.7.1 packet_mask v(7) 6.1.7.2 if (packet_mask & 0x1) { psi_bits = num_bits_code() 6.1.7.3, 5.2.23 packet_symbol_index u(psi_bits) 6.1.7.4 } if (packet_mask & 0x2) { if (b_systematic_symbol) { b_systematic_symb... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.10 encoder_content_info() | Table 20: Syntax of encoder_content_info() Syntax Encoding Clause encoder_content_info() 6.1.8 { b_encoder_id_present b(1) 6.1.8.1 if (b_encoder_id_present) ETSI ETSI TS 103 973 V1.2.1 (2026-03) 50 Syntax Encoding Clause { encoder_uuid v(128) 6.1.8.2 } b_content_id_present b(1) 6.1.8.4 if (b_content_id_present) { conte... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.11 media_segment_info() | Table 21: Syntax of media_segment_info() Syntax Encoding Clause media_segment_info() 6.1.9 { media_segment_block_index = block_index_or_count_value() 6.1.9.1, 5.2.24 reserved v(4) b_composite_source_index_present b(1) 6.1.9.3 if (b_composite_source_index_present) { media_segment_composite_source_index u(8) 6.1.9.4 } me... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.12 cmmf_time() | Table 22: Syntax of cmmf_time() Syntax Encoding Clause cmmf_time() 6.1.10 { b_ddhhmmss_format b(1) 6.1.10.1 if (b_ddhhmmss_format) { if (b_dd_present) ( b(1) 6.1.10.2 days u(5) 6.1.10.2 } if (b_hh_present) ( b(1) 6.1.10.2 hours u(5) 6.1.10.2 } if (b_mm_present) ( b(1) 6.1.10.2 minutes u(6) 6.1.10.2 } if (b_ss_present) ... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.13 chunked_subatom() | Table 23: Syntax of chunked_subatom() Syntax Encoding Clause chunked_subatom() 6.1.11 { /* chunk subatom info start */ chunk_segment_id u(16) 6.1.11.1 chunk_segment_index u(24) 6.1.11.2 if (chunk_segment_index == 0) { num_chunk_segments u(24) 6.1.11.3 original_subatom_id u(4) 6.1.11.4 if (original_subatom_id == 0xF) { ... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.14 block_group_directory() | Table 24: Syntax of block_group_directory() Syntax Encoding Clause block_group_directory() 6.1.12 { block_group_dir_mask v(8) 6.1.12.1 block_count_minus1 = block_index_or_count_value() 6.1.4.7, 5.2.24 if (block_group_dir_mask & 0x1) { for (block = 0; block < (block_count_minus1 + 1); block++) { block_header_subatom_off... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.15 fb_integrity() | Table 25: Syntax of fb_integrity() Syntax Encoding Clause fb_integrity() 6.1.13 { fb_hash_type v(2) 6.1.13.1 fb_hash_algorithm v(3) 6.1.13.2 fb_hash_size v(4) 6.1.13.3 reserved v(6) b_fb_integrity_ext b(1) 6.1.13.4 if (b_fb_integrity_ext) { fb_integrity_extension() = extension(3) 5.2.18 } fb_hash v(fb_hash_bits) 6.1.13... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.16 packet_integrity() | Table 26: Syntax of packet_integrity() Syntax Encoding Clause packet_integrity() 6.1.14 { packet_hash_algorithm v(3) 6.1.14.1 packet_hash_size v(3) 6.1.14.2 reserved v(1) b_packet_integrity_ext b(1) 6.1.14.3 if (b_packet_integrity_ext) { packet_integrity_extension() = extension(3) 5.2.18 } packet_hash v(pkt_hash_bits) ... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.17 coefficient_vector() | Table 27: Syntax of coefficient_vector() Syntax Encoding Clause coefficient_vector(window_size, block_field_size_exp_val) 6.1.15 { for (index = 0; index < window_size; index++) { coded_symbol_coeff[index] u(block_field_size_exp_val) 6.1.15.1 } } |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.18 extension() | Table 28: Syntax of extension() Syntax Encoding Clause extension(num_bits) 6.1.16 { extension_byte_size u(num_bits) 6.1.16.1 for (i = 0; i < extension_byte_size; i++) { reserved v(8) } } |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.19 packet_header_only() | Table 29: Syntax of packet_header_only() Syntax Encoding Clause packet_header_only() 6.1.17 { if (block_count > 1) { packet_block_index = block_index_or_count_value() 6.1.6.1, 5.2.24 } else { packet_block_index = 0 } packet_header() 5.2.9 ETSI ETSI TS 103 973 V1.2.1 (2026-03) 56 Syntax Encoding Clause } |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.20 rfc5052_information() | Table 30: Syntax of rfc5052_information() Syntax Encoding Clause rfc5052_information() { 6.1.4.6 encoding_symbol_length u(32) 6.1.4.6 if (code_type == 5) { maximum_source_block_length u(32) 6.1.4.6 max_number_of_encoding_symbols u(32) 6.1.4.6 } b_addl_rfc5052_information_present b(1) if (b_rfc5052_information_present) ... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.21 packet_group() | Table 31: Syntax of packet_group() Syntax Encoding Clause packet_group() 6.1.18 { if (block_count > 1) { packet_group_block_index = block_index_or_count_value() 6.1.18.1, 5.2.24 } else { packet_group_block_index = 0 6.1.18.1 } packet_group_index u(8) 6.1.18.2 reserved v(4) pgns_bits = num_bits_code() 6.1.18.3, 5.2.23 p... |
630bb3779e33ebc8586024227b48f59f | 103 973 | 5.2.22 packet_group_header() | Table 32: Syntax of packet_group_header() Syntax Encoding Clause packet_group_header() 6.1.19 { packet_group_symbol_arrangement v(4) 6.1.19.1 packet_group_mask v(6) 6.1.19.2 if (packet_group_mask & 0x1) { reserved v(32) } if (packet_group_mask & 0x2) { switch (packet_group_symbol_arrangement) { case 0: case 1: reserved... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.