hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.3.5 CF013: Data presentation | This common facility provides encoding/decoding support for messages being exchanged between ITS-Ss and data exchanged within an ITS-S. The data presentation is based on the common data dictionary contained in the ITS-S. It formats or encrypts a messages with standardized syntax and semantics representations before tra... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.4 Communication support facilities functional requirements | |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.4.1 CF014: Addressing mode | This common facility determines the addressing mode for messages that need to be transmitted from the ITS-S according to the dissemination destination as required by the messages. Depending on the use case requirements as defined in the BSA [i.1], dissemination destination of a message may be: • a geographic area; • IT... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 6.4.2 CF015: Congestion control | The common facility includes the decentralized congestion control (DCC) functionalities of the facilities layer. It interacts with the management entity and contributes to the overall ITS-S congestion control functionalities. Various methods may be used at the facilities and applications layer for reducing at the numbe... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7 Domain facilities functional requirements | Domain facilities provide services and functionalities for one or several BSA applications or for one or several ITS-S types. A domain facilities may become optional for other ITS applications and other ITS-S types. For the usage in the present document, each domain facility is assigned with a unique number DF#, also i... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.1 Application support facilities functional requirements | |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.1.1 DF001: DEN basic service | This domain facility executes the Decentralized Environmental Notification Message (DENM) protocol and provides management support of DENMs. The DENM protocol is used mainly by the Cooperative Road Hazard Warning applications as defined in BSA [i.1] in order to inform a detected event on the roads to approaching vehicl... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.1.2 DF002: CA basic service | The Cooperative Awareness (CA) basic service is a facilities layer entity that provides functions for the management of the facilities layer heartbeat messages i.e. cooperative awareness messages (CAM). It operates the CAM protocol. In BSA, this common facility is relevant to vehicle ITS-S and road side ITS-S. It is ex... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.1.3 DF003: Extended vehicle floating car data (EFCD) | This domain facility enables road side ITS-S, vehicle ITS-S or personal ITS-S to assist the road traffic management applications. Vehicle ITS-S or personal ITS-S transmits CAM periodically and DENM when a specific event is detected. These two messages contain information that may be useful for the traffic management. C... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.1.4 DF004: Billing and payment | This domain facility is relevant for applications requiring billing and payment. It provides billing and payment functionality for services that require payment. This facility establishes connections with back end actors that operate, handle and confirm billing as required by the applications. In a possible implementat... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.1.6 DF006: Road topology basic service (TOPO basic service) | This domain facility is relevant to the ITS applications that rely on a service provided from road side to inform the local road topology. As example, when the road side ITS-S transmits the SPAT message to the approaching vehicle ITS-S. It may furthermore transmit the TOPO message as well, in order to ensure that the r... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.1.7 DF007: In vehicle signage basic service (IVS basic service) | This domain facility is relevant to the ITS applications that rely on a service provided from road side ITS-S or central ITS-S, to inform the road side signage information to the road users via the wireless communications. The road side signage information may include the static road signage information such as speed l... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.1.8 DF008: Community services user management | This domain facility is relevant to a central ITS-S that provides ITS community services. The community services are services that are provided to a specific groups or categories of users belonging to specific communities, typically under contract or agreements. The user of a community may be end users that are connect... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.2 Information support facilities functional requirements | |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.2.1 DF009: Local dynamic map (LDM) | As defined in [i.1], the LDM is relevant to vehicle, personal ITS-S and road side ITS-S. The LDM is a database that provides a representation of the surrounding situation of the ITS-S based on the received messages such as CAM, DENM. Furthermore, the LDM may include the static map data, road traffic data (e.g. SPAT, TO... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.2.2 DF010: RSU management and communication | This domain facility is relevant at the central ITS-S that manages the road side ITS-Ss (road side units RSU) in its network. The central ITS-S maintains a database of the road side ITS-Ss managed or deployed by the central ITS-S. This database includes information of the road side ITS-Ss required by the management, ma... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.2.3 DF011: Map service | This domain facility provides map information to a facility or an ITS application when necessary. For this, a map matching functionality shall be provided, in order to match a geographical position to road topology and provides the map matched data to the requested application or facility. Within an ITS-S implementatio... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.3 Communication support facilities functional requirements | |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.3.1 DF012: Session support | This domain facility manages the communication session between ITS-Ss. If required by an ITS application, this domain facility initiates, maintains, recovers and closes the communication session. If required by the ITS application, this domain facility may furthermore provide the report of the session status to the ITS... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.3.2 DF013: Web service support | This domain facility implements the protocol of a web services e.g. SOAP application protocol, HTTP, etc. to enable the connection of an ITS-S to the Internet. Existing web service tools may be used by an application. One application (e.g. application implemented by a service provider at the central ITS-S) may select o... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.3.3 DF014: Messaging support | This domain facility is mainly used for non-safety applications requiring connection between user ITS-S and the backend system. The messaging support manages one or several message buffer queues dynamically. The message buffer queues can be organized with priority levels to account for different message priorities, QoS... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 7.3.4 DF015: E2E (end to end) Geocasting | This domain facility specified in [i.6] is used for disseminating messages to vehicle ITS-Ss in geographical area in case a direct connection with a central ITS-S is available. This facility may be invoked both from a vehicle ITS-S in a vehicle to vehicle end to end scenario and from ITS-S in a infrastructure to vehicl... |
947f567a7a9eb8044b57db6c55aaab0f | 102 894-1 | 8 Conformance | The requirements specified in the present document describe the general operation of different elements in the ITS-S facilities layer. They are not intended to be tested on their own. Detailed specifications are to be defined for each specific facility for conformance test purpose. As example, specifications of facilit... |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 1 Scope | The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the Test Suite Structure and Test Purposes defined in TS 102 891-2 [2]. The test notation used in the ATS is TTCN-3 (see ES 201 873-1 [7]). The following test specific... |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 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... |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 606: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Message Waiting Indication (MWI)using IP Multimedia (IM) Core Network (CN) subsystem; Protoco... |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 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. |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 3 Definitions and abbreviations | |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 [6], TS 102 587-2 [9] and TS 102 790-3 [3] apply. |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [5], ISO/IEC 9646-7 [6], TS 102 790-3 [3] and TS 124 606 [1] apply. |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 4 Abstract Test Method (ATM) | For the purposes of the present document, the ATM described in clause 4 of TS 102 790-3 [3] applies with following additions. |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 4.1 Configurations for testing UE | The Gm interface is located between SUT (UE) and the IMS. SUT TS UE IMS Gm Figure 1: Test configuration CF_1GmUE ETSI ETSI TS 102 891-3 V3.1.1 (2012-01) 7 The ISC interface provides an access to the AP. SUT IMS AS ISC TS Figure 2: Test configuration CF_1ISC |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 5 The ATS development process | |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 5.1 Requirements and Test Purposes | For each test purpose there is a table defined in clause 5 of TS 102 891-2 [2]. The requirements applicable to this TP are given by a reference to TS 124 606 [1]. There are no explicit formulations of requirements. |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 5.2 ATS structure | |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 5.2.1 Test case grouping | The ATS structure defined in Table 1 is based on the structuring of Test Purposes in clause 4 of TS 102 891-2 [2]. The group names in column 2 of Table 1 are those assigned in the ATS; they are based on the names provided in clause 4 of TS 102 891-2 [2], but use the naming conventions defined for the ATS (see clause 5.... |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 5.2.2 Test case identifiers | The test case names are built up according to the following scheme: "<TC>"_"<Group index>"_"<TC number>" where: a) double quotes (") are used to enclose literal strings; b) <Group path index> is the group index in Table 1 (which uniquely identifies the path of groups/subgroups); c) <TC number> is a running 3-digit deci... |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 5.3 ATS specification framework | |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 5.3.1 ATS Library | For this ATS the TTCN-3 library modules are basically organized as: 1) AtsCommon modules. 2) LibIms modules. 3) LibSip modules (RFC 3261 [4]). 4) LibCommon modules (taken from an improved version of TS 102 351 [8]). NOTE: Due to the common LibSip and LibIms library approach with some other parallel running projects the... |
891084ddbafb791b6fd93a9247cc4040 | 102 891-3 | 5.3.2 Use of TTCN-3 | For the purposes of the present document, the description of the use of TTCN-3 described in clause 5.3.2 of TS 102 790-3 [3] applies. ETSI ETSI TS 102 891-3 V3.1.1 (2012-01) 10 Annex A (normative): Partial PIXIT proforma Notwithstanding the provisions of the copyright clause related to the text of the present document,... |
8eb66225f5bbec02d11fcc591d04f6dd | 102 916-1 | 1 Scope | The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the test specifications for the methods to ensure coexistence of cooperative ITS G5 with TTT DSRC as specified in ETSI TS 102 792 [3] and ETSI EN 302 663 [1] in compliance with the relevant requirements and in accordance... |
8eb66225f5bbec02d11fcc591d04f6dd | 102 916-1 | 2 References | |
8eb66225f5bbec02d11fcc591d04f6dd | 102 916-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 referenced document (including any amendments) applies. Referenced documents which a... |
8eb66225f5bbec02d11fcc591d04f6dd | 102 916-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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
8eb66225f5bbec02d11fcc591d04f6dd | 102 916-1 | 3 Definition of terms, symbols and abbreviations | |
8eb66225f5bbec02d11fcc591d04f6dd | 102 916-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 792 [3], ETSI EN 302 663 [1] and the following apply: PICS proforma: document, in the form of a questionnaire, designed by the protocol specifier or conformance test suite specifier, which, when completed for an OSI implementation or system, becom... |
8eb66225f5bbec02d11fcc591d04f6dd | 102 916-1 | 3.2 Symbols | Void. |
8eb66225f5bbec02d11fcc591d04f6dd | 102 916-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 792 [3], ETSI EN 302 663 [1] and the following apply: DSRC Dedicated Short Range Communication ICS Implementation Conformance Statement ITS Intelligent Transport System ITS-G5 Acronym for the 5,9 GHz vehicular ad-hoc network ITS-S ITS Stat... |
8eb66225f5bbec02d11fcc591d04f6dd | 102 916-1 | 4 Conformance | A PICS proforma which conforms to this PICS proforma specification shall be technically equivalent to annex A, and shall preserve the numbering and ordering of the items in annex A. A PICS which conforms to this PICS proforma specification shall: a) describe an implementation which claims to conform to ETSI TS 102 792 ... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 1 Scope | The present document covers a subset of the use cases from the DVB Home Network commercial requirements (TM3422) and described in DVB BlueBook A109 [3]; it is therefore called DVB-HN Phase 1. It supports features like: • connecting DVB HN devices to the home network allowing them to receive existing DVB services; • det... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 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... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 034: "Digital Video Broadcasting (DVB); Transport of MPEG-2 TS Based DVB Services over IP Based Networks". [2] ETSI TS 102 539: "Digital Video Broadcasting (DVB); Carriage of Broadband Content Guide (BCG) infor... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 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 3066: "Tags for the Identification of Languages". |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 3 Definitions and abbreviations | |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 102 034 [1], TS 102 539 [2] and the following apply: Device: when used alone, "device" means "physical device" ETSI ETSI TS 102 905 V1.1.1 (2010-05) 8 Device Class: Class defined by a set of Logical Functions NOTE: A single physical device ... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 102 034 [1], TS 102 539 [2] and the following apply: AL-FEC Application Layer Forward Error Correction AN Access Network BCG Broadband Content Guide CDS Content Download Service CoD Content on Demand CPCM Content Protection and Copy Management CRID... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 4 Use Cases | This clause describes the Use Cases covered by the DVB-HN Phase 1 specification. The Use Cases are a subset taken from DVB BlueBook A109 [3]. DVB content is protected content or free to air content. 4.1 Use case 1: Streamed content from the Access Network into the Home Network A DVB Home Network device receiving DVB co... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 4.2 Use case 2: Locally stored content | A user uses a DVB Home Network device which enables him to find and play DVB content that is advertised and distributed by another DVB Home Network device. In this use case the DVB content is stored completely on the DVB Home Network device and no active connection to the Access Network is needed. ETSI ETSI TS 102 905 ... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 5 Home Network Architecture | |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 5.1 Logical model | This clause presents the DVB Home Network model. The DVB-HN model is a logical model that defines logical functions and the IPI-HN interface. Figure 1 presents the description model that will be used in the present document. IPI-HN DVB- C/S/T IPI-1 <logical function name> <data translation > p1 p1 p2 <data generation >... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 5.2 Logical functions | Table 1 describes each of the logical functions of the DVB-HN model. Table 1: DVB Logical functions DVB-HN Logical Function Description HN-DP Discovery Point: • Advertises DVB content over IPI-HN interface by translating SD&S and BCG data received via IPI-1 interface from IPI-1 access network into UPnP-CDS. • Advertise... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 5.3 Device Classes | In alignment with DLNA, DVB distinguishes different classes of devices. The identified classes specific to DVB-HN are listed in table 2. A physical device may implement one or more device classes. Table 2: DVB-HN Device Classes Acronym Name Definition Logical functions DVB-MR DVB Media Renderer A device class having IP... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 5.4 UPnP mapping | All Device Classes must support UPnP Device Architecture [14] for discovery, description, control, eventing and presentation as defined in [6]: • A HN-RP shall support an UPnP AV MediaRenderer as defined in [6] device having an AVTransport service, RenderingControl service and a ConnectionManager service. • A HN-DP sha... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 6 Networking and connectivity | This clause is related to the physical interfaces and MAC layers of the Home Network devices. This includes both wired and wireless standards for device connectivity. A DVB HN device shall support at least one of the following connectivity methods: • Ethernet (according to IEEE 802.3 [4], minimum 100Tx). • Wireless LAN... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 7 Supported media formats | HN-RP shall support the DLNA MPEG_TS_SD_EU profile (DLNA Guidelines [7]). HN-RP may also support additional media formats described in TS 101 154 [10]. HN-SP may send DVB content following any format described in TS 101 154 [10]. The ability to transcode to a DLNA supported format is not mandatory in the HN-SP. |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 7.1 Media Format Matching | Media Format matching is an important step in the process of discovering and presenting a content item to the end-user. The server exposes content which is available in a specific format. The rendering device is assumed to be able to render one or more formats, for the components of that content item, for example video... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 7.2 Retrieve Supported Media Formats from the HN-RP | A new UPnP action is defined within the Rendering Control Service. It is called RCS::GetCapabilities(). Argument Direction relatedStateVariable HorizontalSize OUT Size VerticalSize OUT Size SupportedMediaFormat OUT MediaFormatList The Size state variable is an integer representing the size HN-RP is able to decode. The ... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 8 DVB HN Device Discovery | The method of description of a DVB device class in terms of UPnP DDC shall follow the same structure as used by DLNA [6]. |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 8.1 DVB-HN Device Specific Extensions | DVB HN devices shall employ the <dvb:X_DVBDOC> XML element inside the <device> element of the device description document to indicate adherence to a particular DVB TM-IPI Home Network interoperability specification document version (this document). The value of this element is the DVB Device Class, a dash character, fo... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 8.2 Discovery of CPCM Devices | A serving endpoint or a HN RP that implements DVB CPCM shall implement a DVB CPCM UPnP service and advertise this service in their UPnP device description, as defined by CPCM [11]. |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 9 Content Discovery | |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 9.1 CDS | The UPnP Content Discovery Service (CDS) as defined by DLNA [6] shall be used to expose all services that are made available over the HN. The CDS shall follow all the relevant guidelines defined by DLNA [6]. In addition to this, the UPnP CDS should carry the tva:AVAttributes XML elements as defined in [18]. Services ma... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 9.1.1 Translation of DVB metadata into UPnP CDS | The present document describes the mapping of the metadata provided over the access networks into CDS format for delivery into the DVB home network. However, in some cases there may not be a direct correspondence for some fields and elements of the incoming metadata in the CDS document structure. In the cases where the... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 9.2 Transport protocol information | There are three media transport methods for DVB-HN. The method covers both: • Transport format • Session interaction between client and server The three methods are: Media transport method session protocol transport format Server Client HTTP HTTP HTTP HTTP server HTTP client RTSP-RTP RTSP RTP RTSP server, RTP sender RT... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 9.3 Tuner representation | In the ContentDiscovery service, a tuner shall be described following the DLNA Guidelines [6]. |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 9.4 DVB CPCM | Content protected by DVB CPCM shall follow specific extensions as defined in the CPCM specifications [11]. A serving endpoint may contain a mixture of content that is both protected and unprotected. UPnP CDS fields in each content item description are used to signal if content is protected. If a content item has parts ... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 10 DVB content transport | A HN-SP with an IPI-1 interface shall support the reception of a MPEG-2 TS services that comply with clauses 7.1 and 7.2 of TS 102 034 [1]. On the IPI-HN interface, the HN-SP shall support sending a MPEG-2 TS service to another DVB device attached to the home network using RTP/UDP/IP unicast delivery and may support de... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 10.1 RTSP | A HN-SP and HN-RP shall support the RTSP protocol as defined in TS 102 034 [1]. Although all the necessary information will be contained in the UPnP CDS for a content item, the DESCRIBE method may be implemented to describe the transport for that content item. In that case the DESCRIBE answer should contain the UPnP CD... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 10.2 DVB CPCM | If a serving endpoint provides protected content over HTTP transport and supports random access, it shall signal if it supports random access in the clear text domain by appropriate use of the "cleartextbyteseek-full" and "lop-cleartextbytes" bits of the "DLNA.ORG_FLAGS" parameter (see clauses 7.3.37 and 17.3.1 in DLNA... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 11 QoS | DVB shall use a QoS mechanism based on differentiated services code point (DSCP) definitions as given in RFC 2475 [12] and RFC 4594 [13] over the IPI-HN network. The values used shall be the same as defined in the DLNA Extended Guidelines [6]. These values are not identical to those specified in TS 102 034 [1] but ther... |
4ec66d5e5cc2ddd270a62c97769b5ac1 | 102 905 | 12 Reliable HN data transfers | The streaming of DVB content with TS/RTP/UDP between two DVB HN devices can be protected against packet loss by means of RTP retransmission. Duplicate or multicast repair shall not be used. A HN-DP advertises the RTP retransmission support by means of UPnP CDS. RTP retransmission in DVB HN MUST make use of the RFC 4588... |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 1 Scope | The present document is the second part of the Smart Metering Wireless Access Protocol describing the data structures and functional operation of Smart Metering and other applications intending to use spectrum resources covered by TS 102 887-1 [1] Physical Layer. TS 102 887-1 [1] is derived from IEEE 802.15.4g-2012™ [5... |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-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... |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 887-1: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Short Range Devices; Smart Metering Wireless Access Protocol; Part 1: PHY layer". [2] ANSI/TIA-4957.200: "Layer 2 Standard Specification f... |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-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] IEEE Standards Association Registration Authority. NOTE: Available at: http://standards.ieee.org/develop/regauth/ [i.2] IEEE-Standards Association Gui... |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 3 Definitions and abbreviations | |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: beacon: periodically transmitted Frame channel function: function that computes the channel number from a Channel Table as a function of time channel table: standardized representation of the channels of a frequency band frame: data st... |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK ACKnowledgement AEAD Authenticated Encryption with Associated Data AES Advanced Encryption Standard ASH Auxiliary Security Header CCM Counter with CBC-MAC Mode CMAC Cipher-based Message Authentication Code CSL Coordinated Sample Listening ... |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 4 Global modifications to normative references | In order to make use, in the European market context, of the functionality defined in the normative references, the following adaptations are applied: Table 1: Global Modifications to ANSI/TIA-4957.200 Section Reference in ANSI/TIA-4957.200 Action 2.1 Normative References [1] ANSI/TIA-4957.100 Layer 1 Standard Specific... |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 5 Overview | This document describes the MAC sub-layer of the Smart Metering Wireless Access Protocol (SMEP). The SMEP PHY layer is derived from external specifications with enhancements specific to the European context. Similarly, the SMEP MAC sub-layer makes use of functionality in appropriate published standards adapted for use ... |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 6 Devices operating in Mode 1 | This clause defines the behaviour of a node operating in Mode 1 at the MAC sub-layer of the OSI communications model. The IEEE 802.15.4 family of standards (see [3], [4] and [5]) defines a wide range of features that enable simple, low-cost and low-power Low Rate Wireless Personal Area Networks (LR-WPAN). This clause d... |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 6.1 General Description | The general description and architecture shall be as described in [3], clause 4 as amended by [4], clause 4 except: • The Physical Layer referred to in [3], clause 4.4.1 and elsewhere in [3] shall be replaced by the Physical Layer described in [1]. • The description of Guaranteed Time Slots which shall be a feature not... |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 6.2 MAC Protocol | The MAC protocol shall be as defined in [3], clause 5. |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 6.2.1 MAC Functional Description | The MAC Functional Description shall be as defined in [3], clause 5.1 except for clause 5.1.7. In addition, functionality defined in [4], clause 5.1.1a for frequency hopping operation and in [4], clause 5.1.11 for low energy operation is supported in the present document. |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 6.2.1.1 Channel Access | Channel access shall be as defined in [3], clause 5.1.1 (except for references to GTS in [3], clause 5.1.1.1.2 which is a feature not supported in the present document) with the CSMA-CA algorithm as defined in [4], clause 5.1.1.4 and with LE enhancements defined in [4], clause 5.1.1.7. |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 6.2.1.2 Starting and Maintaining PANs | Starting and maintaining PANs shall be as defined in [3], clause 5.1.2 with scanning through channels as defined in [4], clause 5.1.2.1. |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 6.2.1.3 Association and Disassociation | Association and disassociation shall be as defined in [3], clause 5.1.3 with the addition of Fast Association as defined in [4], clause 5.1.3.3. |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 6.2.1.4 Transmission, Reception and Acknowledgement | Frame transmission, reception and acknowledgement shall be as defined in [3], clause 5.1.6 as amended by the following clauses in [4]: • Clause 5.1.6.2 ETSI ETSI TS 102 887-2 V1.1.1 (2013-09) 13 • Clause 5.1.6.4.2 except LLDN and TSCH which are features not supported in the present document • Clause 5.1.6.4.3 • Clause ... |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 6.2.2 MAC Frame Formats | MAC frame formats shall be as defined in [3], clause 5.2 and as amended by [4], clause 5.2.1 and the following clauses of [5], clause 5.2.1. The Frame Control field shall be as defined in [3], clause 5.2.1.1 and as amended by [4], clause 5.2.1.1 except: • The Frame Type field value 0b100 (LLDN) defined in [4], clause 5... |
49cdd64bd5c592cebee27d88ce5814ea | 102 887-2 | 6.2.2.1 Beacon Frame Format | The format of a Beacon frame shall be as defined in [3], clause 5.2.2.1 and as amended by [5], clause 5.2.2.1 and [4], clause 5.2.2.1 except that: • Definitions relating to DSME are not supported. • Definitions relating to TSCH are not supported. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.