hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
6e1e801bd7af1cea77ed35fb178b73ae | 102 797-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ISO 24102-4:2013: "Intelligent transport systems -- Communications access for land mobiles (CALM) -- ITS station management -- Part 4: Station-internal management communications". [2] ISO 24102-5:2013: "Intelligent transpo... |
6e1e801bd7af1cea77ed35fb178b73ae | 102 797-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. [i.1] ETSI EG 202 798: "Intelligent Transport Systems (ITS); Testing; Framework for conformance and interoperability testing". |
6e1e801bd7af1cea77ed35fb178b73ae | 102 797-1 | 3 Definitions and abbreviations | |
6e1e801bd7af1cea77ed35fb178b73ae | 102 797-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ISO 24102-4 [1], ISO 24102-5 [2], ETS 300 406 [3], ISO/IEC 9646-7 [4], EG 202 798 [i.1] and the following apply: PICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system becomes a PICS ETSI ... |
6e1e801bd7af1cea77ed35fb178b73ae | 102 797-1 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ISO 24102-4 [1], ISO 24102-5 [2], ETS 300 406 [3], ISO/IEC 9646-7 [4], EG 202 798 [i.1] and the following apply: FSAP Fast Service Advertisement Protocol IUT Implementation Under Test PICS Protocol Implementation Conformance Statement SUT System Under... |
6e1e801bd7af1cea77ed35fb178b73ae | 102 797-1 | 4 Conformance to this PICS proforma specification | If it claims to conform to the present document, the actual PICS proformas to be filled in by a supplier shall be technically equivalent to the text of the PICS proformas given in annexes A or B, and shall preserve the numbering/naming and ordering of the proforma items. A PICS which conforms to the set of "ITS station... |
55e8cf3d44359863d07868fba5ce6290 | 102 723-5 | 1 Scope | The present document is the baseline for the definition of the Release 2 interface between the management entity and the facilities layer. |
55e8cf3d44359863d07868fba5ce6290 | 102 723-5 | 2 References | |
55e8cf3d44359863d07868fba5ce6290 | 102 723-5 | 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... |
55e8cf3d44359863d07868fba5ce6290 | 102 723-5 | 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... |
55e8cf3d44359863d07868fba5ce6290 | 102 723-5 | 3 Definition of terms, symbols and abbreviations | |
55e8cf3d44359863d07868fba5ce6290 | 102 723-5 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 723-5 [1] apply. |
55e8cf3d44359863d07868fba5ce6290 | 102 723-5 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TS 102 723-5 [1] apply. |
55e8cf3d44359863d07868fba5ce6290 | 102 723-5 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 723-5 [1] apply. ETSI ETSI TS 102 723-5 V2.0.0 (2023-02) 6 4 Use of references and numbering in Release 2 specifications TC ITS specifications are developed in Releases and each Release needs to be self-consistent. The following rules appl... |
55e8cf3d44359863d07868fba5ce6290 | 102 723-5 | 5 Normative Provisions | ETSI TS 102 723-5 [1] shall apply altogether. ETSI ETSI TS 102 723-5 V2.0.0 (2023-02) 7 History Document history V1.1.1 November 2012 Publication V2.0.0 February 2023 Publication |
a26fa17ee61e61a64609c43722b160a0 | 102 770 | 1 Scope | The present document defines mechanisms for locating and conveying System Renewability Messages (SRM) in DVB systems. Here, "System Renewability" primarily refers to the renewal of typically non-volatile information relating to security functionalities including, but not limited to Conditional Access (CA) and Content P... |
a26fa17ee61e61a64609c43722b160a0 | 102 770 | 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... |
a26fa17ee61e61a64609c43722b160a0 | 102 770 | 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 EN 300 468: "Digital Video Broadcasting (DVB); S... |
a26fa17ee61e61a64609c43722b160a0 | 102 770 | 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 ETSI TS 102 770 V1.1.1 (2009-05) ... |
a26fa17ee61e61a64609c43722b160a0 | 102 770 | 3 Abbreviations | For the purposes of the present document, the abbreviations given in [1], [2] and the following apply: SRM System Renewability Message ATSC Advanced Television Systems Committee NOTE: See http://www.atsc.org/. CP Copy Protection DVB Digital Video Broadcasting Project NOTE: See http://www.dvb.org/. PMT Program Map Table... |
a26fa17ee61e61a64609c43722b160a0 | 102 770 | 4 Locating System Renewability Sreams | |
a26fa17ee61e61a64609c43722b160a0 | 102 770 | 4.1 Overview | For locating SRM streams from the SDT, the present document defines two mechanisms. The first mechanism allows to locate a DVB Service the Components of which only convey SRM data. Consequently such a service shall be signalled as being of the type "SRM Service". The second mechanism allows to locate a Component convey... |
a26fa17ee61e61a64609c43722b160a0 | 102 770 | 4.2 Service Description Table (SDT) Signalling | |
a26fa17ee61e61a64609c43722b160a0 | 102 770 | 4.2.1 Locating SRM Services | When all components of a DVB Service convey SRM data, the service_descriptor describing this Service in the SDT shall bear a service_type of 0x08 (SRM Service [1]). In the service descriptor loop of the SDT containing said service_descriptor, at least one CP_identifier_descriptor [1] shall be present, indicating the CP... |
a26fa17ee61e61a64609c43722b160a0 | 102 770 | 4.2.2 Locating SRM Streams as Components of other services | When only a few of the components of a DVB Service convey SRM data, the service_descriptor describing this Service in the SDT shall bear a service_type as defined by [1] but may use a value other than 0x08 (SRM Service [1]). In the service descriptor loop of the SDT containing said service_descriptor, at least one comp... |
a26fa17ee61e61a64609c43722b160a0 | 102 770 | 4.3 Programme Map Table (PMT) Signalling | In the ES_info loop describing a SRM component, one or more CP_descriptors [1] shall be conveyed indicating the CP_system_ids [4] for which SRMs are carried in the component. The stream_type field for SRM components shall be set to 0x05 (ISO/IEC 13818-1 Private Sections [2]). NOTE: This enables SRMs from several CP sys... |
a26fa17ee61e61a64609c43722b160a0 | 102 770 | 5 Transport of System Renewability Messages | The SRM shall be carried in System renewability message sections as specified in ATSC A/98 [3], clause 4. The Transport System Target Decoder (T-STD) model for SRM transport is defined by ATSC A/98 [3], clause 6. ETSI ETSI TS 102 770 V1.1.1 (2009-05) 9 History Document history V1.1.1 May 2009 Publication |
2f0cb67c734a46e7ecbedd8970d041e7 | 102 723-4 | 1 Scope | The present document specifies the MN interface between the management entity and the networking & transport layer of the ITS station reference architecture. Based on the definition of the MN interface as a service access point and the generic services and service primitives specified in [3], the present document provi... |
2f0cb67c734a46e7ecbedd8970d041e7 | 102 723-4 | 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... |
2f0cb67c734a46e7ecbedd8970d041e7 | 102 723-4 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI EN 302 665: "Intelligent Transport Systems (ITS); Communications Architecture". [2] ISO 21217: "Intelligent Transport Systems - Communications access for land mobiles (CALM) - Architecture". [3] ETSI TS 102 723-1: "In... |
2f0cb67c734a46e7ecbedd8970d041e7 | 102 723-4 | 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. |
2f0cb67c734a46e7ecbedd8970d041e7 | 102 723-4 | 3 Definitions and abbreviations | |
2f0cb67c734a46e7ecbedd8970d041e7 | 102 723-4 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in [1] to [3] apply. |
2f0cb67c734a46e7ecbedd8970d041e7 | 102 723-4 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in [1] to [3] apply. ETSI ETSI TS 102 723-4 V1.1.1 (2012-11) 6 |
2f0cb67c734a46e7ecbedd8970d041e7 | 102 723-4 | 4 Architecture | Figure 1 shows the generic architecture of the ITS-S networking & transport layer as specified in [1] and [2]. The MN interface presented in figure 1 is subject of the present document. Layer m anagem ent ITS-S m anagem ent entity ITS-S networking & transport layer M N SM Figure 1: Architecture |
2f0cb67c734a46e7ecbedd8970d041e7 | 102 723-4 | 5 Requirements | The MN interface is specified as a service access point (SAP) in the present document. Compliant with the specifications in [3], the MN-SAP presented in figure 1 provides the functionality of the services • MN-COMMAND • MN-REQUEST and the related service primitives. Details of the related service primitives are specifi... |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 1 Scope | The present document provides the test suite structure and test purposes (TSS & TP) specification for the protocols specified in ISO 21218 [1] in compliance with the relevant requirements, and in accordance with the relevant guidance given in ETSI TS 102 760-1 [2] and in ETSI EG 202 798 [i.2]. NOTE: ISO 21218 [1] canno... |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 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... |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ISO 21218: "Intelligent Transport Systems - Communications access for land mobiles (CALM) - Access technology support". [2] ETSI TS 102 760-1: "Intelligent Transport Systems (ITS); Communications Access for Land Mobiles (C... |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 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. [i.1] ISO 21217:2014: "Intelligent Transport Systems - Communications access for land mobiles (CALM) - Architecture". [i.2] ETSI EG 202 798: "Intelligent Tr... |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 3 Definitions and abbreviations | |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ISO 21218 [1], ISO 21217 [i.1], ISO 24102-3 [3], ISO 24102-4 [i.3], ETSI TS 102 760-1 [2] and ETSI EG 202 798 [i.2] apply. |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ISO 21218 [1], ISO 21217 [i.1], ISO 24102-3 [3], ISO 24102-4 [i.3], ETSI TS 102 760 1 [2] and ETSI EG 202 798 [i.2] apply. |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 4 Test suite architecture | ISO 21218 [1] cannot be tested without being applied to a specific communication interface (CI) specified in ISO 21217 [i.1]. Thus the test architecture presented in figure 3 shows also the OSI communication layers PHY and DLL which are below the "Communication Adaptation Layer" (CAL), both in the system under test (SU... |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 5 TP basics | |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 5.1 TP definition conventions | The TP definition is built according to the guidelines provided in the ITS testing framework ETSI EG 202 798 [i.2], applying a formalized language with pre-defined keywords for the behaviour description. |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 5.2 TP identifier naming conventions | The identifier of the TP is built according to table 1 as recommended in the ITS testing framework ETSI EG 202 798 [i.2]. Table 1: TP naming convention TP/<group>/<x>/<n> group = Group of tests SE State event transitions MB MIB I-Parameters HC Handling of CIs DP Handling of data plane x = Type of testing BV Valid Behav... |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 6 Test purposes | |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 6.1 CI state transitions | |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 6.1.1 Valid behaviour tests | TP ID SE/BV/01 Test objective IUT with CI supporting 48-bit MAC addresses registers correctly at the management entity Reference ISO 21218 [1], clause 6.4.2 PICS Selection PICS_DYNREG AND PICS_MAC48 Initial conditions with { the IUT being in the CI state "not-existent" } Expected behaviour ensure that { when { the IUT ... |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 6.1.2 Invalid behaviour tests | TP ID SE/BI/01 Test objective IUT rejects an invalid CI state transition request Reference ISO 21218 [1], clause 6.4.10 PICS Selection PICS_DYNREG OR PICS_INACT OR PICS_ACT OR PICS_SUSP OR PICS_RES OR PICS_CONN OR PICS_DISCONN Initial conditions with { the IUT being in any CI state except the CI state "existent" } Expe... |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 6.2 MIB parameters | |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 6.2.1 Valid behaviour tests | TP ID MB/BV/01 Test objective IUT correctly reads I-Parameters with Read/Write access or Read-only access Reference ISO 21218 [1], clause 9 and annex A PICS Selection PICS_IPRW OR PICS_IPRO Initial conditions with { the IUT being in the CI state "active" } Expected behaviour ensure that { when { the IUT receives the MI... |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 6.2.2 Invalid behaviour tests | TP ID MB/BI/01 Test objective IUT correctly acknowledges MI-GET requests to non-existent I-Parameters Reference ISO 21218 [1], clause 9 and annex A PICS Selection Initial conditions with { the IUT being in the CI state "active" } Expected behaviour ensure that { when { the IUT receives the MI-GET command for an I-Param... |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 6.3 Handling of CIs | |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 6.3.1 Valid behaviour tests | TP ID HC/BV/01 Test objective IUT correctly handles COMMAND "WakeUp" Reference ISO 21218 [1], clause 9 and annex A PICS Selection PICS_WAKEUP Initial conditions with { the IUT being in the CI state "active" } Expected behaviour ensure that { when { the IUT receives the MI-COMMAND "WakeUp" } then { the IUT periodically ... |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 6.3.2 Invalid behaviour tests | TP ID HC/BI/01 Test objective IUT correctly handles invalid MI-COMMAND Reference ISO 21218 [1], clause 9 PICS Selection Initial conditions with { the IUT being in any CI state except "not_existent" or "existent" } Expected behaviour ensure that { when { the IUT receives an invalid MI-COMMAND } then { the IUT acknowledg... |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 6.4 Handling of data plane | |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 6.4.1 Valid behaviour tests | TP ID DP/BV/01 Test objective IUT correctly handles an IN-UNITDATA transmission request with MAC broadcast address Reference ISO 21218 [1], clause 8.3.1 PICS Selection (PICS_MAC48 AND PICS_BCVCI) AND NOT PICS_CIC_l4 AND NOT PICS_CIC_l5 Initial conditions with { the IUT being in the CI state "active" or "connected" } Ex... |
5136b28672e3f427d8758998de7d30ac | 102 760-2 | 6.4.2 Invalid behaviour tests | TP ID DP/BI/01 Test objective IUT correctly handles the minimum priority "MinimumUserPriority" and notifies this in an IN- UNITDATA-STATUS.indication service primitive Reference ISO 21218 [1], clause 8.3.3 and clause 8.4 PICS Selection PICS_INUDS AND NOT PICS_CIC_l4 Initial conditions with { the IUT being in the CI sta... |
b4c0779814c8f6a750bd8f6d5708232e | 102 723-2 | 1 Scope | The present document: • specifies the architectural approach to specify a "Management Information Base" (MIB) for ITS, • specifies common addressing parameters needed for MIBs. |
b4c0779814c8f6a750bd8f6d5708232e | 102 723-2 | 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... |
b4c0779814c8f6a750bd8f6d5708232e | 102 723-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI EN 302 665: "Intelligent Transport Systems (ITS); Communications Architecture". [2] ISO 21217: "Intelligent transport systems - Communications access for land mobiles (CALM) - Architecture". [3] ETSI TS 102 723-1: "In... |
b4c0779814c8f6a750bd8f6d5708232e | 102 723-2 | 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. [i.1] IETF RFC 3410 (2002): "Introduction and Applicability Statements for Internet Standard Management Framework". |
b4c0779814c8f6a750bd8f6d5708232e | 102 723-2 | 3 Definitions and abbreviations | |
b4c0779814c8f6a750bd8f6d5708232e | 102 723-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in [1] and [2] apply. ETSI ETSI TS 102 723-2 V1.1.1 (2012-11) 6 |
b4c0779814c8f6a750bd8f6d5708232e | 102 723-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in [1] and [2] and the following apply: ASN Abstract Syntax Notation MIB Management Information Base OID Object Identifier SMI Structure of Management Information SNMP Simple Network Management Protocol |
b4c0779814c8f6a750bd8f6d5708232e | 102 723-2 | 4 Management of communication objects in ITS | |
b4c0779814c8f6a750bd8f6d5708232e | 102 723-2 | 4.1 Introduction | ITS communication objects are addressable instances of functionality of ITS stations (ITS-S) specified in [1], [2] and [3]. The behaviour of such objects may be given by parameter settings. Values of such parameters may be set either at time of installation of the object, or may be set dynamically during operation of t... |
b4c0779814c8f6a750bd8f6d5708232e | 102 723-2 | 4.2 MIB for SNMPv2 | Design of MIBs for access with version 2 of the SNMP shall be as specified in RFC 3418 [6], in line with general requirements set up in [1], [2] and [3]. RFC 3418 [6] contains several references to other RFCs, of which very essential applicable RFCs are listed below: • Structure of Management Information Version 2 [4].... |
b4c0779814c8f6a750bd8f6d5708232e | 102 723-2 | 4.3 Other MIBs | In case SNMP is not required to be used to manage a MIB for a specific ITS-S functionality, the design of a MIB may be directly based on elements of the latest version of ASN.1 applying any reasonable solution. ETSI ETSI TS 102 723-2 V1.1.1 (2012-11) 7 |
b4c0779814c8f6a750bd8f6d5708232e | 102 723-2 | 4.4 OID | MIBs and there elements are addressed by means of "Object Identifiers" (OID). The root to a MIB specified in an ETSI deliverable produces by ETSI TC ITS shall be as specified in [3]. ETSI ETSI TS 102 723-2 V1.1.1 (2012-11) 8 History Document history V1.1.1 November 2011 Publication |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 1 Scope | The present document defines the Bearer Control Layer (BCt) peer-to-peer interface of the Family SL satellite radio interface between the Radio Network Controller (RNC) and the User Equipment (UE) used in the satellite network. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 2 References | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 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 reference document (including any amendments) applies. Referenced documents which ar... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 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 reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 3 Symbols and abbreviations | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 3.1 Symbols | For the purposes of the present document, the symbols given in ETSI TS 102 744-1-4 [7], clause 3.1 apply. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 744-1-4 [7], clause 3.2 apply. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 4 Bearer Control Interface | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 4.1 Radio Interface Layering | As described in ETSI TS 102 744-1-3 [6], the satellite communication protocol is considered as a number of communication layers, as follows: • Adaptation Layer (AL); • Bearer Connection Layer (BCn); • Bearer Control Layer (BCt); and • Physical Layer (L1). The satellite radio interface protocol stack is designed to seam... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 4.2 Bearer Control Layer | The Bearer Control Layer includes at least one Bearer Control process, which operates over and manages specific Bearer Types (physical layer specifications for the Shared Access Bearer). The detailed behaviour of the Bearer Control process, and the interface definitions for peer-peer communication of the Bearer Control... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 4.3 Conventions used in the present document | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 4.3.1 Presentation | The following conventions are applied throughout the present document: • In the ASN.1 notation, variable names are always in lower case letters with hyphenation used to improve readability (e.g. ret-bct-pdu-header). Data Types in the ASN.1 always start with an upper case letter and may contain additional upper case let... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 4.3.2 "Reserved" Fields and Values | Fields shown as Reserved BITSTRING (..) in the ASN.1 structures shall be set to zero by the sender and shall be ignored by the receiver. Values not allocated in Distinguished Value Lists shall not be used by the sender and shall be ignored by the receiver. NOTE 1: Distinguished Value Lists of type Integer are being use... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 4.3.3 Boolean Variables | BOOLEAN variables shall be encoded as follows: TRUE ::= 1 FALSE ::= 0 |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 4.3.4 ASN.1 Encoding Rules | The ASN.1 presentation provided in the present document for this interface specification is normative. The encoding rules used for this interface specification are non-standard, using a structured form of packed encoding that ensures efficient packing of each encoded BCtPDU while maintaining preservation of octet bound... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5 Bearer Control Process | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1 Bearer Control Protocol Data Unit (BCtPDU) | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.1 Return Bearer Control PDU Structure (RetBCtPDU) | The Return Bearer Control PDU structure depends on the Return Bearer type used on the Physical Layer as follows. For all Bearer Types except R80T0.5Q and R80T1Q, each RetBCtPDU consists of a Return BCtPDU Header, an optional sequence of one or more Bearer Control Signalling Data Units (BCtSDUs), an optional BCtPayload ... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.2 Forward Bearer Control PDU Structure (FwdBCtPDU) | The Bearer Control PDU has the following structure as shown below and in Figure 5.2a: CRC BCnPDU Octet n Bits: Octet 1 1 2 3 4 5 6 7 8 BCtSDU n BCtSDU 1 RetBCtPDUHeader CRC ALComPDU Octet n Bits: Octet 1 1 2 3 4 5 6 7 8 BCtSDU n BCtSDU 1 RetBCtPDUHeader BCnPDU Octet n Bits: Octet 1 1 2 3 4 5 6 7 8 BCtSDU n BCtSDU 1 Ldr... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.3 Return Bearer Control PDU Header Structure (RetBCtPDUHeader) | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.3.1 RetBCtPDU Header Structure Type 1 | The Bearer Control PDU Header Type 1 shall be used for all BCtPDUs except for the first BCtPDU sent in a Return Block structure (see ETSI TS 102 744-2-2 [9]) using Return Bearer Types R80T0.5Q or R80T1Q. This Bearer Control PDU Header has the following structure: RetBCtPDUHeader ::= SEQUENCE { bct-sdu-follows BOOLEAN, ... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.3.2 RetBCtPDU Header Structure Type 2 | The Bearer Control PDU Header Type 2 shall be used for the first BCtPDUs sent in a Return Block structure (see ETSI TS 102 744-2-1 [8]) using Return Bearer Types R80T0.5Q or R80T1Q. This Bearer Control PDU Header has the following structure: LdrBCtPDUHeader ::= SEQUENCE { bct-sdu-follows BOOLEAN, length-present BOOLEAN... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5 Header Parameters | |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.1 Bct-sdu-follows | The BOOLEAN variable bct-sdu-follows indicates, when set to value '1', that a BCtSDU follows the header; else a BCnPDU follows the header. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.2 Length-present | The BOOLEAN variable length-present indicates the presence of a length field within the header when set to the value '1'. |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.3 Length | The length field, if present, is an eight-bit value which specifies the content length of the PDU from the end of the header to the start of the CRC field. If the length field is absent, the PDU either fills the remaining space in a physical layer block or slot (up to a maximum content length of 256 octets), or is a PD... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.4 BCtPDUAddrType | The variable bct-pdu-addr-type is a two-bit field which is used in the to-UE direction only, and determines the addressing mechanism used for the BCtPDU. The variable is encoded as follows and as shown in Table 5.1: BCtPDUAddrType ::= INTEGER { broadcast (0), tbcn-id (1), comsig-or-ext-addr (2) -- reserved (3) } (0..3)... |
c685b69cc7e892f5b479b9df06e20b36 | 102 744-3-1 | 5.1.5.5 Comsig-or-ext-addr-present | The BOOLEAN variable comsig-or-ext-addr-present determines the choice of the addressing mechanism of the BCtPDU. If this variable is set to '1', then the sequence comsig-type-and-address or ext-addr-type-and-address is present in the header, else tbcn-id is present. ETSI ETSI TS 102 744-3-1 V1.1.1 (2015-10) 27 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.