02.343GPPHigh Speed Circuit Switched Data (HSCSD)Stage 1TS
HSCSD is a feature that allows users subscribing to the General Bearer Services to access user rates that can be achieved with one or more TCH/F. HSCSD also defines mechanisms for the use of air interface resources which makes efficient and flexible use of higher user rates feasible.
HSCSD shall provide flexible ways of supporting GSM Phase 2, T and NT data services and new data services at the higher rates possible with one or more TCH/F. Data compression shall be applicable to NT HSCSD. Supplementary Services that are applicable to the General Bearer Services can be used with the HSCSD feature (Reference GSM 02.04, ).
4.3 General Bearer Services
The General Bearer Services are defined in GSM 02.02 .
The General Bearer Services consist of four Bearer Services, and they are as follows:
– dedicated PAD access;
– dedicated packet access.
4.4 Parameters to be indicated and negotiated
4.4.1 Call set-up
The parameters to be indicated, and negotiated, if applicable, during the call set-up shall include:
– Channel coding(s) acceptable (for the call);
– Maximum number of TCH/F (that the mobile user can accept);
– Wanted AIUR (desired rate that the mobile user wants the network to allocate). The wanted AIUR is applicable to NT services only;
– Indication if the user initiated modification is required, and if so, the network resource needs.
The channel coding(s) acceptable shall be indicated by the mobile at call set-up and is not negotiable. It indicates the channel coding(s) that may be chosen by the network for the call.
The maximum number of TCH/F shall be indicated at call set-up. It enables the mobile user to limit the number of TCH/F used and thus to control an essential parameter for charging. It sets the upper limit of number of TCH/F that the network may allocate to the mobile.
The wanted AIUR (applicable to NT services only) indicates the AIUR that the mobile user wants and which the network shall try to reach but which it is not allowed to exceed. The exception where the network is allowed to exceed the wanted AIUR is when the network can achieve the AIUR with a lower number of TCH/F, e.g. wanted AIUR indicated by the mobile is 14,4 kbit/s, channel codings acceptable are both TCH/F9.6 and TCH/F4.8 and maximum number of TCH/F are 3, then the network shall choose 2 x 9,6 over 3 x 4,8 if a channel coding of TCH/F9.6 is available on two TCH/F.
If the user wishes to make use of the user initiated modification procedure, this shall be indicated at the call set-up.
It shall be possible to reserve a FNUR that is considerably higher than the AIUR.
126.96.36.199 T services
The ME or the network may propose to modify the FNUR. The calling entity may accept or release the call. Autobauding is not allowed.
The AIUR is always equal to the FNUR.
Fax Group 3 can make use of HSCSD.
The channel coding selected must be one of the channel coding(s) indicated in the channel coding(s) acceptable parameter, the number of TCH/F selected shall not exceed the maximum number of TCH/F parameter, and the combination of the two shall result in an AIUR that is equal to the FNUR.
188.8.131.52 NT services
The ME or the network may propose to modify the FNUR. The calling entity may accept or release the call. Autobauding is allowed.
The wanted AIUR is indicated by the mobile at call set-up.
4.4.2 Network initiated modification
184.108.40.206 T services
For transparent calls the radio resource parameters must remain within limits that allow the transparent call to maintain it is characteristics of fixed end to end throughput and delay. This means that the channel coding and the number of TCH/F used may change during the call as long as a channel coding indicated in the channel coding(s) acceptable parameter is used, the maximum number of TCH/F is not exceeded and the AIUR is kept constant.
220.127.116.11 NT services
For NT calls the network may modify the number of TCH/F and the channel coding used and thus also the AIUR during the call as long as the maximum number of TCH/F, and the channel coding(s) acceptable are all respected. The network shall try to reach the wanted AIUR indicated, as long as the resource situation allows it.
4.4.3 User initiated modification
The in-call modification feature shall be supported in case of alternate services.
18.104.22.168 T services
The user initiated modification is not applicable to T services.
22.214.171.124 NT services
The user may indicate a change of the parameters maximum number of TCH/F and wanted AIUR only.
The user initiated modification is only applicable to the data phase of alternate services.
4.5 Air Interface Resource Allocation
4.5.1 Minimum Air Interface Resource Allocation and Allocation Increment
Air interface resources shall be allocated to HSCSD calls at TCH/F increments. The minimum air interface resource allocation for HSCSD calls shall be one TCH/F.
4.5.2 Flexible Air Interface Resource Allocation
Flexible air interface resource allocation enables:
The network to allocate dynamically resources related to the air interface usage according to the network operator’s strategy, within the limits negotiated at the call set-up or during a user initiated modification.
4.6 Symmetric and asymmetric connections
4.6.1 Symmetric connections
For symmetric connections, air interface resources are allocated symmetrically.
4.6.2 Asymmetric connections
The provision of the asymmetric air interface connections allows simple ME (of Type 1, Reference GSM 05.02, ) to receive at higher AIUR than otherwise would be possible with a symmetric connection.
Asymmetric air interface connections that are a subset of the symmetric HSCSD, and support different user rates at uplink and downlink, shall be provided.
Asymmetric air interface connections are only applicable to the downlink-biased asymmetry, i.e., where the ME is receiving at a higher rate than it is transmitting.
Asymmetric air interface connections shall only be applicable to NT HSCSD.
4.6.3 Network choice of connection symmetry
When the network has a choice of allocating either a symmetric or an asymmetric air interface connection it shall proceed as follows:
– In the case where the wanted AIUR is smaller than or equal to the AIUR supported symmetrically by the ME, or asymmetric air interface connection is not supported by the network, then a symmetric air interface connection is established.
– In the case where the wanted AIUR exceeds the AIUR supported symmetrically by the ME, the network shall assign the maximum AIUR supported by the ME in the down-link, upper-bounded by the maximum number of TCH/F indicated by the mobile user, and the number of TCH/F supported by the network, maintaining the minimum of one TCH/F.
4.7 Mobile Station/Mobile Equipment requirements
The general MS capabilities is applicable to HSCSD (Reference GSM 02.60 ).
A ME that supports HSCSD shall support one or more of the channel types TCH/F at or above 4,8 kbit/s.
Given that the ME supports a certain channel coding, the network shall be able to assume that the ME can support this channel coding in any multislot configuration allowed by its multislot class (Reference GSM 05.02, ).
4.8 Mobility Management
HSCSD shall be provided for within the existing supported Mobility Management.
Roaming shall be possible.
4.10 Quality of Service
4.10.1 Bit error rate
126.96.36.199 TCH/F Bit Error Rate
The bit error rate performance of each TCH/F of a multiple TCH/F HSCSD call shall be the same as that of a single TCH/F data call for the same channel coding.
188.8.131.52 Overall HSCSD Bit Error Rate
Any increase in the bit error rate caused by the splitting and combining of multiple TCH/F shall be kept to a minimum.
4.10.2 Radio resource management
HSCSD shall be provided for within the existing Radio Resource management control functions, including the relevant handover types. The handover shall be simultaneous for all air interface timeslots making up an HSCSD call.
HSCSD shall be provided with full mobility.
4.10.3 Call set-up delay
Any increase in call set-up delay of the HSCSD calls compared to Phase 2 data services shall be kept to a minimum.
4.10.4 End-to-end delay
Any increase in end-to-end delay of the HSCSD calls compared to Phase 2 data services shall be kept to a minimum.
The throughput for HSCSD T calls shall remain constant for the duration of the call except for the interruption of transmission at handover.
4.10.6 Network planning and interference levels
The impact of HSCSD on network planning and interference levels shall be kept to a minimum.
4.11 Mapping of FNUR to TCH/F for T services
For some FNUR padding is required to adapt the maximum possible AIUR to the FNUR.
4.12 Mapping of AIUR to TCH/F for NT services
The following table indicates the mapping of AIUR to the number of TCH/F for NT services.
Table 1/GSM 02.34: Mapping of AIUR to TCH/F for NT services
N/A Not applicable.
4.13 HSCSD MMI aspects
It shall be possible to configure the parameters negotiated and indicated at HSCSD call set-up and during user initiated modification.
4.14 HSCSD Subscription aspects
HSCSD is not subscribed to. Users wanting to use HSCSD must subscribe to the General Bearer Services.
4.15 HSCSD charging aspects
To allow accurate charging of HSCSD calls, a record of start and stop timestamps versus the number of TCH/F, for each change in TCH/F allocation, shall be provided.
NOTE: For MO HSCSD calls, the A party is liable for the use of all the TCH/F in her PLMN.
For MT HSCSD calls, the B party may have to pay for one or more of the TCH/F in her PLMN.
In case the originating or terminating subscriber is a fixed network subscriber, there should be no additional charge (in respect of the changing allocation of TCH/F) for the originating or terminating fixed network subscriber.
4.16 O and M aspects
For HSCSD call, there are several new and modified parameters compared to GSM Phase 2 data calls.
For HSCSD, the air interface resource allocation may change several times during the call (network initiated and user initiated changes). It shall be possible to limit the frequency of changes per call, separately for network initiated and user initiated changes.
HSCSD calls can occupy multiple TCH/F. It shall dynamically be possible to limit the maximum number of TCH/F allowed for HSCSD calls per cell.
4.17 HSCSD security aspects
Authentication and ciphering are applicable to HSCSD calls with no or minimal reduction in the security of the air interface.