hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.14 Bearer handover - double simplex | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.14.1 General | The procedure shall be performed as defined in ETSI EN 300 175-3 [3], clauses 10.6.3 and 10.5.1.4. The procedure is only supported for intra-cell handover. Inter-cell handovers shall use connection handover to move all bearers to the new cell, see clause 7.4.17. If the handover space is restricted, as configured in the... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.14.2 MT message | The fields shown in Table 40 to Table 43 and defined in ETSI EN 300 175-3 [3], clauses 7.2.5.3 and 7.2.5.5 in the MAC control (MT) message shall be supported by the PT and the FT. Table 40: Values used within MT message - Unconfirmed handover request MAC message Field within the message Standard values within the MAC m... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.14.3 Associated Procedures | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.14.3.1 FT initiated bearer handover | FT initiated double simplex bearer handover uses the bearer establishment procedures defined in clause 7.4.10.3 with the following modifications: • The bearer request message used shall be an unconfirmed handover request instead of an unconfirmed access request. • The LBN used shall be the value of the bearer for which... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.14.3.2 PT request for bearer handover | The PT can request a handover for a downlink double simplex bearer using a quality control message as described in ETSI EN 300 175-3 [3], clause 10.6.3.2. The FT may then perform the handover as described in clause 7.4.14.3.1 or may reject the attempt using a further quality control message. The sequence and mapping of... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.15 Frequency replacement - duplex bearer | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.15.1 General | The procedure shall be performed as defined in ETSI EN 300 175-3 [3], clause 10.6.4.2. The procedure is only supported for intra-cell operation. Inter-cell handovers shall use connection handover to move all bearers to the new cell, see clause 7.4.17. NOTE: Frequency replacement has no fallback in case of failure. Henc... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.15.2 MT message | The fields shown in Table 44 and defined in ETSI EN 300 175-3 [3], clause 7.2.5.5 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) 63 Table 44: Values used within MT message - Quality control frequency replacement MAC message Field within the message Standar... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.15.3 Associated Procedures | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.15.3.1 Duplex bearer frequency replacement | The procedure defined in ETSI EN 300 175-3 [3], clause 10.6.4.2 and shown in Figure 17, shall be used for duplex bearer frequency replacement. PT FT Quality Control (Frequency replacement grant) (on new duplex bearer) Quality Control (Frequency replacement confirm) (on new duplex bearer) Quality Control (Frequency repl... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.15.4 Exceptional cases | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.15.4.1 Frequency replacement confirm not detected | If, after N206 repetitions of the frequency replacement request, no confirm message is received, then the PT shall release the duplex bearer and the connection, and the higher layers shall be informed. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.15.4.2 Frequency replacement grant not detected | If, after N207 repetitions of the frequency replacement confirm, no grant message is received, then the FT shall release the duplex bearer and the connection, and the higher layers shall be informed. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 64 |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.16 Frequency replacement - double simplex | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.16.1 General | The procedure shall be performed as defined in ETSI EN 300 175-3 [3], clause 10.6.4.2. The procedure is only supported for intra-cell operation. Inter-cell handovers shall use connection handover to move all bearers to the new cell, see clause 7.4.17. NOTE: Frequency replacement has no fallback in case of failure. Henc... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.16.2 MT message | The fields shown in Table 44 and Table 45 and defined in ETSI EN 300 175-3 [3], clause 7.2.5.5 in the MAC control (MT) message shall be supported by the PT and the FT. Table 45: Values used within MT message - Double simplex bearer request MAC message Field within the message Standard values within the MAC message Norm... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.16.3 Associated Procedures | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.16.3.1 Double simplex bearer frequency replacement | The procedure defined in ETSI EN 300 175-3 [3], clause 10.6.4.2 and shown in Figure 18, shall be used for uplink double simplex bearer frequency replacement. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 65 PT FT Bearer request (on double simplex bearer, both slots) Quality Control (Frequency replacement grant) (on duplex bear... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.16.3.2 Timer T212 management | Timer T212 is handled for frequency replacement in the same way as for bearer setup, where the frequency replacement request, confirm and grant replace the LISTEN, START and ACTIVE channel list messages respectively. See clause 7.4.10.3.3. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.16.4 Exceptional cases | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.16.4.1 Timer T212 Expiry | Timer T212 is handled for frequency replacement in the same way as for bearer setup, see clause 7.4.10.4.1. Upon release of the bearer, a new bearer setup attempt may be started by the FT in order to reach the target bandwidth, as described in clause 7.4.9. Failure to setup a new bearer will result in connection releas... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.17 Connection handover | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.17.1 General | NOTE: This procedure description replaces clause 10.7 of ETSI EN 300 444 [9] (GAP). The procedure consists of two steps: • A connection establishment for the handover connection, using the procedures described in clauses 7.4.6 and 7.4.7. • A release of the old connection as described in clause 7.4.11. The procedure may... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.17.2 MT message | The fields shown in Table 46 and defined in ETSI EN 300 175-3 [3], clause 7.2.5.2 in the MAC control (MT) message shall be supported by the PT and the FT. Table 46: Values used within MT message MAC message Field within the message Standard values within the MAC message Normative action/comment <<MT message>> <MT heade... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.4.18 Audio data transfer | Audio data from the LC3plus codec shall be mapped to the bearers according to the audio configuration as described in annex B. If multiple simplex bearers are required to carry a single audio frame then the audio frame shall be split into segments and assigned to bearers using according to LBN as described in ETSI EN 3... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.5 Data Link Control (DLC) layer procedures | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.5.1 General | This clause specifies the additional DLC layer procedures, messages and information elements which are required for advanced audio services not described in ETSI EN 300 444 [9] (GAP) or which incorporate modifications to the GAP specification. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.5.2 FU1 frame operation | The procedure shall be performed as defined in ETSI EN 300 175-4 [4], clauses 12.1 and 12.2. The following text together with the associated clauses define the mandatory requirements with regard to the present document. PT FT FU1 frame MAC_CO_DATA-req MAC_CO_DATA-ind Figure 20: Sending a FU1 frame NOTE: The case when F... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6 Network (NWK) layer procedures | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.1 General | This clause specifies the additional NWK layer procedures, messages and information elements required in the Advanced Audio Profile which are not described in ETSI EN 300 444 [9] (GAP), or which incorporate modifications to the GAP specification. This profile does not prevent any PT or FT from transmitting or receiving... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.2 Summary of PT initiated call messages | NOTE: This summary description replaces clause 8.1 of ETSI EN 300 444 [9] (GAP). Figure 21 shows a summary of the PT initiated call related message sequence. PT FT CC-SETUP CC-CONNECT T-00 T-01 T-10 F-00 F-01 F-10 Figure 21: PT initiated call messages |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.3 PT initiated call request | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.3.1 Procedure | NOTE: This procedure description replaces clause 8.2 of ETSI EN 300 444 [9] (GAP). The procedure shall be performed as defined in ETSI EN 300 175-5 [5], clauses 9.3.1, 9.3.1.1 and 9.3.1.2. Figure 22 and Table 47 together with the associated clauses define the mandatory requirements with regard to the present document. ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.3.2 Associated procedures | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.3.2.1 Timer P-<CC.03> management | <CC.03>: CC setup timer; value: refer to ETSI EN 300 175-5 [5], annex A; start: a {CC-SETUP} message has been sent; stop: an indication for release or reject from the IWU or for link release from the DLC layer is received. A {CC-CONNECT} or {CC-RELEASE-COM} message is received; restart: FT may restart it at any time by... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.3.3 Exceptional cases | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.3.3.1 Timer P-<CC.03> expiry | The abnormal call release procedure shall be used (see clause 7.6.9) as shown in Figure 23. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 71 PT FT CC-SETUP T-00 T-01 F-00 CC.03 CC-RELEASE-COM T-00 NOTE: FT may not be answering because of some FT problems or because the {CC-SETUP} message has been lost or corrupted. The same re... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.3.3.2 PT releases the PT initiated call request | The normal call release procedure shall be used (see clause 7.6.8) as shown in Figure 24. PT FT CC-SETUP CC-RELEASE-COM T-00 T-01 T-19 F-00 F-01 F-01 T-00 F-00 CC-RELEASE Figure 24: PT releases the PT initiated call request For the values used within {CC-SETUP} see Table 47. For the contents of {CC-RELEASE} and {CC-REL... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.3.3.3 FT rejects the PT initiated call request | The abnormal call release procedure shall be used (see clause 7.6.9) as shown in Figure 25. PT FT CC-SETUP CC-RELEASE-COM T-00 T-01 F-00 F-01 T-00 F-00 NOTE: Either F-CC or the F-IWU may reject the call. Figure 25: FT rejects the PT initiated call request For the contents of {CC-RELEASE-COM} see Table 51. The contents ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.4 PT initiated call connection | NOTE: This procedure description replaces clause 8.6 of ETSI EN 300 444 [9] (GAP). The procedure shall be performed as defined in ETSI EN 300 175-5 [5], clauses 9.3.1.8 and 9.3.1.4. Figure 26 and Table 48 together with the associated clauses define the mandatory requirements with regard to the present document. Before ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.5 Summary of FT initiated call messages | NOTE: This summary description replaces clause 8.11 of ETSI EN 300 444 [9] (GAP). ETSI ETSI TS 103 706 V1.1.1 (2022-01) 74 Figure 27 shows a summary of the FT initiated call related message sequence. PT FT CC-CONNECT CC-SETUP T-00 T-06 T-08 F-00 F-06 F-10 CC-CONNECT-ACK T-10 F-10 Figure 27: FT initiated call messages |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.6 Indirect FT initiated call request | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.6.1 Procedure | NOTE 1: This procedure description replaces clause 8.12 of ETSI EN 300 444 [9] (GAP). The procedure shall be performed as defined in ETSI EN 300 175-5 [5], clauses 9.3.2, 9.3.2.1 and 9.3.2.2. Figure 28 and Table 47 together with the associated clauses define the mandatory requirements with regard to the present documen... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.6.2 Associated procedure | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.6.2.1 Timer F-<CC.03> management | <CC.03>: CC setup timer; value: refer to ETSI EN 300 175-5 [5], annex A; start: a {CC-SETUP} message has been sent; stop: an indication for release from the IWU or for link release from the DLC layer is received. A {CC-CONNECT} or {CC-RELEASE-COM} message is received. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 75 |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.6.3 Exceptional cases | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.6.3.1 FT releases the FT initiated call request | The normal release procedure shall be used (see clause 7.6.8) as shown in Figure 29. PT FT CC-RELEASE-COM CC-SETUP T-00 T-06 T-06 F-00 F-06 F-19 CC-RELEASE T-00 F-00 Figure 29: FT releases the FT initiated call request For the values used within the {CC-SETUP} see Table 47. For the contents of {CC-RELEASE} and {CC-RELE... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.6.3.2 PT rejects the FT initiated call request | The abnormal release procedure shall be used (see clause 7.6.9) as shown in Figure 30. PT FT CC-RELEASE-COM CC-SETUP T-00 T-06 F-00 F-06 T-00 F-00 NOTE: Either PT-CC or PT-IWU may reject the call. Figure 30: PT rejects the FT initiated call request For the values used within the {CC-SETUP} see Table 47. For the content... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.6.3.3 Timer F-<CC.03> expiry | The abnormal release procedure shall be used (see clause 7.6.9) as shown in Figure 31. PT FT CC-SETUP T-00 F-00 F-06 F-00 CC.03 CC-RELEASE-COM NOTE: PT may not be answering because of some PT problems or because the {CC-SETUP} message has been lost or corrupted. The same result will occur if the eventual answer from th... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.7 FT initiated call connection | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.7.1 Procedure | NOTE: This procedure description replaces clause 8.15 of ETSI EN 300 444 [9] (GAP). The procedure shall be performed as defined in ETSI EN 300 175-5 [5], clause 9.3.2.8. Figure 32 and the following text together with the associated clauses define the mandatory requirements with regard to the present document. PT FT CC-... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.7.2 Associated procedure | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.7.2.1 Timer P-<CC.05> management | <CC.05>: CC connect timer; value: refer to ETSI EN 300 175-5 [5], annex A; start: a {CC-CONNECT} message has been sent; stop: an indication for release from the IWU or for link release from the DLC layer is received. A {CC-CONNECT-ACK} or {CC-RELEASE} message is received; restart: FT may restart it at any time by sendi... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.7.3 Exceptional cases | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.7.3.1 FT releases the FT initiated call transaction | The normal release procedure shall be used (see clause 7.6.8) as shown in Figure 33. PT FT CC-CONNECT T-06 T-08 F-06 F-10 CC-RELEASE T-08 F-19 CC-RELEASE-COM T-00 F-00 Figure 33: FT releases the FT initiated call transaction For the values used within the {CC-CONNECT} see Table 48. For the contents of {CC-RELEASE} and ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.7.3.2 PT releases the FT initiated call transaction | The normal release procedure shall be used (see clause 7.6.8) as shown in Figure 34. PT FT CC-CONNECT T-06 T-08 F-06 F-10 CC-RELEASE-COM T-19 F-10 CC-RELEASE T-00 F-00 Figure 34: PT releases the FT initiated call transaction For the values used within the {CC-CONNECT} see Table 48. For the contents of {CC-RELEASE} and ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.7.3.3 Timer P-<CC.05> expiry | The normal release procedure shall be used (see clause 7.6.8) as shown in Figure 35. PT FT CC-CONNECT T-06 T-08 F-06 F-10 CC-RELEASE-COM T-19 F-10 CC-RELEASE T-00 F-00 CC.05 NOTE: FT may not be answering because of some FT problems or because the {CC-CONNECT} message has been lost or corrupted. The same result will occ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.8 Normal call release | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.8.1 Procedure | NOTE: This procedure description replaces clause 8.7 of ETSI EN 300 444 [9] (GAP). The procedure shall be performed as defined in ETSI EN 300 175-5 [5], clauses 9.5.1 and 9.5.3. Figure 36, Figure 37, Table 50 and Table 51 together with the associated clauses define the mandatory requirements with regard to the present ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.8.2 Associated procedures | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.8.2.1 Timer P-<CC.02> management | <CC.02>: CC release timer; value: refer to ETSI EN 300 175-5 [5], annex A; start: a {CC-RELEASE} message has been sent; stop: an indication for link release from the DLC layer is received. A {CC-RELEASE-COM} or a {CC-RELEASE} message is received; restart: FT may restart it at any time by sending a {CC-NOTIFY} message (... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.8.2.2 Timer F-<CC.02> management | <CC.02>: CC release timer; value: refer to ETSI EN 300 175-5 [5], annex A; start: a {CC-RELEASE} message has been sent; stop: an indication for link release from the DLC layer is received. A {CC-RELEASE-COM} or a {CC-RELEASE} message is received. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.8.3 Exceptional cases | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.8.3.1 Release collisions | A release collision occurs when both sides send {CC-RELEASE} at the same time or a {CC-RELEASE} message has been received when the receiver is in "RELEASE PENDING" state due to loss of the first sent {CC-RELEASE} message. Figure 38 and Figure 39 show possible cases. PT FT T-xx T-19 F-xx F-19 T-00 F-00 CC-RELEASE CC-REL... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.8.3.2 Timer F-<CC.02> expiry | The handling of timer F<CC.02> expiry is shown in Figure 40. PT FT CC-RELEASE T-xx T-xx F-xx F-19 T-00 F-00 CC-RELEASE-COM CC.02 NOTE: PT may not be answering because of some PT problems or the {CC-RELEASE} sent by the FT or the eventual {CC-RELEASE-COM} message sent by the PT has been lost or corrupted. Figure 40: Tim... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.8.3.3 Timer P-<CC.02> expiry | PT FT T-xx T-19 F-xx F-xx T-00 F-00 CC-RELEASE CC-RELEASE-COM CC.02 NOTE: FT may not be answering because of some FT problems or the {CC-RELEASE} sent by the PT or the eventual {CC-RELEASE-COM} message sent by the FT has been lost or corrupted. Figure 41: Timer P<CC.02> expiry For the values used within the {CC-RELEASE... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.9 Abnormal call release | NOTE: This procedure description replaces clause 8.8 of ETSI EN 300 444 [9] (GAP). The procedure shall be performed as defined in ETSI EN 300 175-5 [5], clause 9.5.2. Figure 42, Figure 43 and Table 52 together with the associated clauses define the mandatory requirements with regard to the present document. The abnorma... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.10 Exchange of codec list during registration and location registration | AAP devices shall include the IE << CODEC-LIST>> indicating the supported codecs in the following messages: {ACCESS-RIGHTS-REQUEST}, {ACCESS-RIGHTS-ACCEPT} {LOCATE-REQUEST}, {LOCATE-ACCEPT} In order to minimize the number of codecs that need to be included in the <<CODEC-LIST>>, it is only necessary to indicate the hig... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.11 Codec negotiation during call establishment | For AAP devices supporting more than one codec, codec negotiation shall be supported as described in this clause. The IE <<CODEC-LIST>> shall be added in CC-SETUP if a new list of codecs is needed on a call by call basis. This may be useful when requesting a new codec (codec different from the location/registration pha... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.12 Codec change | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.12.1 General | For AAP devices supporting more than one codec, codec change shall be supported as described in this clause in CC-state ACTIVE. To change the codec the initiating side sends a {CC-SERVICE-CHANGE} including the IE<<CODEC-LIST>> and the IE<<SERVICE-CHANGE-INFO>> as shown in Table 53. The receiving side shall either accep... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.13 Slot type modification | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.13.1 General | If a codec change requires a modification in duplex bearer slot type, the MAC slot type modification procedure shall be executed as described in clause 7.4.8 and ETSI EN 300 175-3 [3], clause 10.3.2. The FT shall always initiate this procedure. NOTE: In the case of a multibearer connection, the slot type modification i... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.13.2 Failure of slot type modification | On failure of the slot type modification the initiating side shall, where possible, not release the call but switch back to the previously active codec and indicate so to the receiving side by sending {IWU-INFO} including the IE <<CODEC-LIST>> with the old codec. On receiving this message, the receiving side shall also... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.14 Bandwidth modification | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.14.1 General | If the codec change requires a bandwidth modification, the MAC bandwidth modification procedure shall be executed as described in in clause 7.4.9 and ETSI EN 300 175-3 [3], clause 10.3.1. The FT shall always initiate this procedure. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 89 |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.14.2 Failure of bandwidth modification | On failure of the bandwidth modification the initiating side shall, where possible, not release the call but switch back to the previously active codec and indicate so to the receiving side by sending {IWU-INFO} including the IE <<CODEC- LIST>> with the old codec. On receiving this message, the receiving side shall als... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.15 Terminal capability indication | NOTE: This procedure description replaces clause 8.17 of ETSI EN 300 444 [9] (GAP). The PT shall send the <<Terminal capability>> and <<IWU-to-IWU>> information elements and the FT shall be able to receive them at least in {ACCESS-RIGHTS-REQUEST} and when location registration is supported in the {LOCATE-REQUEST}.Table... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.16 Indirect FT initiated link establishment | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.16.1 General | NOTE: This procedure description replaces clause 8.35 of ETSI EN 300 444 [9] (GAP). The procedure (shown in Figure 48) shall be performed as defined in ETSI EN 300 175-5 [5], clauses 14.2.1 and 14.2.3. The following text together with the associated clauses define the mandatory requirements with regard to the present d... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.16.2 Paging messages | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.16.2.1 LCE-REQUEST-PAGE message | FULL paging format with TPUI address structure, as defined in ETSI EN 300 175-5 [5], clause 8.2.2 shall be used, with content as shown in Table 57 . ETSI ETSI TS 103 706 V1.1.1 (2022-01) 91 Table 57: Values used within the {LCE-REQUEST-PAGE} message in case of FULL paging format with TPUI Information element Field with... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.16.2.2 LCE-PAGE-RESPONSE message | This message shall be as defined in ETSI EN 300 175-5 [5], clause 6.3.7.1 with content as shown in Table 58. Table 58: Values used within {LCE-PAGE-RESPONSE} message Information element Field within the information element Standard values within the field/information element Normative action/comment <<Protocol discrimi... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.16.3 Associated procedure | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.16.3.1 Timer F-<LCE.03> management | There shall be separate instances of a <LCE.03> timer corresponding to each IPUI identity that has been paged with {LCE-REQUEST-PAGE} message. <LCE.03>: {LCE-REQUEST-PAGE} message re submission timer; Value: Refer to ETSI EN 300 175-5 [5], annex A; Start: A {LCE-REQUEST-PAGE} message is sent; Stop: A {LCE-PAGE-RESPONSE... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.16.4 Exceptional cases | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.16.4.1 The IPUI received in the {LCE-PAGE-RESPONSE} does not match | This LCE-PAGE-REJECT message shall be used as defined in ETSI EN 300 175-5 [5], clause 6.3.7.2 and Figure 49 with content as shown in Table 59. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 93 PT FT LCE-REQUEST-PAGE LCE-PAGE-RESPONSE LCE-PAGE-REJECT Figure 49: The IPUI received in the {LCE-PAGE-RESPONSE} does not match Table 5... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.16.4.2 Timer <LCE.03> expiry | PT FT LCE-REQUEST-PAGE LCE-REQUEST-PAGE LCE.03 Figure 50: Timer <LCE.03> expiry If timer <LCE.03> expires before the wanted link is established, the LCE may resubmit the {LCE-REQUEST-PAGE} message (see Figure 50) in which case the link shall remain in the "ESTABLISH-PENDING" state. Resubmitted messages shall only be is... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.16.4.3 Release from the higher entity | If the higher entity indicates that the link resources are no longer required, the LCE shall immediately delete the outstanding IPUI and stop the corresponding timer <LCE.03>. |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.17 Higher layer information FP broadcast | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.17.1 General | The FT and PT shall support the broadcast of Higher Layer capabilities as part of QT MAC broadcast messages (see clause 7.4.4). The broadcast attributes are a small set of NWK layer and DLC layer capabilities (jointly known as "higher layer capabilities") that shall be broadcast regularly as part of the MAC layer broad... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.17.2 Higher layer information in standard FP broadcast (QH= 3) | Table 60 shows the higher layer information attributes in standard FP broadcast. Table 60: Higher layer information attributes in standard FP broadcast (QH = 3) Bit Number Attribute Value Note a36 DECT Standard Authentication (DSAA) required 1 a37 DECT Standard Cipher (DSC) supported 1 a38 Location registration support... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.17.3 Higher layer information in Extended FP broadcast (QH = 4) | Table 61 shows the higher layer information attributes in standard FP broadcast. Table 61: Higher layer information attributes in extended FP broadcast (QH = 4) Bit Number Attribute Value Note a41 Asymmetric bearers supported 1 |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.17.4 Higher layer information in Extended FP broadcast part 2 (QH = 12) | Table 62 shows the higher layer information attributes in extended FP broadcast part 2. ETSI ETSI TS 103 706 V1.1.1 (2022-01) 95 Table 62: Higher layer information attributes in Extended FP broadcast part 2 (QH = 11) Bit Number Attribute Value Note a42 Support of "Re-keying" and "early encryption" 0,1 See clauses 8.45.... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.6.17.5 Higher layer information in Extended FP broadcast part 3 (QH = 14) | Table 63 shows the higher layer information attributes in extended FP broadcast part 3. Table 63: Higher layer information attributes in Extended FP broadcast part 3 (QH = 14) Bit Number Attribute Value Note a36 Support of advanced audio profile microphone 0,1 This bit indicates support of an LC3plus based microphone w... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.7 Application procedures | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.7.1 General | This clause specifies the additional application layer procedures, messages and information elements required the advanced audio profile, which are not described in ETSI EN 300 444 [9] (GAP), or which incorporate modifications to the description given in that specification. NOTE: The main functional application is out ... |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.7.2 Easy pairing procedures | |
a0fad7efdd1a46de4db9258537ad4810 | 103 706 | 7.7.2.1 General | The easy pairing feature simplifies the registration process by not requesting any PIN code from the user when the PIN code is set to the default '0000' value. When this feature is implemented, related procedures shall be valid at first power-on of an unregistered PT and at any additional further registrations. The PT ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.