hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.2.4.2 Initiation of the data transfer from the master | Figure 7.4 illustrates the initiation of the data transfer by the master. Figure 7.4: Initiation of the data transfer from the master The Master shall perform the following procedure: 1) The master checks the state of the SPI_NSS signal (by reading SS_MI) and if it is de-asserted (i.e. at the high state) the master goe... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.2.4.3 Initiation of the data transfer from the slave | Figure 7.5 illustrates the initiation of the data transfer from the slave. DATA TRANSFER T1 SPI_NSS SS_MO SS_SO T2 Ts T5 T7 T8 DATA TRANSFER Figure 7.5: Slave initiates a MAC access request ETSI ETSI TS 103 713 V18.0.0 (2023-07) 23 Release 18 The slave runs the following procedure: 1) In case the master reported T8 > 0... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.2.4.4 Simultaneous initiation of the data transfer from both master and slave | Figure 7.6 illustrates a simultaneous initiation from the master and the slave. Figure 7.6: Simultaneous initiation of the data transfer from both master and slave Both endpoints initiate a MAC phase for data transfers and run simultaneously their respective procedures. From a master perspective the resulting procedure... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.2.4.5 Slave-driven Flow Control | In certain use-cases and depending on the SPI module design, a slave may assert SPI_NSS (via its SS_SO) during a data transfer in progress for flow control e.g. when the slave needs to delay a subsequent master access as the slave estimates it may not be ready to receive or transmit data. It is assumed that the slave h... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.2.4.6 MAC activation | The MAC activation procedure at power on shall be the following: • The SS_MO shall be de-asserted (i.e. at low level) setting the SPI_NSS output to high impedance. • The master shall drive the VDD power line on. When the power supply of the slave needs to be toggled independently from the power of the other devices sha... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.2.4.7 MAC deactivation | The MAC deactivation procedure for power off shall be the following: • The SS_MO shall be de-asserted (i.e. at low level) setting the SPI_NSS output to high impedance. • The master shall drive the VDD power line off. |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.3 Link Layer Frame | |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.3.1 Overview | Master and slave exchange frames. The format of the frames generated by master and slave is determined by the link layer and it is shown in figure 7.8. Figure 7.8: Link Layer Frame structure All bytes shall be transmitted with Most Significant Bit first (MSB first). All frames are transferred with the bytes in the orde... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.3.2 Frame generation and transfer rules | |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.3.2.1 Overview | The SPI master initiates an SPI access either to send a frame, retrieve a frame from the slave after a MAC access request or both. Depending on the master and the slave specific implementations (as described in the following clauses), the SPI master retrieves the slave frames over one or two SPI accesses. |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.3.2.2 Generally applicable rules | If the SPI master has a frame to send, the SPI master shall send that frame in a single SPI access. The SPI master may initiate a SPI access with a length higher than the length of the frame to send. In case the SPI access is longer than the length of the frame being sent, SPI master and/or slave shall add Non-Signific... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.3.2.3 Slave frame retrieval in one SPI access | If the slave sets the bit 5 to 0 in the MCT_DATA field byte 0 (see table 7.9), the SPI master shall retrieve the slave frames within a single SPI access, i.e. without de-asserting SPI_NSS for the entire slave frame transfer, possibly with a gap when SPI_CLK is stopped (i.e. SPI_CLK is idle). If the SPI master has a fra... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.3.2.4 Slave frame retrieval in two SPI accesses | When the slave sets bit 5 to 1 in the MCT_DATA field byte 0 (see table 7.9), the SPI master may use two SPI accesses to retrieve a slave frame. The SPI master de-asserts the SPI_NSS when the first SPI access is completed and asserts again the SPI_NSS for the second SPI access for retrieving any remaining bytes of the s... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.3.3 Data transfer cases | Some of the most representative data transfer cases based on the frames generation and transfer rules in clause 7.3.2 are described below. Any frame sent by the SPI master or the slave shall be preceded by a MAC phase issued respectively by the SPI master or the slave. When two SPI accesses are required for transferrin... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.4 LLC layers | Three Logical Link Control (LLC) layers are defined in the present document: • SHDLC: this is the generic LLC. SHDLC is defined in ETSI TS 102 613 [2], clause 10. Support of this LLC is mandatory for the master and the slave. • CLT: this LLC is used for some proprietary protocol handling. CLT mode is defined in ETSI TS... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.5 Interworking of the LLC layers | After MAC activation, the SHDLC link shall not be established and no CLT session shall be open. Only the MCT LLC shall be used by the master and by the slave for the SPI interface initialization. The master shall take the following action after a successful MCT LLC phase: • If the master has data to be sent to the slav... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.6 MCT LLC definition | |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.6.1 MCT LPDU structure | The MCT LPDU shall be structured according to figure 7.12. Figure 7.12: MCT LPDU structure The meaning of MCT_CTRL and MCT_DATA is given in table 7.4. Table 7.4: Meaning of MCT_CTRL and MCT_DATA MCT_CTRL Meaning MCT_DATA 00000 MCT_READY Sent from Slave to Master See table 7.5 00010 MCT_MASTER_REQ Sent from Master to Sl... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.6.2 MCT_DATA from master | Tables 7.5, 7.6 and 7.7 define the capabilities of the master. ETSI ETSI TS 103 713 V18.0.0 (2023-07) 32 Release 18 Table 7.5: Master-specific MCT_DATA field Byte Info/parameter Meaning 0 Spec_Ver Specification version to which master is compliant. Defined in table 7.6. 1 Capabilities Defined in table 7.7. 2, 3 T4 Inac... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.6.3 MCT_DATA from slave | Tables 7.8.and 7.9 define the capabilities of the slave. Table 7.8: Slave-specific MCT_DATA field Byte Info/parameter Meaning 0 Spec_Ver Specification version to which slave is compliant. Defined in table 7.6. 1 Capabilities Defined in table 7.9. 2 SPI_CLK Max SPI_CLK value supported by SPI slave (MHz). 3 T1 Slave MAC ... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.6.4 MCT activation procedure | Slave start-up time following power-on is defined as POT and has an initial value of 1 s for the first power on, when the slave reported MCT_READY parameters are not yet available. After POT time (from the time VDD is valid after power-on) slave shall be ready to receive the MCT_MASTER_REQ from master. Shorter POT valu... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.7 SHDLC LLC definition | |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.7.1 SHDLC overview | The provisions of ETSI TS 102 613 [2], clause 10.1 shall apply. The SWP SHDLC layer is replaced by the SPI SHDLC layer defined in the present document. The SHDLC layer shall ensure that data passed up to the next layer has been received exactly as transmitted i.e. error free, without loss and in the correct order. Also... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.7.2 Endpoints | SHDLC communication occurs between two endpoints. Those endpoints may be either the master endpoint or the slave endpoint. There is no priority of traffic. SHDLC Master Endpoint Slave Endpoint Figure 7.13: Endpoints In ETSI TS 102 613 [2], clause 10, the term CLF refers to the master endpoint and the term UICC to the s... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.7.3 Flow control | |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.7.3.1 Overview | Flow control is performed by a transmitter in order to avoid corruption or loss of data. It consists of methods applied by the transmitter and receiver in order to send a maximum number of SHDLC frames that can be accepted by the receiver, after which it shall stop sending data until the receiver sends at least an ackn... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.7.3.2 Flow control based on SHDLC | The method defined in this clause is based on SHDLC flow control, as defined in ETSI TS 102 613 [2]. ETSI ETSI TS 103 713 V18.0.0 (2023-07) 35 Release 18 In addition to the provisions of clause 7.3.2, the total number of bytes transferred on SPI_MOSI while retrieving a slave frame over two SPI accesses shall be less th... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.8 Power management | |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.8.1 Power saving mode | In order to optimize the power consumption, both the master and the slave may enter into power saving mode. This clause defines the conditions for the slave to enter into power saving mode and the procedures for the master for resuming the slave from power saving mode. The master and the slave shall both resume in the ... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.8.2 Conditions for entering power saving mode | |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.8.2.1 Slave entering power saving mode | The slave shall not enter into power saving mode, if the slave has issued a MAC access request and is waiting for data transfer from the master. The slave may enter into power saving mode in one of the cases below, assuming there is no pending activity: 1) All frames have been transmitted by the slave, acknowledged suc... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.8.2.2 Master entering power saving mode | The master may enter into an implementation-specific power saving mode at any time, without informing the slave. The slave power source status and capabilities indicated by the master at interface initialization shall not change when the master enters into power saving mode, is in power saving mode, is resuming from po... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.8.3 Resuming from power saving mode | |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.8.3.1 Resuming the slave from power saving mode | Resuming the slave from power saving mode shall be performed by the master when any of the conditions above for the slave to enter into power saving mode has been previously met. The master shall ensure that all signals it drives are in the idle state corresponding to SPI mode 0 before initiating the resuming of the sl... |
54685e5148bbff6300c41deae946f3c9 | 103 713 | 7.8.3.2 Resuming the master from power saving mode | If the master has entered into power saving mode, it shall resume when the slave initiates a MAC access request. The slave initiates the MAC access request with the procedures as described in clause 7, regardless the power management status of the master. Following a resume by a MAC access request during T2 as describe... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 1 Scope | The present document provides the handover details for HTTP delivery of LI and LD. The present document applies in particular to messaging services, but is not limited to messaging services. The delivery of streaming content is not in the scope of the present document. |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 2 References | |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 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... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 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... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 3 Definition of terms, symbols and abbreviations | |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 120 [1] and the following apply: Lawful Disclosure (LD): process by which a LEA requests and receives data from a CSP NOTE: A formal definition of Lawful Disclosure (or the related terms "Retained Data" and "Stored Data") is not given in the prese... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 3.2 Symbols | Void. |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CA Certificate Authority CSP Communications Service Provider HTTP HyperText Transfer Protocol HTTPS HyperText Transfer Protocol Secure ID IDentifier LD Lawful Disclosure LDID Lawful Disclosure IDentifier LEA Law Enforcement Agency LI Lawful In... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 4 Introductory material | |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 4.1 Reference Model | This clause provides a Reference Model which applies to request and delivery mechanisms between Law Enforcement Agencies (LEAs) and Communications Service Providers (CSPs) for the present document. Request means submission of a request for data and delivery means handover of the material that was identified by the CSP ... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 4.2 Responsibilities | The LEA is responsible for creating a lawful request and the request needs to be clear. The LEA delivers the request to the CSP. The legal obligation on the CSP (e.g. what has to be delivered, what has to be retained) is managed independently of the delivery interface and is out of scope of the present document. The CS... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5 Basic concepts | |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.1 General | The object consists of the following components: • Application level header (see clause 5.3). ETSI ETSI TS 103 707 V1.11.1 (2025-08) 9 • Core parameters (see clause 5.4). • Glossary (see clause 5.5). • CSP-defined information (see clause 5.6). The components "Core parameters" and "Glossary" vary depending on the servic... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.2 Delivery | |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.2.1 General | Handover items are delivered using the DeliveryObject as described in ETSI TS 103 120 [1], clause 10. A DeliveryObject may contain either a single handover item (using the "handoverItem" root element) or a collection of handover items (using the "handoverItemCollection" root element). All handover items in a collection... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.2.2 ETSI TS 103 120 Message header | The Message Header fields shall be populated as defined in ETSI TS 103 120 [1], clause 6.2, with the additional clarifications as shown in table 3. Table 1: ETSI TS 103 120 [1] Message Header population Parameter Description M/O/C SenderIdentifier The Sender is the CSP. The SenderIdentifier has two components: a Countr... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.2.3 ETSI TS 103 120 Object header | The payload shall contain a "Delivery Request", which shall contain a DeliveryObject as per ETSI TS 103 120 [1], clause 10. The common Object fields shall be specified as per ETSI TS 103 120 [1], clause 7.1.1 with the clarifications as shown in table 2. Table 2: Object top-level fields Parameter Description M/O/C Count... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.3 Application level header | |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.3.1 General | Each handover item may contain an application level header, with the fields shown in table 4. Table 4: Application level Header structure Parameter Description M/O/C applicationCorrelation May be used to indicate that a number of handover items are related to each other (see clause 5.3.2). O |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.3.2 ApplicationCorrelation | If a number of handover items are related to each other, a CSP may use the ApplicationCorrelation structure to indicate that they are related. When this mechanism is used, related items shall be allocated the same ApplicationLevelID value. This value shall be unique for a given LIID or LDID. The precise format and choi... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.4 Core parameters | |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.4.1 General | Table 6 defines the core parameters of a messaging service. NOTE: The present document does not contain core parameters for any other services than messaging services. Table 6: MessagingCoreParameters Parameter Description M/O/C messageSender Identifier of the sender of the message, if available. Given as a MessagingPa... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.4.2 MessagingParty | The MessagingParty type is used to provide a list of identifiers associated with a messaging party (either a sender or a receiver). Multiple identifiers may be provided. The format and values of the identifiers are determined by the CSP. Each MessagingParty may include an indication of whether the party was the subject... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.4.3 AssociatedBinaryData | The associatedBinaryData field is used by the CSP to provide details of any data, such as attached images or video, associated with the delivered information. The data itself shall be delivered separately, according to the details in annex C. The associatedBinaryData field contains a set of binaryObject records, each s... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.5 Glossary | The term glossary is used to refer to parameters for which there is a common definition, context and meaning as agreed by LEAs and CSPs. NOTE: The present document does not contain any glossary parameters. The use of the glossary is in addition to the technique in clause 5.6 in which the parameter definitions from the ... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.6 CSP-defined information | |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.6.1 General | The CSP-defined information includes any self-described information that the CSP can provide for the interception (meta-data and the content of communication) or LD. The parameters themselves are not defined by the present document. Some examples of items which might be present for messaging services are: • Time of rec... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.6.2 CSP-defined schema | The CSP is required to describe the schema of data provided in the CSP-defined information and provide appropriate descriptions. Details of the schema shall be provided using the schemaDetails structure shown in table 10. Table 10: SchemaDetails structure Parameter Description M/O/C schemaIdentifier A unique identifier... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.6.3 Use of common types from ETSI TS 103 280 | Where CSP-defined schemas contain information elements which correspond to common types already defined in ETSI TS 103 280 [7] (e.g. MSISDN) CSPs should use the types defined in ETSI TS 103 280 [7] as part of their schema definitions. NOTE: This technique is in addition to the use of Glossary terms as defined in clause... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.6.4 Including binary data in the CSP-defined content | Details for the delivery of binary data associated with a message are given in annex C. |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 5.7 Error reporting | In the Reference Model described in clause 4.1, the request for data and submission of warrant information may not happen on the same logical channel as the delivery of data. Hence, two types of error reporting are required: error reporting related to the transfer and management of warrant information as well as reques... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 6 Transport details | |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 6.1 HTTP details | There shall be a mechanism to establish the destination information as per ETSI TS 103 120 [1], clause 8.3.6 (specifically clause 8.3.6.2). This is not specified in the present document. The delivery protocol is as specified in ETSI TS 103 120 [1], clause 9, except that the security details (ETSI TS 103 120 [1], clause... |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 6.2 Error reporting for transport | Errors relating to the transport mechanism are handled in accordance with the transport mechanism as per ETSI TS 103 120 [1]. |
a6af474049a255f8dbddc58d054dd770 | 103 707 | 7 Security | Implementations shall use HTTPS as defined in IETF RFC 9110 [10]. The TLS version shall be at least 1.2, as defined in IETF RFC 5246 [3]. TLS 1.3 may be supported, as defined in IETF RFC 8446 [5]. TLS implementations shall support mutual authentication through bidirectional certificate usage. In this regard, TLS 1.2 im... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 1 Scope | The present document specifies a set of functionalities for the support of advanced audio services over the DECT air interface. All DECT devices claiming to be compliant with this application profile will offer at least the services defined as mandatory. In addition to these, optional features can be implemented to off... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 2 References | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 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... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 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... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 3 Definition of terms, symbols and abbreviations | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 3.1 Terms | For the purposes of the present document, the following terms apply: codec frame: portion of the media for a single channel, e.g. speech or audio or a combination thereof, that is input to the encoder or output of the decoder for one channel NOTE: A codec frame includes a codec frame duration of audio (see codec frame ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: BS Slow Broadcast channel C Conditional to support (process mandatory) CF higher layer signalling Channel (fast) CS higher layer signalling Channel (slow) I out-of-scope (provision optional, process optional) not subject for testing IN higher layer ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AA Advanced Audio AAP Advanced Audio Profile AC Authentication Code ETSI ETSI TS 103 706 V1.1.1 (2022-01) 12 AES Advanced Encryption Standard A-MAP A-field Mapping A-VOL Adaptive-Volume BPSK Binary Phase Shift Keying CC Call Control CN Carrier... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 4 Description of services | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 4.1 Introduction | In DECT standards such as GAP [9] and NG-DECT [i.6] the primary audio application is telephony. With the availability of improved audio codecs such as LC3plus [10] and changes in the DECT base standard [2] to [8] to enable asymmetric data rates and lower latency, new application areas can be addressed. In this profile ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 4.2 High level application requirements | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 4.2.1 Wireless speakers/headphones | In this application, the fixed part is connected to an audio source, e.g. a television or personal computer, and each portable part is connected to one or more speakers or to one or more headphones. There is audio transmission in downlink direction only, with the uplink direction being used only for control information... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 4.2.2 Wireless high-resolution headphones | In this application, the fixed part is connected to an audio source streaming high-resolution audio content, e.g. 96 kHz sampling rate and 24 bits per sample, and each portable part is connected to one or more headphones. There is audio transmission in downlink direction only, with the uplink direction being used only ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 4.2.3 Wireless gaming headsets | In this application the fixed part is connected to a gaming console, personal computer or similar, while the portable part is connected to a headset. In the downlink direction, the characteristics of the headsets are similar to those of wireless speakers in clause 4.2.1. In addition, there is an audio path in the uplin... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 4.2.4 Wireless smart speakers | In this application the fixed part is connected to an internet connected device, while the portable part is connected to the smart speaker. In the downlink direction, the characteristics of the smart speaker are similar to those of wireless speakers in clause 4.2.1. In addition, there is an audio path in the uplink whi... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 4.2.5 Professional wireless microphones | In this profile an LC3plus based wireless microphone is specified. However, other professional wireless microphones using proprietary codecs also exist. For these devices, no interoperability is expected and hence all requirements are optional and should only be considered as best practices. In this application the fix... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 5 Service and feature definitions | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 5.1 Audio coding definitions | For the purposes of the present document, the following definitions shall apply: LC3plus codec: LC3plus is standardized as ETSI TS 103 634 [10]. The LC3plus codec is designed for very high audio quality for all kinds of audio signals, i.e. speech and music. For regular 16 bit music encodings at 48 kHz sampling rate, LC... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 5.2 Audio feature definitions | For the purposes of the present document, the following definitions shall apply: Mono compatibility [AA.AF.1]: Capability to provide one-channel mono signal, usually on PCM level, in case more channels are available at the audio origin. This feature is required for instance, if an FT transmits stereo content to a PT su... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 5.3 PHL service definitions | For the purposes of the present document, the following definitions shall apply: 2 level GFSK modulation [AA.P.1]: 2 level Gaussian Frequency Shift Keying (GFSK) modulation as defined by ETSI EN 300 175-2 [2], clause 5. π/2-DBPSK modulation [AA.P.2]: 2 level Differential Binary Phase Shift Keying (DBPSK) modulation as ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 5.4 MAC service definitions | For the purposes of the present document, the definitions of ETSI EN 300 444 [9], clause 5.2 plus the following shall apply: IN_normal delay symmetric MAC service type [AA.M.1]: IN_normal delay symmetric connection as defined in ETSI EN 300 175-3 [3], clause 5.6.2.1. IN_normal delay asymmetric MAC service type [AA.M.2]... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 5.5 DLC service definitions | For the purposes of the present document, the definitions of ETSI EN 300 444 [9], clause 5.1 plus the following shall apply: LU1 Transparent UnProtected service (TRUP) Class 0 [AA.D.1]: Transparent unprotected service, transmission Class 0 as defined by ETSI EN 300 175-4 [4], clause 11.2. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 5.6 NWK feature definitions | For the purposes of the present document, the definitions of ETSI EN 300 444 [9], clause 4.1, plus the following shall apply: PT Initiated Advanced Audio Call [AA.N.1]: Advanced audio call initiated by the PT. FT Initiated Advanced Audio Call [AA.N.2]: Advanced audio call initiated by the FT. Advanced Audio Call Releas... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 5.7 Application feature definitions | For the purposes of the present document, the definitions of ETSI EN 300 444 [9], clause 4.3 plus the following shall apply: Easy pairing registration [AA.A.1]: Ability to register a PT that is not registered to a FT by pressing a physical or logical button on the PT and on the FT. Head tracking [AA.A.2]: Ability to pr... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6 Profile specific requirements | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.1 General | Table 10 to Table 20 define the status of all protocol elements (i.e. features, services and procedures), which can be: mandatory, optional, conditional under the provision of another protocol element, outside the scope of the present document, or not applicable. The status is identified by the status designations defi... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.2 Specific conventions | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.2.1 Use of symbols in support status tables | The symbols defined in this clause are applied for procedures, features, and services in the present document if not explicitly otherwise stated. The interpretation of status columns in all tables is as follows: • "M" (provision mandatory, process mandatory) means that the indicated feature service or procedure shall b... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.3 Advanced audio services support status | Depending on the device type, the requirements for audio support differ as given in Table 10, Table 11 and Table 12. Table 10 specifies the audio codec and general audio feature requirements according to device types. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 22 Table 10: Audio support for specific device types Device type... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.4 Physical layer (PHL) requirements |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.