1、= 3404583 0080075 886 Released: July I, 1993 GSM 04.83 Version: 4.4.0 Date: 2 April 1993 Work Item No: Key words: European digital cellular telecommunication system (phase 2); Mobile radio interface layer 3 Call completion supplementary services Specification ETSI European Telecommunications Standar
2、ds Institute ETSI Secretariat: Route des Lucioles, F-O6921 Sophia Antipolis Cedex . France TP. + 33 92 94 42 O0 TF. + 33 93 65 47 16 Tx. 47 O0 40 F *his is an unpublished work the copyright in which vests in the European Telecommunications Standards Institute. All rights reserved. The information co
3、ntained herein is the property of ETSI and no part may be reproduced or used except as authorised by contract or other written permission. The copyright and the foregoing restriction on reproduction and use extend to all media in which the information may be embodied. 3404583 0080076 712 = Page 3 GS
4、M 04.83 . version 4.4.0 : April 1993 CONTENTS O . GENERAL 5 1 . CALL WAITING (CW) 6 1 . 1 Waiting call indication and confirmation . 6 1 . 2 Normal operation with successful outcome . 7 1.2.1 Waiting call accepted; existing call released 7 1.2.2 Waiting call accepted; existing call on hold . 7 1.2.3
5、 Existing call released by user A; waiting call accepted 8 1.3 Normal operation with unsuccessful outcome . 9 1.3.1 Waiting call released by subscriber B . 9 1.3.2 Waiting call released by calling user C 9 1 . 3.3 Waiting call times out 9 1 . 3.4 No reply condition timer expires 9 1 . 4 Activation .
6、 10 1 . 5 Deactivation 11 1 . 6 Interrogation 12 1.7 Invocation . 12 1.8 Registration and erasure 12 2 . CALL HOLD (HOLD) 13 2.1 Normal operation 13 2.1 . 1 Hold and retrieve functions 13 2.1.2 Hold invocation 14 2.1.3 Retrieve procedure 15 2.1.4 Alternate from one call to the other . 16 2.1.5 Auxil
7、iary states for hold and retrieve 17 2.1.6 An example of dimensioned state space . 17 2.2 Activation and deactivation 17 2.3 Registration. erasure and interrogation 17 Previous page is blank 3404583 0080077 659 Page 5 GSM 04.83 - version 4.4.0 : April 1993 SECTION O O. GENERAL This technical specifi
8、cation specifies the procedures used at the radio interface (Reference point Um as defined in technical specification GSM 04.02) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of call completion supplementary services. Provision and withdrawal of
9、Supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface. In technical specification GSM 04.1 O the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
10、 Technical specification GSM 04.80 specifies the formats and coding for the supplementary services. Definitions and descriptions of supplementary services are given in technical specifications GSM 02.04 and GSM 02.8-series. Technical specification GSM 02.83 is related specially to call completion su
11、pplementary services. Technical realization of supplementary services is described in technical specifications GSM 03.1 1 and GSM 03.8-series. Technical specification GSM 03.83 is related specially to call completion supplementary services. The procedures for Call Control, Mobility Management and Ra
12、dio Resource management at the layer 3 radio interface are defined in technical specifications GSM 04.07 and GSM 04.08. The following supplementary services belong to the call completion supplementary services and are described in this technical specification: - Call waiting (CW) (section 1); - Call
13、 hold (HOLD) (section 2). Previous page is blank 3409583 0080078 595 Page 6 GSM W.83 - version 4.4.0 : April 1993 SECTION 1 1. CALL WAITING (CW) 1.1 Waiting call indication and confirmation When this service is activated for the controlling subscriber B and the B-subscriber has calls only in states
14、U10 (Active) or U26 (MO Modify) as defined in TS GSM 04.08, the arrival of an incoming call from subscriber C shall, if no other call is waiting be signalled to the mobile station B by a normal call indication. In that case the network and the mobile station shall act in accordance with TS GSM 04.08
15、. The transaction identifier shall be the transaction identifier (C-Bi allocated to the waiting call and must not be the same as the transaction identifier (A-BI for the already existing call (see figure 1.1 1. In the CALL CONFIRMED message sent to the network the Cause information element shall be
16、included with cause #17 “user busy“ (see figure 1.1 I. When the ALERTING message is received by the network the call waiting timer T2 shall be started or if call forwarding on no reply is activated for the existing call released If the mobile user E before expiry of timer T2 determines to accept the
17、 waiting call and release the existing call the mobile station shall release the existing call firstly and accept the waiting call secondly. For the release of the existing call the mobile station and the network shall act in accordance with TS GSM 04.08. The transaction identifier shall be the tran
18、saction identifier (A-BI of the already existing call. The Cause information element in the first clearing message shall indicate cause #16 “normal clearing“. For the acceptance of the waiting call the mobile station and the network shall act in accordance with TS GSM 04.08. The transaction identifi
19、er shall be the transaction identifier (C-BI of the waiting call. When the network receives the CONNECT message the timer T2 or if applicable the timer T3 shall be stopped. 1.2.2 Waiting cdl accepted; existing call on hold If the mobile user B before expiry of timer T2 or if applicable timer T3 dete
20、rmines to accept the waiting call and put the existing call on hold the mobile station shall put the existing call on hold firstly and accept the waiting call secondly. In case there is one active call (A-BI and another call (D-BI on hold and call (C-6) waiting, and the mobile user B wants to accept
21、 the waiting call (C-8) and put the active call (A-B) on hold, the held call (D-BI has to be released first, either by user B or user D, in accordance with TS GSM 04.08. To put the existing call on hold the mobile station and the network shall act in accordance with section 2. The hold function shal
22、l be initiated by the mobile station and the transaction identifier shall be the transaction identifier (A-B) of the existing call (see figure 1.3). For the acceptance of the waiting call the mobile station and the network shall act in accordance with TS GSM 04.08. The transaction identifier shall b
23、e the transaction identifier (C-6) of the waiting call (see figure 1.3). Page 8 GSM 04.83 - version 4.4.0 : April 1993 When the network receives the CONNECT message the timer T2 or if applicable the timer T3 shall be stopped. HOLD ACKNOWLEDGE . . . Transaction identifieriA-BI . . . HOLD REJECT Note:
24、 If the BasicServiceCode is not included the activation is valid for all applicable basic services. Figure 1.4/GSM 04.83 Activation of call waiting 3404583 0080083 952 Page 11 GSM 04.83 - version 4.4.0 : April 1993 1.5 Deactivation Deactivation of the supplementary service call waiting will be perfo
25、rmed by the subscriber. The network will send a return result indication of acceptance of the request (see figure 1.5). If the network cannot accept a deactivation request, an error indication is returned to the served mobile subscriber. Error values are specified in TS GSM 04.80 (see figure 1.5). I
26、f the subscriber does not indicate a specific basic service group the deactivation of call waiting is valid for all applicable basic services (see figure 1.5). MS Network REG ISTER Facility (Invoke = DeactivateSS (CW, BasicServiceCode) RELEASE COMPLETE/FACILITY - Facility (Return result = Deactivate
27、SS (BasicServiceCode) RELEASE COMPLETE - Facility (Return error (Error) RELEASE COMPLETE - Facility (Reject (Invoke-problem) Note: If the BasicServiceCode is not included the deactivation is valid for all applicable basic services. Figure 1.5JGSM 04.83 Deactivation of call waiting m 3404583 0080084
28、899 m Page 12 GSM 04.83 - version 4.4.0 : April 1993 1.6 Interrogation Status check The mobile subscriber can request the status of the supplementary service call waiting and be informed whether the service is supported in the network and if so, a list of all basic service groups to which the call w
29、aiting supplementary service is active (see figure 1.61. If a mobile subscriber interrogates the network on the status of call waiting, and the network supports call waiting but the service is not active for any basic service groups then an SS-Status parameter shall be returned indicating “deactivat
30、ed“ (see figure 1.6). If a mobile subscriber interrogates the network on the status of call waiting, whilst the network does not support call waiting, the network shall return an error indication (see figure 1.61. RELEASE COMPLETE/FACILITY - Facility (Return result = InterrogateSS (BasicServiceCode(
31、s) ar RELEASE COMPLETE -.- Facility (Return error (Error) RELEASE COMPLETE - Facility (Reject (Invoke-problem) Figure 1.6/GSM 04.83 Interrogation of call waiting 1.7 Invocation Invocation of call waiting causes no signalling on the radio path. 1.8 Registration and erasure Registration and erasure of
32、 the supplementary service call waiting are not applicable. 3404583 008008.5 725 Pago 13 GSM 04.83 - version 4.4.0 : April 1993 SECTION 2 2. CALL HOLD (HOLD) 2.1 Normal operation 2.1.1 Hold and retrieve functions The hold and retrieve functions are performed on the same MM-connection. The hold funct
33、ion is used to put an existing call which is in the active phase in the Call held auxiliary state. By default, it retains the MM-connection in use and the transaction identifier of the held call for possible subsequent call retrieval. On receipt of a HOLD message the network shall return a HOLD ACKN
34、OWLEDGE message, provided that the requested function can be performed. The network disconnects any user information path allocated to the active call when putting that call in the Call held auxiliary state. The mobile station disconnects any user information path to the active call and retains the
35、transaction identifier and the MM-connection when putting that call in the Call held auxiliary state. The HOLD ACKNOWLEDGE message puts the call in the Call held auxiliary state and indicates that the hold function has been performed. The HOLD REJECT message indicates that the hold request was denie
36、d and returns the call to the condition it was in prior to the hold request. The HOLD REJECT message contains the Cause information element with e.g.: - cause #29 “Facility rejected“; - - cause #50 “Requested facility not subscribed“; cause #69 “Requested facility not implemented“. The retrieve func
37、tion reconnects the mobile station to the requested user information path. The RETRIEVE message requests that a call be retrieved. The RETRIEVE ACKNOWLEDGE message indicates that the retrieve function has been performed. The RETRIEVE REJECT message indicates that the retrieve request was denied. The
38、 RETRIEVE REJECT message contains the Cause information element with e.g.: - cause #34 “No channel available“. 3404583 0080086 bbL Page 14 GSM 04.83 - version 4.4.0 : April 1993 2.1.2 Hold invocation The served mobile subscriber indicates to the network that communication on the interface is to be i
39、nterrupted. The hold function should be invoked in association with an existing active call. The invocation of the hold function does not affect the existing TS GSM 04.08 call states, but does affect the auxiliary state. The request for placing a call on hold places the auxiliary state in the hold r
40、equest state. The responding entity will acknowledge this request with a HOLD ACKNOWLEDGE message if this operation was successful (see figure 2.1 I. This will result in the auxiliary state being put in the Call held state. If the requested hold function cannot be obtained, then a HOLD REJECT messag
41、e will be returned with the appropriate cause (see figure 2.1). This will result in the auxiliary state returning to the Idle state. The traffic channel is now available to originate another call or to accept a waiting call (see call waiting). If at any time a call is in the held state, either party
42、 may clear the call according to the normal release procedure. Before to originate another call the MS will request the establishment of an MM-connection first, see TS GSM 04.08. MS Network HOLD Figure 2.1 IGSM 04.83 Invocation of call hold If the network received a non-zero SS Screening indicator f
43、rom the remote partys mobile station the network shall send a notification to the remote party indicating that the call has been placed on hold (see figure 2.2). If the network did not receive a non-zero SS Screening indicator from the remote partys mobile station it shall not send a notification. M
44、S Network FACILITY - Facility (Invoke = NotifySS (HOLD, CallOnHold-Indicator) Figure 2.2lGSM 04.83 Notification to the held mobile party that the existing call being put on hold If the served mobile subscriber clears the current call and another call is still on hold, the normal call clearing proced
45、ure is used. = 3404583 0080087 5T8 = Page 15 GSM 04.83 - version 4.4.0 : April 1993 2.1.3 Retrieve procedure When the mobile subscriber that invoked the call hold service indicates that the call is to be retrieved, the network shall re-establish communication and send an acknowledgement to the serve
46、d mobile subscriber (see figure 2.3). If the network received a non-zero SS Screening indicator from the remote paws mobile station the network shall send a notification to the remote party indicating that the call has been retrieved (see figure 2.4). If the network did not receive a non-zero SS Scr
47、eening indicator from the remote partys mobile station it shall not send a notification. The retrieve function is requested by sending a RETRIEVE message. This message may be sent while the auxiliary state is in the Call held state. Upon the sending of the RETRIEVE message the auxiliary state of the
48、 initiators terminal would be the retrieve request state. If the retrieve request is successful, the RETRIEVE ACKNOWLEDGE message will be returned. The initiator should not assume that call retrieval has occurred until it receives this message. The auxiliary state would then return to the Idle state. If the retrieve request is not successful, the RETRIEVE
