hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 10.7.3 Procedure | Step
Direction
Message
Comments
1
Start an application in the MS that continually reads all received data
2
SS -> MS
PAGING REQUEST
Contains P-TMSI of the MS. Sent on PCH.
3
MS -> SS
CHANNEL REQUEST
ACCESS TYPE = " Page Response ". Received on RACH.
4
SS -> MS
IMMEDIATE ASSIGNMENT
Random Reference = pertaining to the m... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 10.7.4 Specific message contents | See clause 40. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 10.8 Generic procedure for GPRS uplink data transfer | In the test procedures described in the present document, unless otherwise stated in the test description, the Mobile Originated Data transfer procedure shall be as described in this subclause.
NOTE: In test cases where a fading profile is required, a different and appropriate ARFCN may be selected, for instance if the... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 10.8.1 Initial conditions | System Simulator:
- 1 cell, default parameters as specified in clause 40;
- ideal radio conditions and Timing advance set to 0.
Mobile Station:
- the MS shall be operated under normal test conditions (see annex 1 TC.2.1);
- the special Test-SIM (see annex 4) shall be inserted;
- the MS is GPRS attached with a P-TMSI al... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 10.8.2 Definition of system information messages | See clause 40. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 10.8.3 Procedure | Step
Direction
Message
Comments
1
Start an application in the MS that continually sends data
2
MS -> SS
CHANNEL REQUEST
Received on RACH.
3
SS -> MS
IMMEDIATE ASSIGNMENT
Single block assignment, to order the MS to follow the two phase access procedure. Sent on AGCH.
4
MS -> SS
PACKET RESOURCE REQUEST
Two phase access p... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 10.8.4 Specific message contents | PACKET UPLINK ACK/NACK message:
MESSAGE_TYPE
001001
PAGE_MODE
Normal Paging
UPLINK_TFI
00,
same as the TFI value of the TBF which the message applies
0, message escape
CHANNEL_CODING_COMMAND
Same coding scheme as in the assigned TBF which the message applies to
Ack/Nack Description
- FINAL_ACK_INDICATION
0 (not a fina... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 10.9 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 10.10 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11 General tests | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1 Verification of support and non-support of services (multiple numbering scheme or ISDN) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1.1 Mobile Terminated (MT) calls | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1.1.1 Definition | This test is repeated for all Mobile Terminated Bearer Services / Teleservices according to 3GPP TS 02.02 and 3GPP TS 02.03 except Teleservices 21, 22 and 23. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1.1.2 Conformance requirement | 1. The MS shall check the Information Elements for Bearer Capability in a received SETUP message, and if it agrees to the proposed set, it shall respond with a CALL CONFIRMED message.
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.2.2.2; 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.2.2.3.
2. The MS in the "Null" state, U0,... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1.1.3 Test purpose | 1. To verify that the MS, for the case of the Multinumbering scheme or ISDN, accepts a SETUP message, where the Information Elements for Bearer Capability are compatible with the Bearer Services / Teleservices declared as supported by the MS, by sending a CALL CONFIRMED message.
This is verified for all Mobile Terminat... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1.1.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1.1.4.1 Initial conditions | For an MS with an external interface the interface shall be setup in such a way that the MS is able to successfully receive the call for the service in question. The manufacturer shall state how this is done in a PIXIT statement. The same applies to features which must be activated by MMI before an incoming call can be... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1.1.4.2 Procedure | a) For a Mobile Terminated Bearer Service / Teleservice declared as supported by the MS. The SS transmits a SETUP message.
The SETUP shall contain a single or dual BC-IE where the parameter values are arbitrarily selected among those declared as supported by the MS in PIXIT statements and corresponding to the Bearer Se... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1.1.5 Test requirement | 1) After steps a), b) and c), the MS shall send a CALL CONFIRMED message. The MS may contain a single or dual BC-IE. If present these IEs are not checked.
2) After steps d) and e), the MS shall send a RELEASE COMPLETE message with cause value 88 - incompatible destination. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1.2 Mobile Originated (MO) calls | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1.2.1 Definition | This test is repeated for all Mobile Originated Bearer Services / Teleservices according to 3GPP TS 02.02 and 3GPP TS 02.03 except Teleservices 21, 22 and 23, which are supported by the MS. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1.2.2 Conformance requirement | 1. The MS shall set up a call with a SETUP message containing a single or multiple BC-IE and if required by the service, a single or multiple LLC according to the actual configuration of the MS. Two bearer capabilities can be present only in the cases described in 3GPP TS 07.01.
3GPP TS 04.08 / 3GPP TS 24.008, subclaus... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1.2.3 Test purpose | 1. To verify that the MS generates a SETUP message which includes a single or multiple Bearer Capability and if required by the service, a single or multiple LLC, according to the actual configuration on the MS.
This is verified for all Mobile Originated Bearer Services / Teleservices described in 3GPP TS 07.01 and dec... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1.2.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1.2.4.1 Initial conditions | If possible, the MS shall be configured to initiate an outgoing call with a specified BC and with the corresponding LLC when the ITC value is "unrestricted digital" in the SETUP message. The manufacturer must state how this is done in a PIXIT statement. The same applies to features which must be activated by MMI before... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1.2.4.2 Procedure | a) The MS shall be made to initiate a call.
b) If the MS can be configured to send a specific BC, the test is repeated with the MS configured for all possible preferred Bearer Services and Teleservices declared as supported by the MS. The complete coding of the corresponding BC-IE(s) can be found in subclause 11.8. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.1.2.5 Test requirement | The MS shall send a SETUP message, which shall contain the BC among those declared as supported by the MS. If the MS is configured to send a specific BC, the SETUP message shall contain this particular BC. The BC-IE(s) shall be set according to 3GPP TS 07.01. When an ITC value is set to "unrestricted digital" the MS sh... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.2 Verification of support of the single numbering scheme | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.2.1 Definition | - |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.2.2 Conformance requirement | 1. The MS shall respond to a SETUP message containing no BC-IE with a CALL CONFIRMED message including the single or multiple Bearer Capability, according to the actual configuration of the MS. Two bearer capabilities can be present only in the cases described in 3GPP TS 07.01.
3GPP TS 04.08 / 3GPP TS 24.008, subclause... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.2.3 Test purpose | 1. To verify that the MS, for the case of the Single Numbering Scheme, accepts a SETUP message, where the Information Elements for Bearer Capability and Lower and Higher Layer Compatibility are not present by sending a CALL CONFIRMED message, which includes the single or multiple Bearer Capabilities, according to the a... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.2.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.2.4.1 Initial conditions | The MS is setup to receive a call. If possible, the MS shall be configured to respond to an incoming call with a specified BC selected arbitrarily from those declared as supported by the MS, in the CALL CONFIRMED message, in reply to a SETUP message with no BC, LLC or HLC elements. The manufacturer must state how this ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.2.4.2 Procedure | The SS transmits a SETUP message with no BC, LLC or HLC elements. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.2.5 Test requirement | The MS shall send a CALL CONFIRMED message, which shall contain the BC among those declared as supported by the MS. If the MS is configured to respond with a specific BC, the CALL CONFIRMED message shall contain this particular BC. The BC-IE shall be coded according to 3GPP TS 07.01.
Where two BCs are contained in the ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.3 Verification of non-support of services (Advice of Charge Charging (AoCC)) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.3.1 Definition | Test procedures (a) and (b) apply to MS which support MT calls.
Test procedure (c) applies to MS which support MO calls.
Test procedure (d) applies to MS which support at least one circuit switched basic service. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.3.2 Conformance requirement | 1. An MS claiming to not support AoCC and in the outgoing call / U4 call delivered state, on receipt of a CONNECT message containing AoCC information shall acknowledge the CONNECT message but ignore and not acknowledge the AoCC information sent within the CONNECT.
2. An MS claiming to not support AoCC and in the outgoi... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.3.3 Test purpose | 1. To verify that an MS claiming to not support AoCC and in the outgoing call / U4 call delivered state, on receipt of a CONNECT message containing AoCC information acknowledges the CONNECT message but ignores and does not acknowledge the AoCC information sent within the CONNECT.
2. To verify that an MS claiming to not... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.3.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.3.4.1 Initial conditions | The generic call set up procedures are followed up to and including the reception, or transmission, of the ALERTING message by the MS.
Specific PICS statements:
- Support of at least one MT circuit switched basic service (TSPC_AddInfo_MTsvc)
- Support of at least one MO circuit switched basic service (TSPC_AddInfo_MOsv... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.3.4.2 Procedure | a) For an Mobile Originated call in the U4 state the SS transmits CONNECT containing AoCC information.
b) For an Mobile Originated call in the U4 state the SS transmits FACILITY containing AoCC information.
c) For an Mobile Terminated call in the U9 state the SS transmits a FACILITY containing AoCC information.
d) For ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.3.5 Test requirement | The MS shall ignore the AoCC information sent to it in the Facility information elements as part of the CONNECT/FACILITY messages and not send any AoCC information acknowledgement. It shall be checked for 15 s that the MS does not transmit any AoCC information acknowledgement after the receipt of AoCC information. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.4 Verification of non-support of services (call hold) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.4.1 Definition | - |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.4.2 Conformance requirement | An MS claiming to not support the Call Hold supplementary service and in the U10 call active state shall, when the appropriate Call Hold MMI command is entered:
- Fail to put the first call on hold.
- Fail to place the second call.
- Optionally provide some indication to the user of an error.
3GPP TS 02.83; 3GPP TS 04.... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.4.3 Test purpose | To verify that an MS claiming to not support the Call Hold supplementary service and in the U10 call active state, reacts in the following manner when the appropriate call hold MMI command is entered:
- MS fails to put the first call on hold.
- MS fails to place the second call.
- Optionally provides some indication to... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.4.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.4.4.1 Initial conditions | The mobile originating generic call set up procedures shall be followed up to and including the transmission by the MS of the CONNECT ACKNOWLEDGE to place the call in the U10 call active state. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.4.4.2 Procedure | A second directory number is entered followed by "SEND" via the MMI. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.4.5 Test requirement | The MS shall not send any HOLD messages on the dedicated channel. This is checked for 3 s.
The MS may however send other messages.
The MS may also give the user an indication of the error that has occurred. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.5 Verification of non-support of services (multiparty) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.5.1 Definition | - |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.5.2 Conformance requirement | An MS claiming to not support the MultiParty supplementary service and in the U10 call active state with one call and in the held state with another call shall, when the appropriate MultiParty MMI command is entered:
- Fail to combine the three parties in a MultiParty call.
- Optionally provide some indication to the u... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.5.3 Test purpose | To verify that an MS claiming to not support the MultiParty supplementary service and in the U10 call active state with one call and another call on hold, reacts in the following manner when the appropriate MultiParty MMI command is entered:
- Fails to combine the three parties in a MultiParty call.
- Optionally provid... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.5.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.5.4.1 Initial conditions | The mobile originating generic call set up procedures shall be followed up to and including the transmission by the MS of the CONNECT ACKNOWLEDGE to place the call in the U10 call active state. A second directory number is then entered followed by send to put the first call on hold and place a second call. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.5.4.2 Procedure | "3" followed by "SEND" is entered via the MMI. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.5.5 Test requirement | The MS shall not send a FACILITY message, containing the build multiparty request, on the dedicated channel. This is checked for 3 s.
The MS may however send other messages.
The MS may also give the user an indication of the error that has occurred. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.6 Verification of non-support of feature (Fixed Dialling Number (FDN)) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.6.1 Definition | - |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.6.2 Conformance requirement | 1. An MS claiming to not support FDN that has a SIM with FDN allocated and activated in its SIM Service Table (Service Number 3) and has FDN "enabled" shall refuse a request from the user to attempt an outgoing call.
2. An MS claiming to not support FDN that has a SIM with FDN allocated and activated in its SIM Service... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.6.3 Test purpose | 1. To verify that an MS claiming to not support FDN and that has a SIM with FDN allocated and activated in its SIM Service Table and has FDN "enabled". i.e. AND, IMSI and Location Information Elementary Files are Invalidated inserted, it refuses an attempt to make an outgoing call made by the user.
2. To verify that an... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.6.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.6.4.1 Initial conditions | The ME is powered off. No SIM is inserted in the ME. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.6.4.2 Procedure | a) A SIM with FDN allocated and activated in its SIM Service Table and has FDN "enabled" is inserted in the ME and the MS is powered on.
b) An outgoing CM connection is attempted by the user.
c) The MS paged with its IMSI.
d) The MS is powered off and the SIM is examined using a suitable tool to determine if the IMSI a... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.6.5 Test requirement | 1) in step b), the MS shall not send a CHANNEL REQUEST message.
2) in step c), the MS shall not send a CHANNEL REQUEST message.
3) in step d), the IMSI an Location Information Elementary Files shall be Invalidated. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.7 IMEI Security | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.7.1 Conformance requirements | The IMEI shall not be changed after the ME's final production process. It shall resist tampering, i.e. manipulation and change, by any means (e.g. physical, electrical and software).
NOTE: This requirement is valid for new GSM Phase 2 and Release 96, 97, 98 and 99 MEs type approved after 1st June 2002.
3GPP TS 02.09, 3... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.7.2 Test purpose | To verify the conformance requirement. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.7.3 Method of test | Not available. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.7.4 Declaration | The manufacturer shall declare that:
- he has taken necessary and sufficient steps to ensure that any individual or organisation cannot economically change the IMEI after the ME's final production process; and
- that the IMEI resists tampering, i.e. manipulation and change, by any means (e.g. physical, electrical and s... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8 Coding of the Bearer Capability information element | This subclause describes the coding of the bearer capability IE in a SETUP and in a CALL CONFIRMED message according to 3GPP TS 07.01 and 3GPP TS 04.08 / 3GPP TS 24.008.
More precisely, the matter of subclause 11.8.1 is the coding of the bearer capability IE in a mobile terminating SETUP and subclause 11.8.2 deals with... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1 Network to MS Direction | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.1 BS 21 to 26 - Asynchronous Service | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.1.1 BS 21 | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.1.1.1 3,1 kHz Audio, Transparent | BC GSM = 04 07 AX X8 81 21 X1 4X 81
Octet 1
0
0
0
0
0
1
0
0
Information Element: Bearer Capability
Octet 2
0
0
0
0
0
1
1
1
Length
Octet 3
1
Extension
y
y
Radio Channel Requirement: Spare
0
Coding Standard: GSM
0
Transfer Mode: Circuit
0
1
0
Info. Transfer Cap.: 3,1 kHz Audio
Octet 4
1
Extension
y
Spare
1
1
Structure: U... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.1.1.2 3,1 kHz Audio, Non Transparent | BC GSM = 04 0X X2 XX 81 21 X1 6X A1 (CX)
Octet 1
0
0
0
0
0
1
0
0
Information Element: Bearer Capability
Octet 2
0
0
0
0
x
x
x
x
Length (7 or 8) depending on presence of octet 7.
Octet 3
1
Extension
y
y
Radio Channel Requirement: Spare
0
Coding Standard: GSM
0
Transfer Mode: Circuit
0
1
0
Info. Transfer Cap.: 3,1 kHz Au... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.1.1.3 UDI, Transparent | BC GSM = 04 07 X1 X8 89 21 X1 4X 80
Octet 1
0
0
0
0
0
1
0
0
Information Element: Bearer Capability
Octet 2
0
0
0
0
0
1
1
1
Length
Octet 3
1
Extension
y
y
Radio Channel Requirement: Spare
0
Coding Standard: GSM
0
Transfer Mode: Circuit
0
0
1
Info. Transfer Cap.: UDI
Octet 4
1
Extension
y
Spare
1
1
Structure: Unstructur... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.1.1.4 UDI, Non Transparent | BC GSM = 04 0X X1 XX 89 21 X1 6X A0 (CX)
Octet 1
0
0
0
0
0
1
0
0
Information Element: Bearer Capability
Octet 2
0
0
0
0
x
x
x
x
Length (7 or 8) depending on presence of octet 7.
Octet 3
1
Extension
y
y
Radio Channel Requirement : Spare
0
Coding Standard: GSM
0
Transfer Mode: Circuit
0
0
1
Info. Transfer Cap.: UDI
Octe... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.1.2 BS 22 | Same as BS 21 except:
User Rate in Octet 6a:
-
-
-
-
0
0
1
0
1,2 kbit/s
If different from "none",
Modem Type Octet 6c:
-
-
-
0
0
0
1
0
Modem V.22
In case of 3,1 kHz Audio non transparent service, depending of the type of flow control supported by the TE, octet 7 is present or not. If not present, it means "outband flow... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.1.3 BS 24 | Same as BS 21 except:
User Rate in Octet 6a:
-
-
-
-
0
0
1
1
2,4 kbit/s
If different from "none",
Modem Type Octet 6c:
-
-
-
0
0
0
1
1
Modem V.22bis
In case of 3,1 kHz Audio non transparent service, depending of the type of flow control supported by the TE, octet 7 is present or not. If not present, it means "outband f... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.1.4 BS 25 | Same as BS 21 except:
User Rate in Octet 6a:
-
-
-
-
0
1
0
0
4,8 kbit/s
If different from "none",
Modem Type Octet 6c:
-
-
-
0
0
1
1
0
Modem V.32
In case of 3,1 kHz Audio non transparent service, depending of the type of flow control supported by the TE, octet 7 is present or not. If not present, it means "outband flow... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.1.5 BS 26 | Same as BS 21 except:
NIRR in Octet 4
-
-
-
-
-
-
0
-
no meaning
User Rate in Octet 6a:
-
-
-
-
0
1
0
1
9,6 kbit/s
Interm. Rate in Octet 6b:
-
1
1
-
-
-
-
-
16 kbit/s
If different from "none",
Modem Type Octet 6c:
-
-
-
0
0
1
1
0
Modem V.32
In case of 3,1kHz Audio non transparent service, depending of the type of flow ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.1.6 BS 23 | For MOC only. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.2 BS 31 to 34 - Synchronous Service | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.2.1 BS 32 | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.2.1.1 3,1 kHz Audio, Transparent, non-X.32 case | BC GSM = 04 07 X2 X8 81 20 13 43 83
Octet 1
0
0
0
0
0
1
0
0
Information Element: Bearer Capability
Octet 2
0
0
0
0
0
1
1
1
Length
Octet 3
1
Extension
y
y
Radio Channel Requirement : Spare
0
Coding Standard: GSM
0
Transfer Mode: Circuit
0
1
0
Info. Transfer Cap.: 3,1 kHz Audio
Octet 4
1
Extension
y
Spare
1
1
Structure: ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.2.1.2 UDI, Transparent mode, non-X.32 case | BC GSM = 04 07 X1 X8 8X 20 13 43 80
Octet 1
0
0
0
0
0
1
0
0
Information Element: Bearer Capability
Octet 2
0
0
0
0
0
1
1
1
Length
Octet 3
1
Extension
y
y
Radio Channel Requirement : Spare
0
Coding Standard: GSM
0
Transfer Mode: Circuit
0
0
1
Info. Transfer Cap.: UDI
Octet 4
1
Extension
y
Spare
1
1
Structure: Unstructu... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.2.1.3 3,1 kHz Audio, Transparent mode, X.32 case (Packet Service) | BC GSM = 04 07 X2 X8 86 20 13 43 83
Octet 1
0
0
0
0
0
1
0
0
Information Element: Bearer Capability
Octet 2
0
0
0
0
0
1
1
1
Length
Octet 3
1
Extension
y
y
Radio Channel Requirement : Spare
0
Coding Standard: GSM
0
Transfer Mode: Circuit
0
1
0
Info. Transfer Cap.: 3,1 kHz Audio
Octet 4
1
Extension
y
Spare
1
1
Structure: ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.2.1.4 3,1 kHz Audio, Non Transparent mode, X.32 case (Packet Service) | BC GSM = 04 07 X2 XX 86 20 13 63 A3 C6
Octet 1
0
0
0
0
0
1
0
0
Information Element: Bearer Capability
Octet 2
0
0
0
0
1
0
0
0
Length
Octet 3
1
Extension
y
y
Radio Channel Requirement : Spare
0
Coding Standard: GSM
0
Transfer Mode: Circuit
0
1
0
Info. Transfer Cap.: 3,1 kHz Audio
Octet 4
1
Extension
y
Spare
0
0
Structur... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.2.1.5 UDI, Non Transparent mode, X.32 case (Packet Service) | BC GSM = 04 08 X1 XX 96 20 13 63 A0 C6
Octet 1
0
0
0
0
0
1
0
0
Information Element: Bearer Capability
Octet 2
0
0
0
0
1
0
0
0
Length
Octet 3
1
Extension
y
y
Radio Channel Requirement : Spare
0
Coding Standard: GSM
0
Transfer Mode: Circuit
0
0
1
Info. Transfer Cap.: UDI
Octet 4
1
Extension
y
Spare
0
0
Structure: SDU int... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.2.2 BS 31 | For non X.32 case only, same as BS 32 except:
User Rate in Octet 6a:
-
-
-
-
0
0
1
0
1,2 kbit/s
If different from "none",
Modem Type Octet 6c:
-
-
-
0
0
0
1
0
Modem V.22
BS31 for Packet Service does not exist. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.2.3 BS 33 | Same as BS 32 except:
User Rate in Octet 6a:
-
-
-
-
0
1
0
0
4,8 kbit/s
If different from "none",
Modem Type Octet 6c:
-
-
-
0
0
1
1
0
Modem V.32 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.2.4 BS 34 | Same as BS 32 except:
NIRR in Octet 4
-
-
-
-
-
-
0
-
no meaning
User Rate in Octet 6a:
-
-
-
-
0
1
0
1
9,6 kbit/s
Interm. Rate in Octet 6b:
-
1
1
-
-
-
-
-
16 kbit/s
If different from "none",
Modem Type Octet 6c:
-
-
-
0
0
1
1
0
Modem V.32 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.3 BS 61 - Alternate Speech / Data | The first BC in the Setup message is coded "Speech": 04 01 A0.
The repeat Indicator in the Setup message is coded "Circular for successive selection (alternate)": D1.
The second BC in the Setup message is coded as described below. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.3.1 Speech/Asynchronous Data, Transparent | BC GSM = 04 07 X2 X8 81 21 XX XX 8X
Octet 1
0
0
0
0
0
1
0
0
Information Element: Bearer Capability
Octet 2
0
0
0
0
0
1
1
1
Length
Octet 3
1
Extension
y
y
Radio Channel Requirement : Spare
0
Coding Standard: GSM
0
Transfer Mode: Circuit
0
1
0
Info. Transfer Cap.: 3,1 kHz Audio
Octet 4
1
Extension
y
Spare
1
1
Structure:... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.3.2 Speech/Asynchronous Data, Non Transparent | BC GSM = 04 0X X2 XX 81 21 XX 6X AX (CX)
Octet 1
0
0
0
0
0
1
0
0
Information Element: Bearer Capability
Octet 2
0
0
0
0
x
x
x
x
Length (7 or 8) depending on presence of octet 7.
Octet 3
1
Extension
y
y
Radio Channel Requirement : Spare
0
Coding Standard: GSM
0
Transfer Mode: Circuit
0
1
0
Info. Transfer Cap.: 3,1 kHz A... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.3.3 Speech/Synchronous Data | BC GSM = 04 07 X2 X8 81 20 1X X3 8X
Octet 1
0
0
0
0
0
1
0
0
Information Element: Bearer Capability
Octet 2
0
0
0
0
0
1
1
1
Length
Octet 3
1
Extension
y
y
Radio Channel Requirement : Spare
0
Coding Standard: GSM
0
Transfer Mode: Circuit
0
1
0
Info. Transfer Cap.: 3,1 kHz Audio
Octet 4
1
Extension
y
Spare
1
1
Structure:... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 11.8.1.4 BS 81 - Speech followed by Data | The first BC in the Setup message is coded "Speech": 04 01 A0.
The repeat Indicator in the Setup message is coded “Circular for successive selection "mode 1 alternate mode 2": D1”.
The second BC in the Setup message is coded as described below. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.