hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.4.1 PHL services | Advanced Audio Profile devices shall support the Physical layer (PHL) services described in Table 13. Table 13: Physical layer service support Item Name of service Reference Support status PT FT AA.P.1 GFSK modulation 5.3 M M AA.P.2 π/2-DBPSK modulation 5.3 O O AA.P.3 π/4-DQPSK modulation 5.3 O O AA.P.4 π/8-D8PSK modul... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.4.2 Modulation schemes | The modulation schemes defined in annex D of ETSI EN 300 175-2 [2] shall be supported as described in Table 14. Table 14: Allowed combinations of modulation schemes Modulation scheme S-field A-field B + Z-field Support status 1a GFSK GFSK GFSK M 2 π/2-DBPSK π/2-DBPSK π/4-DQPSK O 3 π/2-DBPSK π/2-DBPSK π/8-D8PSK O |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.5 MAC layer requirements | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.5.1 MAC layer services | Advanced Audio Profile devices shall support the MAC layer services given in Table 15. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 27 Table 15: MAC services status Service supported Item no. Name of service Reference Status PT FT AA.M.1 IN_normal delay symmetric MAC service type 5.4 M M AA.M.2 IN_normal delay asymmetric MAC ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.5.2 MAC layer service to procedure mapping | The MAC service to procedure mapping of ETSI EN 300 444 [9] (GAP), clause 6.8.3, applies with the changes and additional services shown in Table 16. Table 16: MAC service to procedure mapping Service/Procedure mapping Service Procedure Reference Status PT FT AA.M.1 IN_normal delay symmetric MAC service type 5.4 M M MAC... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.6 DLC layer requirements | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.6.1 DLC layer services | Advanced Audio Profile devices shall support the DLC layer services given in Table 17. Table 17: DLC services status Service supported Item no. Name of service Reference Status PT FT AA.D.1 LU1 Transparent UnProtected service (TRUP) Class 0 5.5 M M GAP.D.1 LAPC class A service and Lc 5.1 [9] M M GAP.D.2 CS channel frag... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.6.2 DLC layer service to procedure mapping | The DLC service to procedure mapping of ETSI EN 300 444 [9] (GAP), clause 6.8.2, applies with the changes and additional services shown in Table 18. Table 18: DLC service to procedure mapping Service/Procedure mapping Service Procedure Reference Status PT FT AA.D.1 LU1 Transparent UnProtected service (TRUP) Class 0 5.5... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.7 NWK layer requirements | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.7.1 NWK layer features | Advanced Audio Profile devices shall support the NWK layer services given in Table 19. Note that GAP features which are not listed here are not applicable for Advanced Audio Profile devices but may be supported by devices which support both GAP and the Advanced Audio Profile. Table 19: NWK features status Service suppo... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.7.2 NWK layer feature to procedure mapping | The NWK feature to procedure mapping of ETSI EN 300 444 [9] (GAP), clause 6.8.1, applies with the changes and additional services shown in Table 20. Table 20: NWK feature to procedure mapping Feature/Procedure mapping Feature Procedure Reference Status PT FT AA.N.1 PT initiated advanced audio call 5.6 M M PT initiated ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.8 Application requirements | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.8.1 Application features | Advanced Audio Profile devices shall support the application features given in Table 21. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 33 Table 21: Application features status Feature supported Status Item no. Name of feature Reference PT FT AA.A.1 Easy pairing registration 5.7 O O AA.A.2 Head tracking 5.7 O O GAP.A.1 AC_bitst... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 6.8.2 Application feature to procedure mapping | The application feature to procedure mapping of ETSI EN 300 444 [9] (GAP), clause 6.8.1, applies with the changes and additional services shown in Table 22. Table 22: Application feature to procedure mapping Feature/Procedure mapping Feature Procedure Reference Status PT FT AA.A.1 Easy pairing registration 5.7 M O Gene... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7 Profile specific procedure descriptions | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.1 General | The following clauses define the process mandatory procedures which are in the scope of the Advanced Audio Profile. Each procedure (if appropriate) is divided into three parts: a) normal (i.e. successful) case(s). This part defines the functions and respective protocol element values in normal operation; b) associated ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.2 Requirements regarding the audio transmission | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.2.1 General | The applicable requirements specified in ETSI EN 300 175-8 [8] shall be applied according to their status as defined in clause 6.3. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.2.2 Audio codecs | The FT and PT shall support the LC3plus codec as specified in ETSI TS 103 634 [10] with configurations according to the device type as defined in clause 6.3. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.2.3 Audio performance requirements | The FT and PT shall support the maximum end-to-end-delay as defined in clause 5.2. The FT shall support FP audio type 5 as defined in clause 5.2. The PT shall support the PP audio types according to its device type and audio codec support as defined in clause 6.3. All requirements specified in ETSI EN 300 175-8 [8] and... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.3 Physical (PHL) layer requirements | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.3.1 General | All requirements specified in ETSI EN 300 444 [9] (GAP), clause 11, shall apply. All requirements specified in ETSI EN 300 175-2 [2] and ETSI EN 301 406 [12] for the supported modulation types shall apply. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.3.2 Modulation | The FT and PT shall support 2 level Gaussian Frequency Shift Keying (GFSK) modulation as defined in ETSI EN 300 175-2 [2], clause 5. The FT and PT may support 2 level Differential Binary Phase Shift Keying (π/2-DBPSK) modulation as defined in ETSI EN 300 175-2 [2], clause D.1. The FT and PT may support 4 level Differen... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.3.3 Slot type (Physical packets) | The FT and PT shall support Physical packet P32 (full slot) as defined in ETSI EN 300 175-2 [2], clause 4.4.2. The FT and PT shall support Physical packet P00j (variable slot) as defined in ETSI EN 300 175-2 [2], clause 4.4.3, with a j value of j = 640. The FT and PT may support Physical packet P80 (double slot) as def... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.3.4 Transmitted power management | To avoid mutual interference between data terminals operating in different local DECT networks when using for the transmission most of the slots from a frame, control of the transmission power is recommended. If transmission power control procedure is implemented, the requirements in ETSI EN 300 175-2 [2], annex E shal... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.3.5 Fast hopping radio | The radio transceiver shall be able to perform any frequency change during the interval between two consecutive Physical Packets P32 (full slot) or P80 (double slot) if this feature is supported. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.3.6 Radio receiver category B | The radio receiver shall fulfil the performance requirements defined in ETSI EN 300 175-2 [2], annex G if this feature is supported. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4 Medium Access Control (MAC) layer procedures | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.1 General | This clause specifies the additional MAC layer procedures, messages and information elements required for the Advanced Audio Profile which are not described in ETSI EN 300 444 [9] (GAP) or which incorporate modifications to the GAP specification. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.2 MAC services | NOTE: This description, together with clause 7.4.3, replaces clause 10.1 of ETSI EN 300 444 [9] (GAP). The FT and PT shall support the IN_normal_delay symmetric service as defined in ETSI EN 300 175-3 [3], clauses 5.6.2.1 and 10.8.3.2. The FT and PT shall support the IN_normal_delay asymmetric service as defined in ETS... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.3 Frame formats and multiplexers | NOTE: This description, together with clause 7.4.2, replaces clause 10.1 of ETSI EN 300 444 [9] (GAP). The FT and PT shall support the following frame formats: • D-field mapping for the full slot structure (physical packet P32), as defined in ETSI EN 300 175-3 [3], clause 6.2.1.1.2. • D-field mapping for the variable s... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.4 Downlink broadcast | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.4.1 General | NOTE: This procedure description replaces clause 10.2 of ETSI EN 300 444 [9] (GAP). The procedure shall be performed as defined in ETSI EN 300 175-3 [3], clause 9.1.1. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.4.2 NT messages | The same message defined in ETSI EN 300 444 [9] (GAP), clause 10.2.1 shall be used. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.4.3 QT - static system information | The FT shall be capable of sending and the PT shall be capable of receiving and processing the QT message as defined in ETSI EN 300 175-3 [3], clause 7.2.3.2, with the values shown in Table 23. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 37 Table 23: Values used within static system info MAC message Field within the message ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.4.4 QT - Fixed Part capabilities | The FT shall be capable of sending and the PT shall be capable of receiving and processing the QT message as defined in ETSI EN 300 175-3 [3], clause 7.2.3.4, with the values shown in Table 24. Table 24: Values used within FP capabilities MAC message Field within the message Standard values within the MAC message Norma... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.4.5 QT - Extended Fixed Part capabilities | The FT shall be capable of sending and the PT shall be capable of receiving and processing the QT message as defined in ETSI EN 300 175-3 [3], clause 7.2.3.5, with the values shown in Table 25. Table 25: Values used within Extended FP capabilities MAC message Field within the message Standard values within the MAC mess... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.4.6 QT - Extended Fixed Part capabilities part 2 | The FT shall be capable of sending and the PT shall be capable of receiving and processing the QT message as defined in ETSI EN 300 175-3 [3], clause 7.2.3.11, with the values shown in Table 26. Table 26: Values used within Extended FP capabilities part 2 MAC message Field within the message Standard values within the ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.4.7 QT - Extended Fixed Part capabilities part 3 | If high level modulation is supported then the FT shall be capable of sending and the PT shall be capable of receiving and processing the QT message as defined in ETSI EN 300 175-3 [3], clause 7.2.3.13, with the values shown in Table 27. Table 27: Values used within Extended FP capabilities part 3 MAC message Field wit... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.4.8 QT - SARI list contents | The FT may send and the PT shall be capable of receiving and processing (if broadcast by the FT) the QT SARI message as defined in ETSI EN 300 175-3 [3], clause 7.2.3.6, with same contents as defined by ETSI EN 300 444 [9] (GAP), clause 10.2.4. This is relevant if the NT message indicates SARI support. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.5 Paging broadcast | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.5.1 General | NOTE: This procedure description replaces clause 10.3 of ETSI EN 300 444 [9] (GAP). The procedure shall be performed as defined in ETSI EN 300 175-3 [3], clause 9.1.3. SHORT page, ZERO page and FULL page formats shall be supported. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.5.2 Short page, normal/extended paging | The fields shown in Table 28 and defined in ETSI EN 300 175-3 [3], clauses 7.2.4.1.2, 7.2.4.2 and 7.2.4.3, shall be supported by the PT and the FT. Table 28: Values used within short page message MAC message Field within the message Standard values within the MAC message Normative action/comment <<Short page message>> ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.5.3 Zero page normal/extended paging | The fields shown in Table 29 and defined in ETSI EN 300 175-3 [3], clauses 7.2.4.1.3, 7.2.4.2 and 7.2.4.3, in the zero page message, shall be supported by the PT and the FT. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 40 Table 29: Values used within zero page message MAC message Field within the message Standard values withi... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.5.4 Full page, normal/extended paging | The fields shown in Table 30 and defined in ETSI EN 300 175-3 [3], clauses 7.2.4.1.1 and 7.2.4.2, in the full page message, shall be supported by the PT and the FT. Table 30: Values used within full page message MAC message Field within the message Standard values within the MAC message Normative action/comment <<Full ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.5.5 Blind slot information | It is mandatory for RFPs that have blind slots due to technological limitations such as a slow synthesizer to periodically announce these blind slots (at least every 10 s). In the event the RFP announces blind slot information, such information may also include all blind slots due to an active bearer as well. Not avail... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.5.6 Bearer handover information | It is mandatory for FTs not supporting bearer handover within the whole FT to periodically send the bearer handover information (at least every 10 s). It is mandatory for PT to support the following values of field "Info type" (bits a36 to a39) for "Bearer handover information" (value "9" of <Information type> in the P... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.6 Setup of symmetric advanced connection, duplex bearer setup | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.6.1 General | NOTE: This procedure description replaces clause 10.4 of ETSI EN 300 444 [9] (GAP). The symmetric connection setup procedure shall be performed as defined in ETSI EN 300 175-3 [3], clauses 10.2.4.1 and 10.2.4.2. The "single bearer duplex connection of known service type" setup procedure described in ETSI EN 300 175-3 [... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.6.2 MT messages | The fields shown in Table 31, Table 32 and defined in ETSI EN 300 175-3 [3], clause 7.2.5.3 of in the MAC control (MT) message shall be supported by the PT and the FT. Table 31: Values used within MT message - Setup messages MAC message Field within the message Standard values within the MAC message Normative action/co... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.6.3 Associated procedures | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.6.3.1 Timer T200 management | T200: Connection setup timer; Value: Refer to ETSI EN 300 175-3 [3], annex A; Start: At the creation of an MBC; Stop: The TBC reports "bearer_established" or on request for MAC connection release. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.6.3.2 Counter N200 management | N200: Max. number bearer setup re attempts during connection setup; Value: Refer to ETSI EN 300 175-3 [3], annex A; Start: ACCESS_REQUEST is sent; Change: A new ACCESS_REQUEST within the same connection setup attempt is sent; Clear: The TBC reports "bearer_established" or on request for MAC connection release. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.6.4 Exceptional cases | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.6.4.1 Bearer setup attempt fails N200+1 times | Figure 1 shows the case when a bearer setup attempt fails N200+1 times. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 43 PT FT 1st access request (possible exchange) MAC_CON-req (possible exchange) 1st setup attempt failed 2nd access request . . . . (N200+1)th access request (N200+1)th setup attempt failed MAC_RES_DLC-ind MAC_... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.6.4.2 Timer T200 expiry | Figure 2 shows the case when the timer T200 expires. PT FT 1st access request (possible exchange) MAC_CON-req (possible exchange) 1st setup attempt failed 2nd access request . . . . (less than N200+1)th access request MAC_RES_DLC-ind MAC_RES_DLC-ind MAC_DIS-ind . . T200 Figure 2: Timer T200 expiry |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.7 Setup of asymmetric advanced connection | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.7.1 General | The asymmetric connection setup procedure shall be performed as defined in ETSI EN 300 175-3 [3], clauses 10.2.4.1 and 10.2.4.3. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 44 At establishment of the connection, a symmetric connection is initially established as described in clause 7.4.6. The duplex bearer established here i... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.7.2 Associated procedures | The procedures for the handling of Timer T200 and counter N200, as described in clause 7.4.6.3, shall also be supported for asymmetric connections. The N200 counter applies per bearer in this case, as described in ETSI EN 300 175-3 [3], clause 10.2.4.3.0. Furthermore, the procedures for slot type modification (see clau... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.7.3 Exceptional cases | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.7.3.1 Bearer setup attempt fails N200+1 times | Failure to setup any of the required bearers after N200+1 attempts (per bearer) will result in connection release as described in clause 7.4.6.4.1 and ETSI EN 300 175-3 [3], clause 10.2.4.3.0. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.7.3.2 Timer T200 expiry | Expiry of the T200 timer before successful connection setup will result in connection release as described in clause 7.4.6.4.2 and ETSI EN 300 175-3 [3], clause 10.2.4.3.0. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.7.3.3 Insufficient bandwidth available | If the bandwidth modification procedure fails due to the minimum number of target bearers not being achieved, as described in clause 7.4.9, then the connection shall be released and the failure reported to higher layers as described in ETSI EN 300 175-3 [3], clause 10.2.4.3.0. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.8 Slot type modification | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.8.1 General | After invocation of the NWK layer procedure for slot type modification (see clause 7.6.13), the modification shall be executed using the MAC layer procedure for slot type modification. The MAC slot type change procedure shall be executed as described in ETSI EN 300 175-3 [3], clause 10.3.2. The FT shall always initiate... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.8.2 Failure of slot type modification | On failure of the slot type modification the initiating side shall not release the connection, but shall keep the existing slot type, and shall report the failure to higher layers. The NWK layer shall handle the case as described in clause 7.6.13.2. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.9 Bandwidth modification | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.9.1 General | After invocation of the NWK layer procedure for bandwidth modification (see clause 7.6.14), or during connection setup for a multibearer connection, the modification shall be executed using the MAC layer procedure for bandwidth modification. The MAC bandwidth change procedure shall be executed as described in ETSI EN 3... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.9.2 Mt Messages | The fields shown in Table 33 and defined in ETSI EN 300 175-3 [3], clause 7.2.5.3, in the MAC control (MT) message shall be supported by the PT and the FT. Table 33: Values used within MT message - Bandwidth_T_request/confirm MAC message Field within the message Standard values within the MAC message Normative action/c... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.9.3 Associated procedures | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.9.3.1 General | The overall procedure is as shown in Figure 3. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 46 MAC_MOD-req MAC_MOD-cfm PT FT Bandwidth_T_Cfm Bandwidth_T_Req Release of excess bearers MAC_MOD-ind Setup of new bearers Figure 3: Bandwidth modification procedure For details of the bearer release and setup procedures, refer to cla... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.9.3.2 Timer T211 management | T211: Connection modification timer; Value: Refer to ETSI EN 300 175-3 [3], annex A; Start: When the number of new bearers is less than the minimum number of required bearers; Stop: The TBC for the last double simplex bearer reports "bearer_established" or on request for MAC connection release. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.9.4 Exceptional cases | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.9.4.1 Timer T211 expiry | In case the minimum number of target bearers cannot be met before timer T211 expiry, the connection is released as shown in Figure 4. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 47 MAC_MOD-req MAC_DIS-ind PT FT Bandwidth_T_Cfm Bandwidth_T_Req Release of excess bearers MAC_DIS-ind Incomplete setup of new bearers Release proce... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.10 Double simplex bearer setup | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.10.1 General | The double simple bearer setup is used to increase the bandwidth during a bandwidth modification procedure. The steps in this procedure are as follows: • Channel selection for the new bearers shall be performed by the FT as defined in ETSI EN 300 175-3 [3], clause 10.5.1.4.3. Optionally, the FT may additionally request... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.10.2 Mt Messages | The fields shown in Table 34, Table 35 and Table 36 and defined in ETSI EN 300 175-3 [3], clause 7.2.5.3, in the MAC control (MT) message shall be supported by the PT and the FT. Table 34: Values used within MT message - Unconfirmed access request MAC message Field within the message Standard values within the MAC mess... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.10.3 Associated procedures | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.10.3.1 Uplink double simplex bearer setup | The setup of each double simplex bearer shall follow the procedure defined in ETSI EN 300 175-3 [3], clause 10.5.1.4 with the additional restrictions defined in this clause. The sequence and mapping of messages to the duplex and double simplex bearers shall be as shown in Figure 5. Other variations of the signalling ar... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.10.3.2 Downlink double simplex bearer setup | The setup of each double simplex bearer shall follow the procedure defined in ETSI EN 300 175-3 [3], clause 10.5.1.4 with the additional restrictions defined in this clause. The sequence and mapping of messages to the duplex and double simplex bearers shall be as shown in Figure 6. Other variations of the signalling ar... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.10.3.3 Timer T212 management | T212: Double simplex bearer setup acknowledge timer; Value: Refer to ETSI EN 300 175-3 [3], annex A; Start: At T-Side: Transmission of the first bearer request message At R-Side: One frame after transmission or reception of the Channel list (LISTEN or START) message, or one frame after the Attributes_T_Req if present. ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.10.4 Exceptional cases | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.10.4.1 Timer T212 Expiry | If the bearer setup does not succeed before timer T212 expiry, the connection is released. An example of a case where the timer expires at the T-Side, resulting in unacknowledged release, is shown in Figure 7. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 52 PT FT Bearer request (on double simplex bearer, both slots) T212 X Be... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.10.4.2 Channel selection for uplink double simplex bearer fails at PT | Upon reception of a LISTEN channel list message, the PT shall check the channel is still acceptable before starting transmission, as defined in ETSI EN 300 175-3 [3], clause 11.4.2. If the channel is no longer acceptable, then is shall respond to the LISTEN channel list message with a POOR channel list message as shown... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.11 Connection release | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.11.1 General | NOTE 1: This procedure description replaces the connection related aspects of clause 10.5 of ETSI EN 300 444 [9] (GAP). The procedure shall be performed as defined in ETSI EN 300 175-3 [3], clause 10.4. The procedure may be used if the connection is either basic or advanced. Unacknowledged bearer release shall always b... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.12 Bearer release | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.12.1 General | NOTE: This procedure description replaces the bearer related aspects of clause 10.5 of ETSI EN 300 444 [9] (GAP). The procedure shall be performed as defined in ETSI EN 300 175-3 [3], clauses 10.7.2. The procedure may be used if the connection is either basic or advanced. For duplex bearers, unacknowledged bearer relea... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.12.2 MT message | The fields shown in Table 37 and defined in ETSI EN 300 175-3 [3], clauses 7.2.5.2 and 7.2.5.3 in the MAC control (MT) message shall be supported by the PT and the FT. Table 37: Values used within MT message MAC message Field within the message Standard values within the MAC message Normative action/comment <<MT messag... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.12.3 Associated Procedures | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.12.3.1 Unacknowledged Bearer Release | The procedure defined in ETSI EN 300 175-3 [3], clause 10.7.2.1, shall be used for release of a duplex bearer or release of a double simplex bearer from the T-side. In the example of Figure 10 it is assumed that the bearer to be released is either a duplex bearer or an uplink double simplex bearer. PT FT Bearer release... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.12.3.2 Acknowledged Bearer Release | The procedure defined in ETSI EN 300 175-3 [3], clause 10.7.2.2, shall be used for release of a double simplex bearer from the R-side. In the example of Figure 11 it is assumed that the bearer to be released is an uplink double simplex bearer. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 56 PT FT Bearer release (on duplex bea... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.12.3.3 Timer T213 management | T213: Double simplex bearer setup release timer; Value: Refer to ETSI EN 300 175-3 [3], annex A; Start: At R-Side: Transmission of a bearer release message for a double simplex bearer, on the duplex bearer; Stop: At R-Side: Reception of a bearer release message on the double simplex bearer. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.12.4 Exceptional cases | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.12.4.1 T213 expiry | The procedure defined in ETSI EN 300 175-3 [3], clause 10.7.2.2, shall be used in case T213 expires, as shown in Figure 12. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 57 PT FT Bearer release (on duplex bearer, LBN of double simplex bearer) Bearer release (on double simplex bearer, both slots) Bearer release (on double simpl... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.13 Bearer handover - duplex | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.13.1 General | NOTE 1: This procedure description replaces clause 10.6 of ETSI EN 300 444 [9] (GAP). The procedure may be initiated by the PT or the FT and shall be performed as defined in ETSI EN 300 175-3 [3], clauses 10.6.2 and 10.5.1.1. NOTE 2: Duplex bearer handovers are typically initiated by the PT but may be initiated by the ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.13.2 MT message | The fields shown in Table 38 and Table 39 and defined in ETSI EN 300 175-3 [3], clauses 7.2.5.2 and 7.2.5.3, in the MAC control (MT) message shall be supported by the PT and the FT. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 58 Table 38: Values used within MT message - bearer setup MAC message Field within the message Stand... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.13.3 Exceptional cases | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.13.3.1 Channel selection for uplink duplex bearer fails at PT | Upon reception of a LISTEN channel list message in an FT initiated bearer handover, the PT shall check the channel is still acceptable before starting transmission, as defined in ETSI EN 300 175-3 [3], clause 11.4.2. If the channel is no longer acceptable, then it shall respond to the LISTEN channel list message with a... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.