ts_127007v110800p

Recommendations

Info

3GPP TS 27.007 version 11.8.0 Release 11 213 ETSI TS 127 007 V11.8.0 (2013-10) Command Possible Response(s) handling priority>,, [...]] +CGEQMIN= +CGEQMIN: ,(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s) [+CGEQMIN: ,(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s),(list of supported s) [...]] Description This command allows the TE to specify a minimum acceptable profile, which is checked by the MT against the negotiated profile returned in the PDP context establishment and PDP contect modification procedures. The set command specifies a profile for the context identified by the (local) context identification parameter, . The specified profile will be stored in the MT and checked against the negotiated profile only at activation or MSinitiated modification of the related context. Since this is the same parameter that is used in the +CGDCONT and +CGDSCONT commands, the +CGEQMIN command is effectively an extension to these commands. The QoS profile consists of a number of parameters, each of which may be set to a separate value. A special form of the set command, +CGEQMIN= causes the minimum acceptable profile for context number to become undefined. In this case no check is made against the negotiated profile. The read command returns the current settings for each defined context. The test command returns values supported as a compound value. If the MT supports several PDP types, the parameter value ranges for each PDP type are returned on a separate line. Defined values ETSI
3GPP TS 27.007 version 11.8.0 Release 11 214 ETSI TS 127 007 V11.8.0 (2013-10) : integer type; specifies a particular PDP context definition (see +CGDCONT and +CGDSCONT commands). : string type; specifies the type of packet data protocol (see the +CGDCONT command). For the following parameters, see also 3GPP TS 23.107 [46]. : integer type; indicates the type of application for which the UMTS bearer service is optimised (refer 3GPP TS 24.008 [8] subclause 10.5.6.5). 0 conversational 1 streaming 2 interactive 3 background : integer type; indicates the maximum number of kbits/s delivered to UMTS (up-link traffic) at a SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQMIN=…,32, …) (refer 3GPP TS 24.008 [8] subclause 10.5.6.5). : integer type; indicates the maximum number of kbits/s delivered by UMTS (downlink traffic) at a SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQMIN=…,32, …) (refer 3GPP TS 24.008 [8] subclause 10.5.6.5). : integer type; indicates the guaranteed number of kbits/s delivered to UMTS (uplink traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQMIN=…,32, …) (refer 3GPP TS 24.008 [8] subclause 10.5.6.5). : integer type; indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQMIN=…,32, …) (refer 3GPP TS 24.008 [8] subclause 10.5.6.5). : integer type; indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not (refer 3GPP TS 24.008 [8] subclause 10.5.6.5). 0 no 1 yes : integer type; (1,2,3,…) indicates the maximum allowed SDU size in octets (refer 3GPP TS 24.008 [8] subclause 10.5.6.5). : string type; indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU error ratio is defined only for conforming traffic. The value is specified as "mEe". As an example a target SDU error ratio of 5•10 -3 would be specified as "5E3" (e.g. AT+CGEQMIN=…,"5E3",…) (refer 3GPP TS 24.008 [8] subclause 10.5.6.5). : string type; indicates the target value for the undetected bit error ratio in the delivered SDUs. If no error detection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. The value is specified as "mEe". As an example a target residual bit error ratio of 5•10 -3 would be specified as "5E3" (e.g. AT+CGEQMIN=…,"5E3",…) (refer 3GPP TS 24.008 [8] subclause 10.5.6.5). : integer type; indicates whether SDUs detected as erroneous shall be delivered or not (refer 3GPP TS 24.008 [8] subclause 10.5.6.5). 0 no 1 yes 2 no detect ETSI
Page 1 and 2:
ETSI TS 127 007 V11.8.0 (2013-10) T
Page 3 and 4:
3GPP TS 27.007 version 11.8.0 Relea
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164: 3GPP TS 27.007 version 11.8.0 Relea
Page 213: 3GPP TS 27.007 version 11.8.0 Relea
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
show all

ts_127007v110800p

Create successful ePaper yourself

Delete template?

Save as template?