hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
1.2 Registration
|
........................................................................................................................................................ 8
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
1.3 Activation
|
.......................................................................................................................................................... 9
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
1.4 Deactivation
|
..................................................................................................................................................... 10
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
1.5 Interrogation
|
.................................................................................................................................................... 11
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
1.6 Invocation and erasure
|
..................................................................................................................................... 11
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
1.7 Cross phase compatibility
|
................................................................................................................................ 11
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
1.7.1 Network only supports GSM Phase 1 control of SS by the subscriber
|
...................................................... 11
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
1.7.2 MS only supports protocol version 1 control of SS by the subscriber
|
....................................................... 11
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
2 Barring of incoming calls
|
......................................................................................................................12
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
2.1 Normal operation
|
............................................................................................................................................. 12
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
2.2 Registration
|
...................................................................................................................................................... 12
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
2.3 Activation
|
........................................................................................................................................................ 13
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
2.4 Deactivation
|
..................................................................................................................................................... 14
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
2.5 Interrogation
|
.................................................................................................................................................... 15
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
2.6 Invocation and erasure
|
..................................................................................................................................... 15
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
2.7 Cross phase compatibility
|
................................................................................................................................ 15
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
2.7.1 Network only supports GSM Phase 1 control of SS by the subscriber
|
...................................................... 15
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
2.7.2 MS only supports protocol version 1 control of SS by the subscriber
|
....................................................... 15 Annex A: Change history......................................................................................................................16 History..............................................................................................................................................................17 ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 4 3G TS 24.088 version 3.0.0 Foreword This Technical Specification has been produced by the 3GPP. This TS specifies the procedures used at the radio interface for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of call barring supplementary services within the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 5 3G TS 24.088 version 3.0.0 Introduction The present document includes references to features which are not part of the Phase 2+ Release 96 of the GSM Technical specifications. All subclauses which were changed as a result of these features contain a marker (see table below) relevant to the particular feature. GSM 10.01 defines the correspondence between these features and GSM yearly releases. The following table lists all features that were introduced after Release 96. Feature Designator CAMEL Phase 2 $(CAMEL2)$ ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 6 3G TS 24.088 version 3.0.0
|
c0dd1f49bffdd1daa285ed67ebae4b56
|
124 088
|
0 Scope
|
This Technical Specification (TS) specifies the procedures used at the radio interface (reference point Um as defined in GSM 04.02) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of call barring supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface. In GSM 04.10 the general aspects of the specification of supplementary services at the layer 3 radio interface are given. GSM 04.80 specifies the formats and coding for the supplementary services. Definitions and descriptions of supplementary services are given in GSM 02.04, GSM 02.8x and GSM 02.9x-series. Technical realization of supplementary services is described in GSM 03.11, GSM 03.8x and GSM 03.9x-series. The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in GSM 04.07 and GSM 04.08. The following supplementary services belong to the call restriction supplementary services and are described in this specification: - Barring of outgoing calls (clause 1): - Barring of all outgoing calls (BAOC) (Barring program 1); - Barring of outgoing international calls (BOIC) (Barring program 2); - Barring of outgoing international calls EXCEPT those directed to the home PLMN country (BOIC-exHC) (Barring program 3). - Barring of incoming calls (clause 2): - Barring of all incoming calls (BAIC) (Barring program 1); - Barring of incoming calls when roaming outside the home PLMN country (BIC-Roam) (Barring program 2). 0.1 Normative references References may be made to: a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in which case, subsequent revisions to the referenced document do not apply; or b) all versions up to and including the identified version (identified by "up to and including" before the version identity); or c) all versions subsequent to and including the identified version (identified by "onwards" following the version identity); or d) publications without mention of a specific version, in which case the latest version applies. A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [3] GSM 03.11: "Digital cellular telecommunications system (Phase 2+); Technical realization of supplementary services". [4] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 7 3G TS 24.088 version 3.0.0 [5] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". [6] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [7] GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3; Supplementary services specification; General aspects". [8] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". 0.2 Abbreviations Abbreviations used in this specification are listed in GSM 01.04. 0.3 Cross phase compatibility For the following supplementary services, a number of changes exist between this specification and the protocol version 1 specification: - Barring of outgoing calls; - Barring of incoming calls. The main body of this specification assumes that all network entities comply with this version of the service. In each case an additional subclauses 1.7 and 2.7 defines the additional requirements for when one or more network entities or the MS complies with the protocol version 1 specifications for the supplementary service procedures. ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 8 3G TS 24.088 version 3.0.0 1 Barring of outgoing calls 1.1 Normal operation When a barring program relating to outgoing calls is active and operative for a basic service, each call set up related to that basic service and not allowed by the barring program will be refused by the network. In this case a NotifySS operation containing the SS-Status indicating that a barring program relating to outgoing calls is currently active and operative will be sent to the served mobile subscriber in a clearing message (see figure 1.1). MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> DISCONNECT/RELEASE/RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (SS-Code, SS-Status)) NOTE 1: The SS-Code will be the common code for outgoing barring services. NOTE 2: $(CAMEL2)$ The DISCONNECT and RELEASE messages were introduced because of CAMEL Phase 2. Figure 1.1: Notification to the served mobile subscriber that barring of outgoing calls is active When a barring program is active (operative or quiescent), the ability of the served mobile subscriber to set up emergency calls is not affected, irrespective of the basic service to which the barring program applies. When a barring program relating to outgoing calls is active (operative or quiescent), the ability of the served mobile subscriber to receive calls is not affected. 1.2 Registration If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by subscriber using password", the subscriber has to register a call barring password at provision time. Furthermore the served mobile subscriber can change the call barring password by a registration procedure at any time. If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by service provider", an attempt to register a new call barring password will be denied. The procedure to register a new password is specified in GSM 04.10. ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 9 3G TS 24.088 version 3.0.0 1.3 Activation If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by subscriber using password", the supplementary service is activated for a basic service if the subscriber has requested so by means of an activation procedure for that basic service. If the subscriber does not indicate a specific basic service, the activation applies to all basic services. The subscriber may use the call barring password at activation (see figure 1.2). If the activation is successful, the service will be activated. The network will then send a return result indicating acceptance of the request. The result is formatted according to the options shown below: - The result includes the Basic Service group Code(s) to which the service is activated. The result may also contain an SS-Code and SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then these parameters shall be presented in the result. If the MS does send an SS Version Indicator in the invocation request then these parameters are optional in the result. If the SS-Status is included the network shall set it to reflect the state of the service. If the SS-Code is included then it shall contain the SS-Code of the service which has been activated. The MS shall ignore the contents of the SS-Code and SS-Status parameters if they are received. Note that the use of SS-Code and SS-Status is to provide backwards compatibility with GSM Phase 1. - If the request did not include a BasicServiceCode, and the activation was successful for all basic services, the network may send an empty return result to the MS. This option applies whether or not an SS Version Indicator is received from the MS. If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by service provider", an attempt to activate the service will be denied and the served mobile subscriber receives an error indication (see figure 1.3). Error values are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = ActivateSS (SS-Code, BasicServiceCode)) Password procedure according to GSM 04.10 RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = ActivateSS (SS-Code, BasicServiceCode, SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code will be one of the specific outgoing barring codes. If BasicServiceCode is not included it applies to all basic services. The SS-Code and SS-Status may not be included in the result in all cases (see text). Figure 1.2: Activation of a barring program ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 10 3G TS 24.088 version 3.0.0 1.4 Deactivation If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by subscriber using password", the supplementary service is deactivated for a basic service if the subscriber has requested deactivation by means of a deactivation procedure for that basic service. The subscriber may use the call barring password at deactivation (see figure 1.3). The deactivation request of a barring program may specify the basic service. If the subscriber does not indicate a specific basic service, the deactivation applies to all basic services (see figure 1.3). If the deactivation is successful, the service will be deactivated. The network will then send a return result indicating acceptance of the request. The result is formatted according to the options shown below: - The result includes the Basic Service group Code(s) to which the service is deactivated. The result may also contain an SS-Code and SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then these parameters shall be presented in the result. If the MS does send an SS Version Indicator in the invocation request then these parameters are optional in the result. If the SS-Status is included the network shall set it to reflect the state of the service. If the SS-Code is included then it shall contain the SS-Code of the service which has been deactivated. The MS shall ignore the contents of the SS-Code and SS-Status parameters if they are received. Note that the use of SS-Code and SS-Status is to provide backwards compatibility with GSM Phase 1. - If the request did not include a BasicServiceCode, and the deactivation was successful for all basic services, the network may send an empty return result to the MS. This option applies whether or not an SS Version Indicator is received from the MS. If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by service provider", an attempt to deactivate the supplementary service will be denied and the served mobile subscriber receives an error indication (see figure 1.3). Error values are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = DeactivateSS (SS-Code, BasicServiceCode)) Password procedure according to GSM 04.10 RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = DeactivateSS (SS-Code, BasicServiceCode, SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may be one of the specific outgoing barring codes, the common code for the outgoing barring services, or the SS-Code for all call barring services. If BasicServiceCode is not included it applies to all basic services. The SS-Code and SS-Status may not be included in the result in all cases (see text). Figure 1.3: Deactivation of barring of outgoing calls ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 11 3G TS 24.088 version 3.0.0 1.5 Interrogation The interrogation procedure enables the mobile subscriber to obtain information about data stored in the PLMN. After having requested this procedure the network shall return a list of all basic service groups for which the service is active (see figure 1.4). If there is no basic service group for which the service is active, an SS-Status will be returned indicating that the service is "deactivated". MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (SS-Code)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode)) or RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may be one of the specific outgoing barring codes. Figure 1.4: Interrogation of a barring program 1.6 Invocation and erasure Invocation and erasure are not applicable to barring programs. 1.7 Cross phase compatibility 1.7.1 Network only supports GSM Phase 1 control of SS by the subscriber In this case there is no relevant cross phase compatibility problem. 1.7.2 MS only supports protocol version 1 control of SS by the subscriber In this case there is no relevant cross phase compatibility problem. ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 12 3G TS 24.088 version 3.0.0 2 Barring of incoming calls 2.1 Normal operation When a barring program relating to incoming calls is active and operative for a basic service, each incoming call set-up related to that basic service and not allowed by the barring program will be refused by the network. In this case a NotifySS operation containing the SS-Status indicating that a barring program relating to incoming calls is currently active and operative will be sent to the calling mobile subscriber in a clearing message (see figure 2.1). MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> DISCONNECT/RELEASE/RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (SS-Code, SS-Status)) NOTE: The SS-Code will be the common code for incoming barring services. Figure 2.1: Notification to the calling mobile subscriber that at the called subscriber side barring is active When barring of incoming calls is active (operative or quiescent), the ability of the served mobile subscriber to originate calls is not affected. 2.2 Registration If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by subscriber using password", the subscriber has to register a call barring password at provision time. Furthermore the served mobile subscriber can change the call barring password by a registration procedure at any time. If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by service provider", an attempt to register a new call barring password will be denied. The procedure to register a new password is specified in GSM 04.10. ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 13 3G TS 24.088 version 3.0.0 2.3 Activation If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by subscriber using password", the supplementary service is activated for a basic service if the subscriber has requested so by means of an activation procedure for that basic service. If the subscriber does not indicate a specific basic service, the activation applies to all basic services. The subscriber may use the call barring password at activation (see figure 2.2). If the activation is successful, the service will be activated. The network will then send a return result indicating acceptance of the request. The result is formatted according to the options shown below: - The result includes the Basic Service group Code(s) to which the service is activated. The result may also contain an SS-Code and SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then these parameters shall be presented in the result. If the MS does send an SS Version Indicator in the invocation request then these parameters are optional in the result. If the SS-Status is included the network shall set it to reflect the state of the service. If the SS-Code is included then it shall contain the SS-Code of the service which has been activated. The MS shall ignore the contents of the SS-Code and SS-Status parameters if they are received. Note that the use of SS-Code and SS-Status is to provide backwards compatibility with GSM Phase 1. - If the request did not include a BasicServiceCode, and the activation was successful for all basic services, the network may send an empty return result to the MS. This option applies whether or not an SS Version Indicator is received from the MS. If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by service provider", an attempt to activate the service will be denied and the served mobile subscriber receives an error indication (see figure 2.2). Error values are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = ActivateSS (SS-Code, BasicServiceCode)) Password procedure according to GSM 04.10 RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = ActivateSS (SS-Code, BasicServiceCode, SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code will be one of the specific incoming barring codes. If BasicServiceCode is not included it applies to all basic services. The SS-Code and SS-Status may not be included in the result in all cases (see text). Figure 2.2: Activation of a barring program ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 14 3G TS 24.088 version 3.0.0 2.4 Deactivation If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by subscriber using password", the supplementary service is deactivated for a basic service if the subscriber has requested deactivation by means of a deactivation procedure for that basic service. The subscriber may use the call barring password at deactivation (see figure 2.3). If the deactivation is successful, the service will be deactivated. The network will then send a return result indicating acceptance of the request. The result is formatted according to the options shown below: - The result includes the Basic Service group Code(s) to which the service is deactivated. The result may also contain an SS-Code and SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then these parameters shall be presented in the result. If the MS does send an SS Version Indicator in the invocation request then these parameters are optional in the result. If the SS-Status is included the network shall set it to reflect the state of the service. If the SS-Code is included then it shall contain the SS-Code of the service which has been deactivated. The MS shall ignore the contents of the SS-Code and SS-Status parameters if they are received. Note that the use of SS-Code and SS-Status is to provide backwards compatibility with GSM Phase 1. - If the request did not include a BasicServiceCode, and the deactivation was successful for all basic services, the network may send an empty return result to the MS. This option applies whether or not an SS Version Indicator is received from the MS. If the served mobile subscriber at provision time has selected the subscription option "control of barring service: by service provider", an attempt to deactivate the supplementary service will be denied and the served mobile subscriber receives an error indication (see figure 2.3). Error values are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = DeactivateSS (SS-Code, BasicServiceCode)) Password procedure according to GSM 04.10 RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = DeactivateSS (SS-Code, BasicServiceCode, SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may be one of the specific incoming barring codes, the common code for the incoming barring services, or the SS-Code for all call barring services. If BasicServiceCode is not included it applies to all basic services. The SS-Code and SS-Status may not be included in the result in all cases (see text). Figure 2.3: Deactivation of barring of incoming calls ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 15 3G TS 24.088 version 3.0.0 2.5 Interrogation The interrogation procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return a list of all basic service groups for which the service is active (see figure 2.4). If there is no basic service group for which the service is active, an SS-Status will be returned indicating that the service is "deactivated". MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (SS-Code)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode)) or RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may be one of the specific incoming barring codes. Figure 2.4: Interrogation of a barring program 2.6 Invocation and erasure Invocation and erasure are not applicable to barring programs. 2.7 Cross phase compatibility 2.7.1 Network only supports GSM Phase 1 control of SS by the subscriber In this case there is no relevant cross phase compatibility problem. 2.7.2 MS only supports protocol version 1 control of SS by the subscriber The NotifySS operation containing the SS-Status indicating that a barring program relating to incoming calls is currently active and operative shall be sent to the calling subscriber only in the RELEASE COMPLETE message, if the MS only supports GSM Phase 1. ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.088 V3.0.0 (1999-05) 16 3G TS 24.088 version 3.0.0 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 04.88 6.0.1 Transferred to 3GPP CN1 CN#03 24.088 3.0.0 Approved at CN#03 ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) ETSI 17 ETSI ETSI TS 124 088 V3.0.0 (2000-01) (3G TS 24.088 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
1 Scope
|
........................................................................................................................................................5
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
2 References
|
................................................................................................................................................5
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
3 Definitions and abbreviations
|
..................................................................................................................5
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
3.1 Definitions
|
......................................................................................................................................................... 5
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
3.2 Abbreviations
|
..................................................................................................................................................... 6
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4 User-to-User Signalling (UUS); served mobile subscriber side
|
..............................................................6
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.1 UUS1
|
................................................................................................................................................................. 6
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.1.1 Operation when implicitly activated
|
............................................................................................................ 7
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.1.2 Operation when explicitly activated
|
............................................................................................................. 7
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.1.2.1 UUS required
|
.......................................................................................................................................... 8
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.1.2.2 UUS not required
|
.................................................................................................................................... 9
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.2 UUS2
|
................................................................................................................................................................. 9
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.2.1 Operation
|
.................................................................................................................................................... 10
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.2.1.1 UUS required
|
........................................................................................................................................ 11
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.2.1.2 UUS not required
|
.................................................................................................................................. 12
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.3 UUS3
|
............................................................................................................................................................... 12
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.3.1 Activation when originating a call
|
............................................................................................................. 12
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.3.1.1 UUS required
|
........................................................................................................................................ 14
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.3.1.2 UUS not required
|
.................................................................................................................................. 14
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.3.2 Activation during an active call
|
.................................................................................................................. 15
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.3.3 Invocation and operation
|
............................................................................................................................ 16
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.3.4 Flow Control
|
.............................................................................................................................................. 16
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
4.4 Combination of UUS Services
|
......................................................................................................................... 17
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
5 User-to-User Signalling (UUS); remote mobile subscriber side
|
...........................................................18
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
5.1 UUS1
|
............................................................................................................................................................... 19
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
5.1.1 Operation when explicitly activated, UUS required
|
................................................................................... 19
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
5.1.2 Operation when explicitly activated, UUS not required
|
............................................................................. 20
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
5.2 UUS2
|
............................................................................................................................................................... 21
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
5.2.1 Operation, UUS required
|
............................................................................................................................ 21
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
5.2.2 Operation, UUS not required
|
..................................................................................................................... 22
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
5.3 UUS3
|
............................................................................................................................................................... 23
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
5.3.1 Activation when originating a call
|
............................................................................................................. 23
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
5.3.1.1 UUS required
|
........................................................................................................................................ 23
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
5.3.1.2 UUS not required
|
.................................................................................................................................. 23
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
5.3.2 Activation during an active call
|
.................................................................................................................. 24
|
ee2c935c1685ff867baa8ebca666cae8
|
124 087
|
6 Identification of parallel transactions in UUS
|
.......................................................................................24 Annex A (normative): Cause values used in UUS supplementary service......................................25 Annex B: Change history......................................................................................................................26 History..............................................................................................................................................................27 ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 4 3G TS 24.087 version 3.0.0 Foreword This Technical Specification has been produced by the 3GPP. This TS gives the stage 3 description of the User-to-User signalling supplementary services within the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 5 3G TS 24.087 version 3.0.0 1 Scope This Technical Specification gives the stage 3 description of the User-to-User signalling supplementary services. The User-to-user supplementary service is divided into 3 different services: - Service 1 (UUS1) - Service 2 (UUS2) - Service 3 (UUS3) 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 03.87: "Digital cellular telecommunications system (Phase 2+); User-to-User Signalling (UUS); Stage 2". [3] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification ". [4] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following definitions apply: Remote party: For service 1 and 2 the remote party is the called party of a call to which the served subscriber activates the UUS supplementary service. For service 3 the remote party can be either the called or the calling party of an established call to whom the use of the UUS supplementary service is requested by the served subscriber. Served subscriber: The subscriber who has a provision of the UUS supplementary service and who activates the UUS supplementary service. For service 1 and 2 the served subscriber is always the calling subscriber, for service 3 either the calling or the called subscriber can be the served subscriber. User-to-User Information (UUI): The information transferred by using the UUS supplementary service. UUS not required: If the "UUS not required" indication is given by the subscriber, the call will be completed even if UUI cannot be passed to the called subscriber. ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 6 3G TS 24.087 version 3.0.0 UUS required: If the "UUS required" indication is given by the subscriber, the call shall not be completed if UUI cannot be passed to the called subscriber. UUS Service: The UUS services (Service 1, 2 and 3) are components of the UUS supplementary service. If the UUS supplementary service is provided to a subscriber, he can handle the UUS services independently within a call. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: MS A Mobile Station A, the mobile station of the served subscriber MS B Mobile Station B, the mobile station of the remote subscriber UUI User-to-User Information UUS User-to-User Signalling UUS1 User-to-User Signalling Service 1 UUS2 User-to-User Signalling Service 2 UUS3 User-to-User Signalling Service 3 Further GSM related abbreviations are listed in GSM 01.04. 4 User-to-User Signalling (UUS); served mobile subscriber side 4.1 UUS1 For UUS1, both parties may exchange UUI during the set-up and the clearing phases of a call by including User-user information element(s) in basic call control messages (ALERTING, CONNECT, DISCONNECT, PROGRESS, RELEASE, RELEASE COMPLETE, SETUP). UUS1 can be activated implicitly or explicitly. When UUS1 has been activated, either subscriber may include UUI when accepting, rejecting or terminating the call. UUS1 is automatically deactivated when the call is cleared. ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 7 3G TS 24.087 version 3.0.0 4.1.1 Operation when implicitly activated To activate UUS1 implicitly, the MS A shall include a User-user information element in the SETUP message as part of a normal call request. See GSM 04.08. Implicitly activated UUS1 is active for the duration of the call; i.e. the remote party is not required to send a response to the implicit activation request. However, the remote party may include a User-user information element in the call response. The served subscriber or the remote party may terminate the call before a connection is established. MS A NETWORK SETUP -----------------------------------------------------------------------------------------------------------------------------> User-user . ALERTING <---------------------------------------------------------------------------------------------------------------------------- User-user (Note 1) CONNECT <---------------------------------------------------------------------------------------------------------------------------- User-user (Note 1) . . DISCONNECT / RELEASE / RELEASE COMPLETE <---------------------------------------------------------------------------------------------------------------------------> User-user (Note 1), (Note 2) NOTE 1: The User-user information element is optional. NOTE 2: Under normal conditions DISCONNECT message is used for clearing the call, but also RELEASE or RELEASE COMPLETE message may be used as the first call clearing message. Figure 1: UUS1 when implicitly activated 4.1.2 Operation when explicitly activated UUS1 is explicitly requested by the MS A when including a Facility information element with a UserUserService invoke component in the SETUP message. See GSM 04.08, GSM 04.80. The UserUserService invoke component shall indicate whether the service is "UUS required" or "UUS not required". If the remote party accepts the request, the network shall include a Facility information element with a UserUserService Return Result component in the ALERTING or the CONNECT message sent to the MS A. If the request is not accepted, the network shall include a Facility information element with a UserUserService Return Error component in the DISCONNECT message (when UUS required) or in the ALERTING or in the CONNECT message (when UUS not required) sent to the MS A. See errors in GSM 04.80. An explicit activation request may include UUI. The network may include User-user information element when accepting the activation request. The served subscriber or the remote party may terminate the call before a connection is established. For UUS1 explicit activation SS Version Indicator value 3 or above has to be used. ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 8 3G TS 24.087 version 3.0.0 4.1.2.1 UUS required If the MS A gives the "UUS required" indication, the call shall not be completed if UUI cannot be passed to the remote party. MS A NETWORK SETUP -----------------------------------------------------------------------------------------------------------------------------> Facility (Invoke=UserUserService (UUS1, UUS required)), User-user (Note 1) . . ALERTING <---------------------------------------------------------------------------------------------------------------------------- Facility (Return Result), User-user (Note 1), (Note 2) DISCONNECT / RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return Error (Error), Cause (Note 3) CONNECT <---------------------------------------------------------------------------------------------------------------------------- User-user (Note 1), (Note 2), (Note 4) . . DISCONNECT / RELEASE / RELEASE COMPLETE <---------------------------------------------------------------------------------------------------------------------------> User-user (Note 1), (Note 5) NOTE 1: The User-user information element is optional. NOTE 2: The Return Result component in the Facility information element shall be sent either in the ALERTING or in the CONNECT message. NOTE 3: If the remote party rejects the service request or does not respond with an explicit service 1 acceptance or rejection, DISCONNECT message is sent to the MS A with Facility information element including Return Error component with error value "rejectedByUser". If the network rejects the request, the error value shall be "rejectedByNetwork". See information on Cause values in Annex A. NOTE 4: If the MS A does not receive an explicit service 1 acceptance or rejection in the ALERTING or the CONNECT message, the MS A shall clear the call. UUS1 is not activated. NOTE 5: Under normal conditions DISCONNECT message is used for clearing the call, but also RELEASE or RELEASE COMPLETE message may be used as the first call clearing message. Figure 2: Request for explicit activation of UUS1, UUS required ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 9 3G TS 24.087 version 3.0.0 4.1.2.2 UUS not required If the MS A gives the "UUS not required" indication, the call will be completed even if UUI cannot be passed to the remote party. MS A NETWORK SETUP -----------------------------------------------------------------------------------------------------------------------------> Facility (Invoke=UserUserService (UUS1, UUS not required)), User-user (Note 1) . . ALERTING <---------------------------------------------------------------------------------------------------------------------------- Facility (Return Result), User-user (Note 1), (Note 2) ALERTING / CONNECT <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return Error (Error) (Note 3) CONNECT <---------------------------------------------------------------------------------------------------------------------------- User-user (Note 1), (Note 2) . . . DISCONNECT / RELEASE / RELEASE COMPLETE <---------------------------------------------------------------------------------------------------------------------------> User-user (Note 1), (Note 4) NOTE 1: The User-user information element is optional. NOTE 2: The Return Result component in the Facility information element shall be sent either in the ALERTING or in the CONNECT message. NOTE 3: If the MS A does not receive an explicit service 1 acceptance or rejection in the ALERTING or the CONNECT message, the served subscriber shall continue normal call handling. UUS1 is not activated. NOTE 4: Under normal conditions DISCONNECT message is used for clearing the call, but also RELEASE or RELEASE COMPLETE message may be used as the first call clearing message. Figure 3: Request for explicit activation of UUS1, UUS not required 4.2 UUS2 For UUS2, both parties may send UUI after the alerting indication has been sent/received and until the connect indication has been sent/received. The UUI is sent in USER INFORMATION message and is limited to two messages in each direction. UUS2 is automatically deactivated when the called subscriber is no longer being informed of the call, i.e. if the call is established or released. ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 10 3G TS 24.087 version 3.0.0 4.2.1 Operation In order to activate UUS2 the MS A shall include a Facility information element with a UserUserService invoke component indicating service 2 in the SETUP message. See GSM 04.08, GSM 04.80. The UserUserService invoke component shall also indicate whether the service is "UUS required" or "UUS not required". If the remote party accepts the request, the network shall include a Facility information element with a UserUserService Return Result component in the ALERTING message received by the MS A. If the request is not accepted, the network shall include a Facility information element with a UserUserService Return Error component in the DISCONNECT message (when UUS required) or in the ALERTING or in the CONNECT message (when UUS not required) sent to the MS A. See errors in GSM 04.80. At any time between the activation of UUS2 and the connection is being established, either subscriber may transfer up to two USER INFORMATION messages in each direction to the other subscriber involved in the call. User-user information element is mandatory in USER INFORMATION message (refer GSM 04.08). More data information element may be included in USER INFORMATION message indicating that another USER INFORMATION message pertaining to the same message block will follow. For UUS2 activation SS Version Indicator value 3 or above has to be used. ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 11 3G TS 24.087 version 3.0.0 4.2.1.1 UUS required If the MS A gives the "UUS required" indication, the call shall not be completed if UUI cannot be passed to the remote party. MS A NETWORK SETUP -----------------------------------------------------------------------------------------------------------------------------> Facility (Invoke=UserUserService (UUS2, UUS required)) . . ALERTING <---------------------------------------------------------------------------------------------------------------------------- Facility (Return Result) (Note 1) DISCONNECT / RELEASE COMPLETE / RELEASE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return Error (Error), Cause (Note 2) USER INFORMATION <----------------------------------------------------------------------------------------------------------------------------> User-user, More data (Note 3) . . CONNECT <---------------------------------------------------------------------------------------------------------------------------- (Note 1) NOTE 1: If the MS A does not receive an explicit service 2 acceptance or rejection in the ALERTING message or does not receive an ALERTING message before receiving the CONNECT message, the served subscriber shall clear the call. UUS2 is not activated. NOTE 2: If the remote party rejects the service request or does not respond with an explicit service 2 acceptance or rejection, DISCONNECT message is sent to the MS A with Facility information element including Return Error component with error value "rejectedByUser". If the network rejects the request, the error value shall be "rejectedByNetwork". See information on Cause values in Annex A. NOTE 3: User-user information element is mandatory and More data information element is optional in USER INFORMATION message. Figure 4: Request for explicit activation of UUS2, UUS required ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 12 3G TS 24.087 version 3.0.0 4.2.1.2 UUS not required If the MS A gives the "UUS not required" indication, the call will be completed even if UUI cannot be passed to the remote party. MS A NETWORK SETUP -----------------------------------------------------------------------------------------------------------------------------> Facility (Invoke=UserUserService (UUS2, UUS not required)) . . ALERTING <---------------------------------------------------------------------------------------------------------------------------- Facility (Return Result) (Note 1) ALERTING <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return Error (Error)) USER INFORMATION <---------------------------------------------------------------------------------------------------------------------------> User-user, More data (Note 2) . . CONNECT <---------------------------------------------------------------------------------------------------------------------------- (Note 1) NOTE 1: If the MS A does not receive an explicit service 2 acceptance or rejection in the ALERTING message or does not receive an ALERTING message before receiving the CONNECT message, the served subscriber shall continue normal call handling. UUS2 is not activated. NOTE 2: User-user information element is mandatory and More data information element is optional in USER INFORMATION message. Figure 5: Request for explicit activation of UUS2, UUS not required 4.3 UUS3 For UUS3, both parties may send UUI in the active phase of a call using USER INFORMATION messages. UUS3 shall be activated explicitly, when a call is originated or after the connection has been established. After UUS3 has been activated, either subscriber may transfer UUI in USER INFORMATION messages to the other subscriber on the call. UUS3 is automatically deactivated when the call is released. For UUS3 activation SS Version Indicator value 3 or above has to be used. 4.3.1 Activation when originating a call When UUS3 is activated during call establishment, the MS A shall include Facility information element with UserUserService operation in an Invoke component indicating UUS3 in the SETUP message. See GSM 04.08, ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 13 3G TS 24.087 version 3.0.0 GSM 04.80. The UserUserService operation shall also indicate whether the service is "UUS required" or "UUS not required". If the remote party accepts the request, the network shall include a Facility information element with a UserUserService Return Result component in the CONNECT message sent to the MS A. If the request is not accepted, the network shall include a Facility information element with a UserUserService Return Error component in the DISCONNECT message (when UUS required) or in the CONNECT message (when UUS not required) sent to the MS A. See errors in GSM 04.80. ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 14 3G TS 24.087 version 3.0.0 4.3.1.1 UUS required If the MS A gives the "UUS required" indication, the call shall not be completed if UUI cannot be passed to the remote party. MS A NETWORK SETUP -----------------------------------------------------------------------------------------------------------------------------> Facility (Invoke=UserUserService (UUS3, UUS required)) . . CONNECT <---------------------------------------------------------------------------------------------------------------------------- Facility (Return Result) (Note 1) DISCONNECT / RELEASE COMPLETE / RELEASE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return Error (Error), Cause (Note 2) NOTE 1: If the MS A does not receive an explicit service 3 acceptance or rejection in the CONNECT message, the MS A shall clear the call. NOTE 2: If the remote party rejects the service request or does not respond with an explicit service 3 acceptance or rejection, DISCONNECT message is sent to the MS A with Facility information element including Return Error component with error value "rejectedByUser". If the network rejects the request, the error value shall be "rejectedByNetwork". See information on Cause values in Annex A. Figure 6: Request for explicit activation of UUS3 when originating a call, UUS required 4.3.1.2 UUS not required If the MS A gives the "UUS not required" indication, the call will be completed even if UUI cannot be passed to the remote party. MS A NETWORK SETUP -----------------------------------------------------------------------------------------------------------------------------> Facility (Invoke=UserUserService (UUS3, UUS not required)) . . CONNECT <---------------------------------------------------------------------------------------------------------------------------- Facility (Return Result) CONNECT <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return Error (Error)) (Note 1) NOTE 1: If the MS A does not receive an explicit service 3 acceptance or rejection in the CONNECT message, the MS A shall continue normal call handling and assume that service 3 is not activated. Figure 7: Request for explicit activation of UUS3 when originating a call, UUS not required ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 15 3G TS 24.087 version 3.0.0 4.3.2 Activation during an active call When UUS3 is activated during an active call, the MS A shall include a Facility information element with a UserUserService invoke component indicating service 3 in a FACILITY message. See GSM 04.08, GSM 04.80. The UserUserService operation shall indicate that the service is "UUS not required". If the remote party accepts the request, the network shall include a Facility information element with a UserUserService Return Result component in the FACILITY message sent to the MS A. If the request is not accepted, the network shall include a Facility information element with a UserUserService Return Error component in the FACILITY message sent to the MS A. See errors in GSM 04.80. MS A NETWORK Active call <----------------------------------------------------------------------------------------------------------------------------> FACILITY -----------------------------------------------------------------------------------------------------------------------------> Facility (Invoke=UserUserService (UUS3, UUS not required)) FACILITY <---------------------------------------------------------------------------------------------------------------------------- Facility (Return Result) FACILITY <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return Error (Error)) (Note 1) NOTE 1: If the remote party rejects the service request or does not respond with an explicit service 3 acceptance of rejection, the FACILITY message includes Facility information element with Return Error component indicating error "rejectedByUser". If the network rejects the request, the error value shall be "rejectedByNetwork". Figure 8: Request for explicit activation of UUS3 during an active call ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 16 3G TS 24.087 version 3.0.0 4.3.3 Invocation and operation After Service 3 has been activated, either subscriber may transfer UUI in USER INFORMATION messages to the other subscriber on the call after the connection has been established. User-user information element is mandatory in USER INFORMATION message. More data information element may be included in USER INFORMATION message indicating that another USER INFORMATION message pertaining to the same message block will follow. MS A NETWORK Active call <----------------------------------------------------------------------------------------------------------------------------> USER INFORMATION <----------------------------------------------------------------------------------------------------------------------------> User-user, More data (Note 1) . . DISCONNECT /RELEASE / RELEASE COMPLETE <---------------------------------------------------------------------------------------------------------------------------> (Note 2) NOTE 1: User-user information element is mandatory and More data information element is optional in USER INFORMATION message. NOTE 2: Under normal conditions DISCONNECT message is used for clearing the call, but also RELEASE or RELEASE COMPLETE message may be used as the first call clearing message. Figure 9: Sending USER INFORMATION messages when UUS3 has been activated 4.3.4 Flow Control Network flow control mechanisms shall exist after the call has entered the Active call state to control USER INFORMATION message flow in each direction. If USER INFORMATION messages are received at a rate which exceeds the flow control limit set by the network, the network shall discard the USER INFORMATION messages that cannot be handled and respond to the first discarded USER INFORMATION message with a control indication. If USER INFORMATION message has been discarded due to flow control, a CONGESTION CONTROL message shall be sent to the MS. When the flow control restrictions are removed, and a USER INFORMATION message has been discarded due to that restriction, an indication that further USER INFORMATION messages can be accepted shall be given. ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 17 3G TS 24.087 version 3.0.0 MS A NETWORK Active call <----------------------------------------------------------------------------------------------------------------------------> USER INFORMATION -----------------------------------------------------------------------------------------------------------------------------> User-user, More data (Note 1) . . USER INFORMATION ----------------------------------------------------------------------------------------------------------------------------> User-user, More data (Note 1), (Note 2) CONGESTION CONTROL <----------------------------------------------------------------------------------------------------------------------------- Congestion level = receiver not ready, Cause #43 (access information discarded) . USER INFORMATION -----------------------------------------------------------------------------------------------------------------------------> User-user, More data (Note 1), (Note 2) . . CONGESTION CONTROL <---------------------------------------------------------------------------------------------------------------------------- Congestion level = receiver ready NOTE 1: User-user information element is mandatory and More data information element is optional in USER INFORMATION message. NOTE 2: Due to the flow control the USER INFORMATION message is discarded. Figure 10: UUS3, Flow control A more detailed presentation of flow control mechanisms is given in UUS Stage 2. 4.4 Combination of UUS Services Depending on the served subscriber’s subscription to the UUS supplementary service and the provision of the UUS services by the service provider, UUS1 implicit or explicit, UUS2 and UUS3 can be activated individually or in combination. The following figure is an example of the situation, when UUS1, UUS2 and UUS3 are simultaneously activated as "UUS required". ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 18 3G TS 24.087 version 3.0.0 MS A NETWORK SETUP -----------------------------------------------------------------------------------------------------------------------------> Facility (Invoke=UserUserService (UUS1, UUS required), Invoke=UserUserService (UUS2, UUS required), Invoke=UserUserService (UUS3, UUS required)), User-user (Note 1) . . ALERTING <---------------------------------------------------------------------------------------------------------------------------- Facility (Return Result, Return Result), User-user (Note 1), (Note 2) . . . CONNECT <---------------------------------------------------------------------------------------------------------------------------- Facility (Return Result), User-user (Note 1), (Note 2) NOTE 1: The User-user information element is optional. NOTE 2: For UUS1 the Return Result component in the Facility information element may be sent either in the ALERTING or in the CONNECT message. For UUS2 the Return Result component in the Facility information element is sent in the ALERTING message. For UUS3 the Return Result component in the Facility information element is sent in the CONNECT message. Figure 11: Request for explicit activation of UUS1, UUS2 and UUS3 simultaneously 5 User-to-User Signalling (UUS); remote mobile subscriber side If the network has received a non-zero SS screening indicator from the remote MS, the description in the subclauses 5.1 to 5.3 applies. If the network has received a zero SS screening indicator from the remote MS, three cases exist: If UUS service was requested as „UUS required" during the call establishment, then the SETUP message will not be sent to the remote MS. If UUS service was requested as „UUS not required" during the call establishment, then the SETUP message will be sent to the remote MS without the Facility information element including the UUS service activation request. If UUS service was requested during an active call, then the Facility information element including the request of UUS service activation will not be sent to the remote MS. ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 19 3G TS 24.087 version 3.0.0 5.1 UUS1 5.1.1 Operation when explicitly activated, UUS required In this subclause the operation of UUS1, explicitly activated and with the indication "UUS required", is described at the remote mobile subscriber side. MS B NETWORK SETUP <---------------------------------------------------------------------------------------------------------------------------- Facility (Invoke=UserUserService (UUS1, UUS required)), User-user (Note 1) . . ALERTING ---------------------------------------------------------------------------------------------------------------------------> Facility (Return Result), User-user (Note 1), (Note 2) ALERTING - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > (Note 3) CONNECT ---------------------------------------------------------------------------------------------------------------------------> User-user (Note 1), (Note 2) CONNECT - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > (Note 3) . . DISCONNECT / RELEASE COMPLETE / RELEASE <---------------------------------------------------------------------------------------------------------------------------> User-user (Note 1), (Note 3), (Note 4) NOTE 1: The User-user information element is optional. NOTE 2: The Return Result component in the Facility information element may be sent either in the ALERTING or in the CONNECT message. NOTE 3: If the MS B does not respond with an explicit service 1 acceptance or rejection, ALERTING or CONNECT message does not include a Return Result component. The following DISCONNECT message clears the call. See information on Cause values in Annex A. NOTE 4: Under normal conditions DISCONNECT message is used for clearing the call, but also RELEASE or RELEASE COMPLETE message may be used as the first call clearing message. Figure 12: Request for explicit activation of UUS1, UUS required ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 20 3G TS 24.087 version 3.0.0 5.1.2 Operation when explicitly activated, UUS not required In this subclause the operation of UUS1, explicitly activated and with the indication "UUS not required", is described at the remote mobile subscriber side. MS B NETWORK SETUP <---------------------------------------------------------------------------------------------------------------------------- Facility (Invoke=UserUserService (UUS1, UUS not required)), User-user (Note 1) . . ALERTING ---------------------------------------------------------------------------------------------------------------------------> Facility (Return Result), User-user (Note 1), (Note 2) ALERTING / CONNECT - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > Facility (Return Error) CONNECT ---------------------------------------------------------------------------------------------------------------------------> User-user (Note 1), (Note 2) . . DISCONNECT / RELEASE COMPLETE / RELEASE <---------------------------------------------------------------------------------------------------------------------------> User-user (Note 1), (Note 3) NOTE 1: The User-user information element is optional. NOTE 2: The Return Result component in the Facility information element may be sent either in the ALERTING or in the CONNECT message. NOTE 3: Under normal conditions DISCONNECT message is used for clearing the call, but also RELEASE or RELEASE COMPLETE message may be used as the first call clearing message. Figure 13: Request for explicit activation of UUS1, UUS not required ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 21 3G TS 24.087 version 3.0.0 5.2 UUS2 5.2.1 Operation, UUS required In this subclause the operation of UUS2, with the indication "UUS required", is described at the remote mobile subscriber side. MS B NETWORK SETUP <----------------------------------------------------------------------------------------------------------------------------- Facility (Invoke=UserUserService (UUS2, UUS required)) . . ALERTING ---------------------------------------------------------------------------------------------------------------------------> Facility (Return Result) ALERTING - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > (Note 1) DISCONNECT / RELEASE COMPLETE / RELEASE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cause (Note 1) USER INFORMATION <----------------------------------------------------------------------------------------------------------------------------> User-user, More data (Note 2) . . CONNECT ----------------------------------------------------------------------------------------------------------------------------> NOTE 1: If the MS B does not respond with an explicit service 2 acceptance or rejection, ALERTING message does not include a Return Result component. The following DISCONNECT message clears the call. See information on Cause values in Annex A. NOTE 2: User-user information element is mandatory and More data information element is optional in USER INFORMATION message. Figure 14: Request for explicit activation of UUS2, UUS required ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 22 3G TS 24.087 version 3.0.0 5.2.2 Operation, UUS not required In this subclause the operation of UUS2, with the indication "UUS not required", is described at the remote mobile subscriber side. MS B NETWORK SETUP <----------------------------------------------------------------------------------------------------------------------------- Facility (Invoke=UserUserService (UUS2, UUS not required)) . . ALERTING ---------------------------------------------------------------------------------------------------------------------------> Facility (Return Result) ALERTING - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > Facility (Return Error) USER INFORMATION <----------------------------------------------------------------------------------------------------------------------------> User-user, More data (Note 1) . . CONNECT ----------------------------------------------------------------------------------------------------------------------------> NOTE 1: User-user information element is mandatory and More data information element is optional in USER INFORMATION message. Figure 15: Request for explicit activation of UUS2, UUS not required ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 23 3G TS 24.087 version 3.0.0 5.3 UUS3 5.3.1 Activation when originating a call 5.3.1.1 UUS required In this subclause the activation of UUS3 when originating a call, with the indication "UUS required", is described at the remote mobile subscriber side. MS B NETWORK SETUP <----------------------------------------------------------------------------------------------------------------------------- Facility (Invoke=UserUserService (UUS3, UUS required)) . . CONNECT ----------------------------------------------------------------------------------------------------------------------------> Facility (Return Result) CONNECT - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -> DISCONNECT <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cause (Note 1) NOTE 1: If the MS B does not respond with an explicit service 3 acceptance or rejection, DISCONNECT message is sent to the MS B to clear the call. See information on Cause values in Annex A. Figure 16: Request for explicit activation of UUS3 when originating a call, UUS required 5.3.1.2 UUS not required In this subclause the activation of UUS3 when originating a call, with the indication "UUS not required", is described at the remote mobile subscriber side. MS B NETWORK SETUP <----------------------------------------------------------------------------------------------------------------------------- Facility (Invoke=UserUserService (UUS3, UUS not required)) . . CONNECT ----------------------------------------------------------------------------------------------------------------------------> Facility (Return Result) CONNECT - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -> Facility (Return Error) Figure 17: Request for explicit activation of UUS3 when originating a call, UUS not required ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 24 3G TS 24.087 version 3.0.0 5.3.2 Activation during an active call In this subclause the activation of UUS3 during an active call is described at the remote mobile subscriber side. MS B NETWORK Active call <----------------------------------------------------------------------------------------------------------------------------> . . FACILITY <----------------------------------------------------------------------------------------------------------------------------- Facility (Invoke=UserUserService (UUS3, UUS not required)) FACILITY ----------------------------------------------------------------------------------------------------------------------------> Facility (Return Result) FACILITY - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -> Facility (Return Error (Error)) (Note 1) NOTE 1: If the remote party rejects the service request or does not respond with an explicit service 3 acceptance of rejection, the FACILITY message includes Facility information element with Return Error component indicating error "rejectedByUser". If the network rejects the request, the error value shall be "rejectedByNetwork". Figure 18: Request for explicit activation of UUS3 during an active call If more than one parallel CC transaction is active, UUS operations are directed to the desired transaction identified by the pertaining transaction identifier. ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 25 3G TS 24.087 version 3.0.0 Annex A (normative): Cause values used in UUS supplementary service Cause value Situation Information on usage #29 facility rejected To served mobile subscriber side, call clearing If the remote party rejects the activation request of a UUS service, the Cause value #29 is sent to the served subscriber. #47 resource unavailable, unspecified To served mobile subscriber side, call clearing If the network rejects the activation request of a UUS service, the Cause value #47 or #50 is sent to the served subscriber. #50 requested facility not subscribed To served mobile subscriber side, call clearing If the network rejects the activation request of a UUS service, the Cause value #47 or #50 is sent to the served subscriber. #69 requested facility not implemented To served mobile subscriber side, call clearing If the remote party does not respond with an explicit UUS service acceptance or rejection to the activation request, the Cause value #69 is sent to the served subscriber. #31 normal, unspecified To remote mobile subscriber side, call clearing If the remote party does not respond with an explicit UUS service acceptance or rejection, the Cause value #31 is sent to him. #43 access information discarded To served mobile subscriber side, flow control The Cause value #43 is sent within CONGESTION CONTROL message to the served subscriber. ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.087 V3.0.0 (1999-05) 26 3G TS 24.087 version 3.0.0 Annex B: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 04.87 7.0.0 Transferred to 3GPP CN1 CN#03 24.087 3.0.0 Approved at CN#03 ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) ETSI 27 ETSI ETSI TS 124 087 V3.0.0 (2000-01) (3G TS 24.087 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
|
848488317adf16c49e39417600a4774c
|
124 086
|
0.1 References
|
.......................................................................................................................................................... 5
|
848488317adf16c49e39417600a4774c
|
124 086
|
0.2 Abbreviations
|
..................................................................................................................................................... 6
|
848488317adf16c49e39417600a4774c
|
124 086
|
1 Advice of Charge (Information) (AoCI)
|
..................................................................................................7
|
848488317adf16c49e39417600a4774c
|
124 086
|
1.1 Normal operation with successful outcome
|
....................................................................................................... 7
|
848488317adf16c49e39417600a4774c
|
124 086
|
1.1.1 Call re-establishment
|
.................................................................................................................................... 7
|
848488317adf16c49e39417600a4774c
|
124 086
|
1.1.2 MS originated call
|
........................................................................................................................................ 7
|
848488317adf16c49e39417600a4774c
|
124 086
|
1.1.3 MS terminated call
|
....................................................................................................................................... 7
|
848488317adf16c49e39417600a4774c
|
124 086
|
1.1.4 Change of charging information
|
................................................................................................................... 8
|
848488317adf16c49e39417600a4774c
|
124 086
|
1.2 Normal operation with unsuccessful outcome
|
................................................................................................... 8
|
848488317adf16c49e39417600a4774c
|
124 086
|
1.3 Activation, deactivation and invocation
|
............................................................................................................. 8
|
848488317adf16c49e39417600a4774c
|
124 086
|
1.4 Interrogation, registration and erasure
|
............................................................................................................... 8
|
848488317adf16c49e39417600a4774c
|
124 086
|
2 Advice of Charge (Charging) (AoCC)
|
.....................................................................................................8
|
848488317adf16c49e39417600a4774c
|
124 086
|
2.1 Normal operation with successful outcome
|
....................................................................................................... 8
|
848488317adf16c49e39417600a4774c
|
124 086
|
2.1.1 Call re-establishment
|
.................................................................................................................................... 9
|
848488317adf16c49e39417600a4774c
|
124 086
|
2.1.2 MS originated call
|
........................................................................................................................................ 9
|
848488317adf16c49e39417600a4774c
|
124 086
|
2.1.3 MS terminated call
|
....................................................................................................................................... 9
|
848488317adf16c49e39417600a4774c
|
124 086
|
2.1.4 Change of charging information
|
................................................................................................................... 9
|
848488317adf16c49e39417600a4774c
|
124 086
|
2.2 Normal operation with unsuccessful outcome
|
................................................................................................. 10
|
848488317adf16c49e39417600a4774c
|
124 086
|
2.3 Accumulated Call Meter is equal to or greater than ACMmax
|
........................................................................ 10
|
848488317adf16c49e39417600a4774c
|
124 086
|
2.4 Activation, deactivation and invocation
|
........................................................................................................... 10
|
848488317adf16c49e39417600a4774c
|
124 086
|
2.5 Interrogation, registration and erasure
|
............................................................................................................. 10 Annex A: Change history......................................................................................................................11 History..............................................................................................................................................................12 ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.086 V3.0.0 (1999-05) 4 3G TS 24.086 version 3.0.0 Foreword This Technical Specification has been produced by the 3GPP. This TS specifies the procedures used at the radio interface for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of charging supplementary services within the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.086 V3.0.0 (1999-05) 5 3G TS 24.086 version 3.0.0
|
848488317adf16c49e39417600a4774c
|
124 086
|
0 Scope
|
The present document specifies the procedures used at the radio interface (reference point Um as defined in GSM 04.02) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of charging supplementary services. The provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and causes no signalling on the radio interface. In GSM 04.10 the general aspects of the specification of supplementary services at the layer 3 radio interface are given. GSM 04.80 specifies the formats and coding for the supplementary services. Definitions and descriptions of supplementary services are given in GSM 02.04 and GSM 02.8x and GSM 02.9x-series. GSM 02.24 and 02.86 are related to the charging supplementary services. Technical realization of supplementary services is described in GSM 03.11 and GSM 03.8x and GSM 03.9x-series. GSM 03.86 is related to the charging supplementary services. The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in GSM 04.07 and GSM 04.08. The following supplementary services belong to the charging supplementary services and are described in the present document: - Advice of Charge (Information) (AoCI) (clause 1); - Advice of Charge (Charging) (AoCC) (clause 2). 0.1 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [3] GSM 02.24: "Digital cellular telecommunications system (Phase 2+); Description of Charge Advice Information (CAI)". [4] GSM 02.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 1". [5] GSM 02.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 1". [6] GSM 02.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1". [7] GSM 02.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 1". ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.086 V3.0.0 (1999-05) 6 3G TS 24.086 version 3.0.0 [8] GSM 02.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 1". [9] GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 1". [10] GSM 02.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 1". [11] GSM 02.90: "Digital cellular telecommunications system (Phase 2+); Unstructured Supplementary Services Data (USSD) - Stage 1". [12] GSM 03.02: "Digital cellular telecommunications system (Phase 2+); Network architecture". [13] GSM 03.11: "Digital cellular telecommunications system (Phase 2+); Technical realization of supplementary services". [14] GSM 03.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 2". [15] GSM 03.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 2". [16] GSM 03.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2". [17] GSM 03.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 2". [18] GSM 03.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 2". [19] GSM 03.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 2". [20] GSM 03.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 2". [21] GSM 03.90: "Digital cellular telecommunications system (Phase 2+); Unstructured supplementary services operation - Stage 2". [22] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". [23] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". [24] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [25] GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3; Supplementary services specification; General aspects". [26] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". 0.2 Abbreviations Abbreviations used in the present document are listed in GSM 01.04. ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.086 V3.0.0 (1999-05) 7 3G TS 24.086 version 3.0.0 1 Advice of Charge (Information) (AoCI) 1.1 Normal operation with successful outcome On every successful request for an applicable telecommunications service, the served Mobile Station (MS) will be provided with charging information. The network sends the Charge Advice Information (CAI) to the MS according to GSM 02.24, GSM 02.86 and GSM 03.86. With this information the MS is able to calculate the units associated with the requested service in real time. In the case where the served mobile is to be charged for multi party calls, separate processes within the MS are used to calculate units appropriate to each call. For unit calculation, each call is treated in the same way as a normal "two-party" call. Any change in the charging rate during a call may be indicated to the MS. 1.1.1 Call re-establishment When the MS detects a radio link failure, the Chargeable Duration (CDUR) shall be suspended. If a call re-establishment procedure is attempted, the MS shall resume the CDUR when: - an MM connection has been successfully completed; and - a TCH has been successfully seized in the appropriate mode. 1.1.2 MS originated call For an MS originated call, charging information is transferred to the MS as shown in figure 1.1. The charging information is acknowledged in a FACILITY message only if the MS supports the AoCI functionality specified in GSM 02.24 and GSM 02.86. AoCI refers to the Advice of Charge (Information) service. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> etc. CONNECT/FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = ForwardChargeAdvice (AoCI, ChargingInformation)) FACILITY/DISCONNECT ------------------------------------------------------------------------------------------------------------------------> Facility (Return result) Figure 1.1: Notification to the served mobile subscriber of the charging information in case of an originated call set up 1.1.3 MS terminated call For an MS terminated call, where required, charging information is transferred to the MS as shown in figure 1.2. The charging information is acknowledged only if the MS supports the AoCI functionality specified in GSM 02.24 and GSM 02.86. ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.086 V3.0.0 (1999-05) 8 3G TS 24.086 version 3.0.0 MS Network CONNECT ------------------------------------------------------------------------------------------------------------------------> FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = ForwardChargeAdvice (AoCI, ChargingInformation)) FACILITY/DISCONNECT ------------------------------------------------------------------------------------------------------------------------> Facility (Return result) Figure 1.2: Notification to the served mobile subscriber of the charging information in case of a terminated call set-up 1.1.4 Change of charging information To inform the MS of a change in charging information the procedure of figure 1.3 is performed. The charging information is acknowledged only if the MS supports the AoCI functionality specified in GSM 02.24 and GSM 02.86. MS Network FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = ForwardChargeAdvice (AoCI, ChargingInformation)) FACILITY/DISCONNECT ------------------------------------------------------------------------------------------------------------------------> Facility (Return result) Figure 1.3: Notification to the served mobile subscriber of a change in the charging information 1.2 Normal operation with unsuccessful outcome No signalling is performed by the network if a MS fails to acknowledge receipt of charging Information. 1.3 Activation, deactivation and invocation Activation, deactivation and invocation of the Advice of Charge (Information) supplementary service are not applicable. 1.4 Interrogation, registration and erasure Interrogation, registration and erasure of the Advice of Charge (Information) supplementary service are not applicable. 2 Advice of Charge (Charging) (AoCC) 2.1 Normal operation with successful outcome On every successful request for an applicable telecommunications service, the served MS will be provided with charging information. The network sends the Charge Advice Information (CAI) to the MS according to GSM 02.24, GSM 02.86 and GSM 03.86. With this information the MS is able to calculate the units associated with the requested service in real time. In the case where the served mobile is to be charged for multi party calls, separate processes within the MS are used to calculate units appropriate to each call. For unit calculation, each call is treated in the same way as a normal "two-party" call. Any change in the charging rate during a call may be indicated to the MS. ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.086 V3.0.0 (1999-05) 9 3G TS 24.086 version 3.0.0 2.1.1 Call re-establishment When the MS detects a radio link failure, the Chargeable Duration (CDUR) shall be suspended. If a call re-establishment procedure is attempted, the MS shall resume the CDUR when: - an MM connection has been successfully completed; and - a TCH has been successfully seized in the appropriate mode. 2.1.2 MS originated call For an MS originated call, charging information is transferred to the MS as shown in figure 2.1. The charging information is acknowledged in a FACILITY message only if the MS supports the AoCC functionality specified in GSM 02.24 and GSM 02.86. AoCC refers to the Advice of Charge (Charging) service. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> etc. CONNECT/FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = ForwardChargeAdvice (AoCC, ChargingInformation)) FACILITY/DISCONNECT ------------------------------------------------------------------------------------------------------------------------> Facility (Return result) Figure 2.1: Notification to the served mobile subscriber of the charging information in case of an originated call set up 2.1.3 MS terminated call For an MS terminated call, where required, charging information is transferred to the MS as shown in figure 2.2. The charging information is acknowledged only if the MS supports the AoCC functionality specified in GSM 02.24 and GSM 02.86. MS Network CONNECT ------------------------------------------------------------------------------------------------------------------------> FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = ForwardChargeAdvice (AoCC, ChargingInformation)) FACILITY/DISCONNECT ------------------------------------------------------------------------------------------------------------------------> Facility (Return result) Figure 2.2: Notification to the served mobile subscriber of the charging information in case of a terminated call set up 2.1.4 Change of charging information To inform the MS of a change in charging information the procedure of figure 2.3 is performed. The charging information is acknowledged only if the MS supports the AoCC functionality specified in GSM 02.24 and GSM 02.86. ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.086 V3.0.0 (1999-05) 10 3G TS 24.086 version 3.0.0 MS Network FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = ForwardChargeAdvice (AoCC, ChargingInformation)) FACILITY/DISCONNECT ------------------------------------------------------------------------------------------------------------------------> Facility (Return result) Figure 2.3: Notification to the served mobile subscriber of a change in the charging information 2.2 Normal operation with unsuccessful outcome If timer T(AoC) (see GSM 03.86) expires before the Charge Advice Information is acknowledged, the network shall release the call. The MS and network shall act in accordance with GSM 04.08 network initiated call clearing procedures (see figure 2.4). MS Network DISCONNECT/RELEASE/RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ ....Cause #69 (Requested facility not implemented).... Figure 2.4: Network release due to unsuccessful operation of Advice of Charge (Charging) service 2.3 Accumulated Call Meter is equal to or greater than ACMmax If the change stored in the Accumulated Call Meter (ACM) is equal to or greater than the maximum value specified by ACMmax, then the MS shall initiate call clearing giving a specific cause value for this situation as indicated in figure 2.5. MS Network DISCONNECT ------------------------------------------------------------------------------------------------------------------------> ....Cause #68 (ACM equal to or greater than ACMmax).... Figure 2.5: Mobile station releases the call due to ACM being equal to or greater than ACMmax 2.4 Activation, deactivation and invocation Activation, deactivation and invocation of the Advice of Charge (Charging) supplementary service are not applicable. 2.5 Interrogation, registration and erasure Interrogation, registration and erasure of the Advice of Charge (Charging) supplementary service are not applicable. ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.086 V3.0.0 (1999-05) 11 3G TS 24.086 version 3.0.0 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 04.86 6.0.0 Transferred to 3GPP CN1 CN#03 24.086 3.0.0 Approved at CN#03 ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) ETSI 12 ETSI ETSI TS 124 086 V3.0.0 (2000-01) (3G TS 24.086 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
|
ea6e250dba6407e8e5eea264daae8279
|
124 085
|
0.1 References
|
.......................................................................................................................................................... 5
|
ea6e250dba6407e8e5eea264daae8279
|
124 085
|
0.2 Abbreviations
|
..................................................................................................................................................... 7
|
ea6e250dba6407e8e5eea264daae8279
|
124 085
|
1 Closed User Group (CUG)
|
......................................................................................................................7
|
ea6e250dba6407e8e5eea264daae8279
|
124 085
|
1.1 Normal operation
|
............................................................................................................................................... 7
|
ea6e250dba6407e8e5eea264daae8279
|
124 085
|
1.1.1 Mobile originated CUG calls
|
....................................................................................................................... 7
|
ea6e250dba6407e8e5eea264daae8279
|
124 085
|
1.1.1.1 Successful operation
|
............................................................................................................................... 7
|
ea6e250dba6407e8e5eea264daae8279
|
124 085
|
1.1.1.2 Unsuccessful operation
|
........................................................................................................................... 8
|
ea6e250dba6407e8e5eea264daae8279
|
124 085
|
1.1.2 Mobile terminated calls
|
................................................................................................................................ 9
|
ea6e250dba6407e8e5eea264daae8279
|
124 085
|
1.2 Activation, deactivation, interrogation, registration and erasure
|
....................................................................... 9 Annex A (normative): CUG rejection cause value mapping ...........................................................10 Annex B: Change history......................................................................................................................11 History..............................................................................................................................................................12 ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.085 V3.0.0 (1999-05) 4 3G TS 24.085 version 3.0.0 Foreword This Technical Specification has been produced by the 3GPP. This TS specifies the procedures used at the radio interface (reference point Um as defined in GSM 04.02) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of Closed User Group (CUG) supplementary services within the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.085 V3.0.0 (1999-05) 5 3G TS 24.085 version 3.0.0
|
ea6e250dba6407e8e5eea264daae8279
|
124 085
|
0 Scope
|
This Technical Specification (TS) for Mobile communications specifies the procedures used at the radio interface (reference point Um as defined in GSM 04.02) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of community of interest supplementary services. The provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and causes no signalling on the radio interface. In GSM 04.10, the general aspects of the specification of supplementary services at the layer 3 radio interface are given. GSM 04.80 specifies the formats coding for the supplementary services. Definitions and descriptions of supplementary services are given in GSM 02.04 and GSM 02.8x and GSM 02.9x-series. GSM 02.85 is related to the community of interest supplementary services. Technical realization of supplementary services is described in technical specifications GSM 03.11 and GSM 03.8x and 03.9x-series. GSM 03.85 is related to the community of interest supplementary services. The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in GSM 04.07 and GSM 04.08. Signalling interworking for supplementary services between GSM 09.02 and GSM 04.08 and between GSM 09.02 and GSM 04.80 is defined in GSM 09.11. The following supplementary services belong to the community of interest supplementary services and are described in this TS: - Closed User Group (CUG) clause 1. 0.1 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [3] GSM 02.81: "Digital cellular telecommunications system (Phase 2+); Line identification Supplementary Services - Stage 1". [4] GSM 02.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) Supplementary Services - Stage 1". [5] GSM 02.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) Supplementary Services - Stage 1". [6] GSM 02.84: "Digital cellular telecommunications system (Phase 2+); Multi Party (MPTY) Supplementary Services - Stage 1". ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.085 V3.0.0 (1999-05) 6 3G TS 24.085 version 3.0.0 [7] GSM 02.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) Supplementary Services - Stage 1". [8] GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) Supplementary Services - Stage 1". [9] GSM 02.87: "Digital cellular telecommunications system. (Phase 2+); User-to-User Signalling (UUS) Service description - Stage 1". [10] GSM 02.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) Supplementary Services - Stage 1". [11] GSM 02.90: "Digital cellular telecommunications system (Phase 2+); Unstructured Supplementary Service Data (USSD) - Stage 1". [12] GSM 03.02: "Digital cellular telecommunications system (Phase 2+); Network architecture". [13] GSM 03.11: "Digital cellular telecommunications system (Phase 2+); Technical realization of supplementary services". [14] GSM 03.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 2". [15] GSM 03.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 2". [16] GSM 03.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2". [17] GSM 03.84: "Digital cellular telecommunications system (Phase 2+); Multi Party (MPTY) supplementary services - Stage 2". [18] GSM 03.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 2". [19] GSM 03.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 2". [20] GSM 03.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 2". [21] GSM 03.90: "Digital cellular telecommunications system (Phase 2+); Unstructured supplementary services operation - Stage 2". [22] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". [23] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". [24] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [25] GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3; Supplementary services specification; General aspects". [26] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". [27] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification". [28] GSM 09.11: "Digital cellular telecommunications system (Phase 2+); Signalling interworking for supplementary services". ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.085 V3.0.0 (1999-05) 7 3G TS 24.085 version 3.0.0 0.2 Abbreviations Abbreviations used in this TS are listed in GSM 01.04. 1 Closed User Group (CUG) 1.1 Normal operation 1.1.1 Mobile originated CUG calls 1.1.1.1 Successful operation CUG calls may be invoked Implicitly or Explicitly by the calling user. In the case of Implicit invocation, no CUG information is provided by the user in the call set-up request and a default attribute of CUG is invoked. Normal call establishment procedures are followed over the radio interface and no CUG signalling is required. In the case of Explicit CUG invocation, CUG information is provided by the user and is included in the SETUP message using the ForwardCUG-Info operation (see figure 1.1). User provided CUG information may consist of any combination of the following parameters: - CUG Index; - Suppress Preferential CUG indicator; - Suppress OA indicator. NOTE: No more than one of each parameter may be included per call attempt. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = ForwardCUG-Info (CUG-Index, SuppressPrefCUG, SuppressOA)) Figure 1.1: Transfer of CUG information during CUG call set-up If the network received a non-zero SS Screening indicator from the calling user's mobile station, the network may optionally indicate to the MS that a CUG has been invoked for a call (see figure 1.2). When a CUG Index is received from the VLR the MSC shall send it immediately to the MS in a FACILITY or CALL PROCEEDING message. If the network did not receive a non-zero SS Screening indicator from the calling user's mobile station, it shall not send this notification. MS Network FACILITY/CALL PROCEEDING <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CUG-Index)) Figure 1.2: Indication of CUG invocation to the calling subscriber by the network ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.085 V3.0.0 (1999-05) 8 3G TS 24.085 version 3.0.0 1.1.1.2 Unsuccessful operation When an attempted CUG call is rejected for CUG related reasons, the mobile station is provided with an indication of the reason for failure. The indication is passed to the calling MS in the first clearing message. The indication may be given in one of two ways: - Diagnostics information in cause value #29 "Facility Rejected"; - A standard call control cause value. Diagnostics are used when the rejection is generated locally (the serving VLR has rejected the call), or if they are provided in a cause value from a remote network node (see figure 1.3). Table 1.1 gives the diagnostics information for each potential local rejection case. A CUG rejection from a remote network node is generally indicated using a standard (CUG related) call control cause value contained in an ISUP clearing message. These cause values are passed to the mobile station in the appropriate radio interface clearing message (see figure 1.4). Table 1.2 gives the cause values in each potential remote rejection case. All CUG related call rejection cases are defined in GSM 03.85. Cause values are defined in GSM 04.08 and diagnostics in GSM 04.80. NOTE: Annex A specifies the mapping of cause values between MAP, ISUP and GSM 04.08 for remotely generated CUG rejections. MS Network DISCONNECT/RELEASE/RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ .....Cause #29 (Facility Rejected (diagnostics))..... Figure 1.3: Indication of local CUG call rejection MS Network DISCONNECT/RELEASE/RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Cause Information Element (Cause Value) Figure 1.4: Indication of remote CUG call rejection Table 1.1: Use of diagnostic values for local CUG call failure indications Reason for rejection See GSM 03.85 Facility Rejected #29 Diagnostic Field (Diagnostics) Outgoing calls barred within the CUG Outgoing calls barred within the CUG Inconsistent access info - No CUG Selected No CUG Selected Unknown CUG Index Unknown CUG Index Inconsistent access info - Index incompatible with requested basic service Index incompatible with requested basic service ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.085 V3.0.0 (1999-05) 9 3G TS 24.085 version 3.0.0 Table 1.2: Use of cause values for remote CUG call failure indications Reason for rejection See GSM 03.85 Cause Information Element (cause value) Called party supplementary service interaction violation Facility Rejected #29 Diagnostic = CUG call failure, unspecified Incompatible Destination (see note) Facility Rejected #29 Diagnostic = CUG call failure, unspecified Incoming calls barred within the CUG Incoming calls barred within the CUG #55 Interlock mismatch User not a member of CUG #87 Requested basic service violates CUG constraints Facility Rejected #29 NOTE: In cases of interworking failures ETSI ISUP V2 clears the call with cause value #29 "Facility Rejected", Diagnostic = "Interlock Code". This is mapped to Facility Rejected with general diagnostic value "CUG call failure, unspecified" since the interlock code has no meaning for a mobile user. 1.1.2 Mobile terminated calls If the network received a non-zero SS Screening indicator from the called user's mobile station, when a CUG call is terminated by a CUG subscriber the Index associated with the invoked CUG may be passed to the mobile station (see figure 1.5). If the network did not receive a non-zero SS Screening indicator from the called user's mobile station, it shall not send this notification. MS Network SETUP <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CUG-Index)) Figure 1.5: Presentation of the CUG Index to a CUG subscriber during reception of a CUG call 1.2 Activation, deactivation, interrogation, registration and erasure Activation, deactivation, interrogation, registration and erasure of the supplementary service closed user group are not applicable. ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.085 V3.0.0 (1999-05) 10 3G TS 24.085 version 3.0.0 Annex A (normative): CUG rejection cause value mapping Table A.1 indicates how MAP, ISUP and GSM 04.08 cause values are mapped to enable a rejection indication to be passed from the remote rejecting node to the calling user. Table A.1: Protocol mapping for CUG call rejection cause values GSM MAP CUG reject cause value CCITT ISUP cause value GSM 04.08 cause value calledPartySupplementary- ServiceInteractionViolation #29 Facility Rejected Diagnostic = IC (see note 1) #29 Facility Rejected Diagnostic = CUG call failure, unspecified incomingCallsBarredWithinCUG #55 I/C calls barred within CUG #55 I/C calls barred within CUG subscriberNotMemberOfCUG #87 User not member of CUG #87 User not member of CUG requestedBasicService- ViolatesCUGConstraints #29 Facility Rejected (see note 2) #29Facility Rejected (no diagnostic) NOTE 1: There is no specific cause value in ISUP for this rejection case. Therefore it is proposed that Cause Value #29 "Facility Rejected" is used with the diagnostic equal to the interlock of the call. This approach has been used in ISUP for interworking problems. NOTE 2: There is no specific cause value in ISUP for this rejection case. It is therefore proposed to use cause value #29 "Facility Rejected" to indicate a general supplementary service failure. ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.085 V3.0.0 (1999-05) 11 3G TS 24.085 version 3.0.0 Annex B: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 04.85 6.0.0 Transferred to 3GPP CN1 CN#03 24.085 3.0.0 Approved at CN#03 ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) ETSI 12 ETSI ETSI TS 124 085 V3.0.0 (2000-01) (3G TS 24.085 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
|
b22801a4d2981f3ac8a4b6b4935e7b16
|
126 094
|
1 Scope
|
........................................................................................................................................................5
|
b22801a4d2981f3ac8a4b6b4935e7b16
|
126 094
|
2 Normative References
|
..............................................................................................................................5
|
b22801a4d2981f3ac8a4b6b4935e7b16
|
126 094
|
3 Technical Description of VAD Option 1
|
.................................................................................................5
|
b22801a4d2981f3ac8a4b6b4935e7b16
|
126 094
|
3.1 Definitions, symbols and abbreviations
|
............................................................................................................. 5
|
b22801a4d2981f3ac8a4b6b4935e7b16
|
126 094
|
3.1.1 Definitions
|
.................................................................................................................................................... 5
|
b22801a4d2981f3ac8a4b6b4935e7b16
|
126 094
|
3.1.2 Symbols
|
........................................................................................................................................................ 5
|
b22801a4d2981f3ac8a4b6b4935e7b16
|
126 094
|
3.1.2.1 Variables
|
................................................................................................................................................. 5
|
b22801a4d2981f3ac8a4b6b4935e7b16
|
126 094
|
3.1.2.2 Constants
|
................................................................................................................................................ 6
|
b22801a4d2981f3ac8a4b6b4935e7b16
|
126 094
|
3.1.2.3 Functions
|
................................................................................................................................................ 7
|
b22801a4d2981f3ac8a4b6b4935e7b16
|
126 094
|
3.1.3 Abbreviations
|
............................................................................................................................................... 8
|
b22801a4d2981f3ac8a4b6b4935e7b16
|
126 094
|
3.2 General
|
............................................................................................................................................................... 8
|
b22801a4d2981f3ac8a4b6b4935e7b16
|
126 094
|
3.3 Functional description
|
........................................................................................................................................ 8
|
b22801a4d2981f3ac8a4b6b4935e7b16
|
126 094
|
3.3.1 Filter bank and computation of sub-band levels
|
........................................................................................... 9
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.