hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
3.7 Cross phase compatibility
|
................................................................................................................................ 27
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
3.7.1 Network only supports protocol version 1 control of SS by the subscriber
|
............................................... 27
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
3.7.2 MS only supports protocol version 1 control of SS by the subscriber
|
....................................................... 27
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
4 Call Forwarding on mobile subscriber Not Reachable (CFNRc)
|
..........................................................27
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
4.1 Normal operation
|
............................................................................................................................................. 27
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
4.1.1 Served mobile subscriber side
|
.................................................................................................................... 27 ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 4 3G TS 24.082 version 3.0.0 4.1.2 Forwarded-to mobile subscriber side ......................................................................................................... 28
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
4.1.3 Calling mobile subscriber side
|
................................................................................................................... 28
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
4.2 Registration
|
...................................................................................................................................................... 29
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
4.2.1 Registration by the served mobile subscriber
|
............................................................................................. 29
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
4.3 Erasure
|
............................................................................................................................................................. 30
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
4.3.1 Erasure by the served mobile subscriber
|
.................................................................................................... 30
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
4.4 Activation
|
........................................................................................................................................................ 31
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
4.5 Deactivation
|
..................................................................................................................................................... 31
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
4.6 Interrogation
|
.................................................................................................................................................... 32
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
4.7 Cross phase compatibility
|
................................................................................................................................ 34
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
4.7.1 Network only supports protocol version 1 control of SS by the subscriber
|
............................................... 34
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
4.7.2 MS only supports protocol version 1 control of SS by the subscriber
|
....................................................... 34 Annex A: Change history......................................................................................................................35 History..............................................................................................................................................................36 ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 5 3G TS 24.082 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, interrogation, and network invocation of the call offering 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 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 6 3G TS 24.082 version 3.0.0
|
df81caf795659f2ed71f5bfcc461b22d
|
124 082
|
0 Scope
|
This European Standard (EN) specifies the procedures used at the radio interface (reference point Um as defined in GSM 04.02) for normal operation, registration, erasure, activation, deactivation, interrogation and network invocation of call offering 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 and GSM 02.8x and GSM 02.9x-series. GSM 02.82 is related specially to call offering supplementary services. Technical realization of supplementary services is described in GSM 03.11 and GSM 03.8x and GSM 03.9x-series. GSM 03.82 is related specially to call offering 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 call offering supplementary services and are described in the present document: - Call forwarding unconditional (CFU) (clause 1); - Call forwarding on mobile subscriber busy (CFB) (clause 2); - Call forwarding on no reply (CFNRy) (clause 3); - Call forwarding on mobile subscriber not reachable (CFNRc) (clause 4). 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.01: "Digital cellular telecommunications system (Phase 2+); Principles of telecommunication services supported by a GSM Public Land Mobile Network (PLMN)". [3] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [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". ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 7 3G TS 24.082 version 3.0.0 [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". [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 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+); 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 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 8 3G TS 24.082 version 3.0.0 0.3 Cross phase compatibility For the following supplementary services, a number of changes exist between the present document and the protocol version 1 specification: - Call forwarding unconditional; - Call forwarding on mobile subscriber busy; - Call forwarding on no reply; - Call forwarding on mobile subscriber not reachable. For these supplementary services, the main body of the present document assumes that all network entities comply with this version of the service. In each case, an additional subclause (subclause x.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. 1 Call Forwarding Unconditional (CFU) 1.1 Normal operation 1.1.1 Served mobile subscriber side When call forwarding unconditional is active, all incoming calls for the specified basic service(s) will be forwarded without being offered to the served mobile subscriber. When CFU is active, the ability of the served mobile subscriber to originate calls is not affected. However, a NotifySS operation containing the SS-Status indicating that CFU is currently active and operative will be sent to the served mobile subscriber each time an outgoing call is made, see figure 1.1. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> e.g. ALERTING <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFU, SS-Status)) Figure 1.1: Notification to the served mobile subscriber that call forwarding is active 1.1.2 Forwarded-to mobile subscriber side The forwarded-to mobile subscriber will receive a NotifySS operation containing the SS-Notification indicating that the incoming call is a forwarded call. When available, the SS-Code of the invoked forwarding service is also included, see figure 1.2. When multiple forwarding occurs the value of the SS-Code shall relate to the last invoked forwarding service. In addition the forwarded-to mobile subscriber will receive the redirecting party BCD number and optionally, a redirecting party subaddress. The redirecting party BCD number information element is made up of a number of information units as indicated in GSM 04.08. In addition to or instead of the redirecting party's digits, the subscriber may be given the following information: - screening indicator; - presentation indicator. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 9 3G TS 24.082 version 3.0.0 Indicator values are given in GSM 04.08. The redirecting party subaddress information element is made up of a number of information units as indicated in GSM 04.08. MS Network SETUP <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFU, SS-Notification)) Redirecting party BCD number (screening indicator, presentation indicator, redirecting party digits), Redirecting party subaddress NOTE: If the specific call forwarding service is not known the common SS-Code for all forwarding SS will be used. Figure 1.2: Notification to the forwarded-to mobile subscriber that the incoming call is a forwarded call 1.1.3 Calling mobile subscriber side As a subscription option, the served mobile subscriber can request that the calling mobile subscriber receives a NotifySS operation containing the SS-Notification indicating that the call has been forwarded. When available, the SS-Code of the invoked forwarding service is also included, see figure 1.3. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFU, SS-Notification)) NOTE: If the specific call forwarding service is not known the common SS-Code for all forwarding SS will be used. Figure 1.3: Notification to the calling mobile subscriber that the call is forwarded 1.2 Registration The following information has to be registered in the network: - the ForwardedToNumber which may be accompanied by a ForwardedToSubAddress; - information as to whether all calls or all calls of a specific basic service should be forwarded. 1.2.1 Registration by the served mobile subscriber A CFU registration request from a mobile user shall include the SS-Code of the forwarding service to be registered and possibly the BasicServiceCode the request applies to. If the BasicServiceCode is not included, the request applies to all basic services. If the registration is successful, the CFU service will be registered and activated. The network will then send a return result indicating acceptance of the request including the ForwardedToNumber and possibly the BasicService (group) Code to which CFU is registered. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases, the result shall not contain a ForwardedToSubAddress. The result may also contain an SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS-Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS-Status in the result is optional. If the SS-Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS-Status parameter if one is received. See figure 1.4. Note that the use of SS-Status is to provide backwards compatibility with phase 1. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 10 3G TS 24.082 version 3.0.0 If the system cannot accept a registration request, a corresponding error indication is returned to the served mobile subscriber that CFU registration was not successful. Error values are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = RegisterSS (CFU, BasicServiceCode, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = RegisterSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If BasicServiceCode is not included it applies to all basic services. The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. The SS-Status may not be included in all cases, see text. Figure 1.4: Registration of call forwarding unconditional When registering call forwarding, the SS-Code may indicate the code for "all forwarding SS". In this case, if the subscriber has CFU provisioned, the return result shall contain the information for CFU. If the subscriber does not have CFU provisioned, the return result shall contain the information for any conditional call forwarding services which the subscriber has provisioned. 1.3 Erasure A previous registration can be erased in one of three ways: - the subscriber can specifically erase a previous registration with an appropriate control procedure; - the subscriber can register information for CFU for a specific basic service group to another directory number, thus causing the previous registration of CFU to be overridden; - all information is erased as a result of withdrawal of the supplementary service (administrative handling). 1.3.1 Erasure by the served mobile subscriber If the erasure is successful, the CFU service will be erased (and automatically 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 BasicService (group) Code for which CFU was erased. The result may also contain an SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS-Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS-Status in the result is optional. If the SS-Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS-Status parameter if one is received. See figure 1.5. Note that the use of SS-Status is to provide backwards compatibility with GSM Phase 1. - If the request did not include a BasicServiceCode, and the erasure 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 network cannot accept the erasure request, the status of CFU in the network remains unchanged. An error indication will then be returned to the served mobile subscriber that erasure of CFU was unsuccessful. Error values are specified in GSM 04.80. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 11 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = EraseSS (CFU, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = EraseSS (BasicServiceCode, SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If BasicServiceCode is not included it applies to all basic services. The SS-Code may also indicate the code for "all forwarding SS". The SS-Status may not be included in all cases, see text. Figure 1.5: Erasure of call forwarding unconditional 1.4 Activation An explicit CFU activation request from a mobile user shall contain the supplementary service to be activated and possibly the basic service group the request applies to. If a basic service group is not included in the activation request the request applies to all basic services against which a CFU forwarded-to number is registered. The user shall receive appropriate notification of acceptance, rejection or partial acceptance of the CFU activation request, see figure 1.6. Error values (which are used in the two latter situations) are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = ActivateSS (CFU, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = ActivateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may also indicate the code for "all forwarding SS", being handled as for registration (see subclause 1.2.1). Figure 1.6: Activation of call forwarding unconditional ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 12 3G TS 24.082 version 3.0.0 1.5 Deactivation An explicit CFU deactivation request shall contain the supplementary service to be deactivated and possibly the basic service group the request applies to. If a basic service group is not included in the deactivation request the request applies to all basic services against which CFU is activated. The user shall receive appropriate notification of acceptance or rejection of the CFU deactivation request, see figure 1.7. Error values to be used in the latter situation are specified in GSM 04.80. Deactivation shall not lead to erasure of the information registered in the network. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = DeactivateSS (CFU, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = DeactivateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may also indicate the code for "all forwarding SS". Figure 1.7: Deactivation of call forwarding unconditional 1.6 Interrogation Data request The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return the following information: - in response to a general data request (i.e. not including a BasicServiceCode) the served mobile subscriber should be given the following data for each basic service group to which CFU is registered: - the SS-Status indicating whether the supplementary service is "not active", "active and operative" or "active and quiescent"; - the associated ForwardedToNumber which shall not be accompanied by a ForwardedToSubAddress, see figure 1.8. If CFU is not registered for any basic service groups, only the SS-Status parameter indicating "not registered" is returned. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 13 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CFU)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The ForwardedToNumber shall not be accompanied by a ForwardedToSubAddress. The return result may consist of a list of parameters, each relating to a specific basic service group. Figure 1.8: Interrogation of active call forwarding unconditional for all basic services - in response to a specific request concerning one particular basic service group, the served mobile subscriber should be informed whether or not CFU is registered, including information on whether or not it is active and operative or active and quiescent for that basic service group. If CFU is registered, the associated ForwardedToNumber shall be given, see figure 1.9. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. If CFU is not registered for the interrogated basic service group, only the SS-Status parameter indicating "not registered" is returned. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CFU, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. Figure 1.9: Interrogation of active call forwarding unconditional for one particular basic service The values "all forwarding SS" and "all conditional forwarding SS" shall not be sent over the air interface by the MS in an interrogation. If an interrogation is received containing one of these codes the network shall send a return error component. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 14 3G TS 24.082 version 3.0.0 1.7 Cross phase compatibility 1.7.1 Network only supports protocol version 1 control of SS by the subscriber A CFU registration request which contains a ForwardedToSubaddress shall be rejected by the network if any network element involved is of protocol version 1. Note that a CFU activation or deactivation request will be rejected by the network is any network element involved is of protocol version 1. 1.7.2 MS only supports protocol version 1 control of SS by the subscriber In response to a CFU interrogation request, where the SS Version Indicator is not received from the MS, the network shall only return data for basic service groups to which CFU is activated and operative. Data shall not be returned for basic service groups to which CFU is deactivated. This means that the subscriber is not always aware of the true state of the service. In response to a CFU registration or erasure request, where the SS Version Indicator is not received from the MS, the network shall always include the SS-Status parameter. 2 Call Forwarding on mobile subscriber Busy (CFB) 2.1 Normal operation 2.1.1 Served mobile subscriber side When call forwarding on mobile subscriber busy is active, the following actions are taken by the network: - If the mobile is Network Determined User Busy (NDUB as defined in GSM 02.01), incoming calls for the specified basic service(s) will be forwarded without being offered to the served mobile subscriber. - If the mobile is not NDUB, the incoming call is offered (as a normal or waiting call) to the served mobile subscriber. - if the call is subsequently released by the mobile with the first clearing message containing the cause = "User Busy" before the CONNECT message is received, it will be forwarded by the network, see figure 2.0; - if any other release causes are given, the call will be released; - if one of the call control timers (T303 or T310) elapse, the call will be released. MS Network SETUP <------------------------------------------------------------------------------------------------------------------------ ....Transaction Identifier (A-B).... RELEASE COMPLETE/RELEASE/DISCONNECT ------------------------------------------------------------------------------------------------------------------------> ....Transaction Identifier (A-B).... ....Cause # 17 (User Busy).... Figure 2.0: Call which is offered to the served mobile subscriber being released. The network will invoke call forwarding on mobile subscriber busy in this case, if CFB is active for the requested basic service ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 15 3G TS 24.082 version 3.0.0 When an incoming call is forwarded on mobile subscriber busy due to NDUB the served mobile subscriber can, as a subscription option, receive a NotifySS operation containing the SS-Notification indicating that a call has been forwarded, see figure 2.1. He will not be able to answer the incoming call. The transaction identifier employed shall correspond to any call B is having. MS Network FACILITY (TI=B-X) <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFB, SS-Notification)) NOTE: X is any party with which B has a call. Figure 2.1: Notification to the served mobile subscriber that a call is forwarded on mobile subscriber busy When CFB is active, the ability of the served mobile subscriber to originate calls is not affected. However, a NotifySS operation containing the SS-Status indicating that a conditional call forwarding supplementary service is currently active and operative will be sent to the served mobile subscriber each time an outgoing call is made, see figure 2.2. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> e.g. ALERTING <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (SS-Code, SS-Status)) NOTE: The SS-Code will be the common SS-Code for all conditional call forwarding services. Figure 2.2: Notification to the served mobile subscriber that a conditional call forwarding service is active 2.1.2 Forwarded-to mobile subscriber side The forwarded-to mobile subscriber will receive a NotifySS operation containing the SS-Notification indicating that the incoming call is a forwarded call. When available, the SS-Code of the invoked forwarding service is also included, see figure 2.3. When multiple forwarding occurs the value of the SS-Code shall relate to the last invoked forwarding service. In addition the forwarded-to mobile subscriber will receive the redirecting party BCD number and optionally, a redirecting party subaddress. The redirecting party BCD number information element is made up of a number of information units as indicated in GSM 04.08. In addition to or instead of the redirecting party's digits, the subscriber may be given the following information: - screening indicator; - presentation indicator. Indicator values are given in GSM 04.08. The redirecting party subaddress information element is made up of a number of information units as indicated in GSM 04.08. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 16 3G TS 24.082 version 3.0.0 MS Network SETUP <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFB, SS-Notification)) Redirecting party BCD number (screening indicator, presentation indicator, redirecting party digits), Redirecting party subaddress NOTE: If the specific call forwarding service is not known the common SS-Code for all forwarding SS will be used. Figure 2.3: Notification to the forwarded-to mobile subscriber that the incoming call is a forwarded call 2.1.3 Calling mobile subscriber side As a subscription option, the served mobile subscriber can request that the calling mobile subscriber receives a NotifySS operation containing the SS-Notification indicating that the call has been forwarded. When available, the SS-Code of the invoked forwarding service is also included, see figure 2.4. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFB, SS-Notification)) NOTE: If the specific call forwarding service is not known the common SS-Code for all forwarding SS will be used. Figure 2.4: Notification to the calling mobile subscriber that the call is forwarded 2.2 Registration The following information has to be registered in the network: - the ForwardedToNumber which may be accompanied by a ForwardedToSubAddress; - information as to whether all calls or all calls of a specific basic service should be forwarded. 2.2.1 Registration by the served mobile subscriber A CFB registration request from a mobile user shall include the SS-Code of the forwarding service to be registered, and possibly the BasicServiceCode the request applies to. If the BasicServiceCode is not included, the request applies to all basic services. If the registration is successful, the CFB service will be registered and activated. The network will then send a return result indicating acceptance of the request, including the ForwardedToNumber and possibly the BasicService (group) Code to which CFB is registered. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. The result may also contain an SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS-Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS-Status in the result is optional. If the SS-Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS-Status parameter if one is received. See figure 2.5. Note that the use of SS-Status is to provide backwards compatibility with phase 1. If the system cannot accept a registration request, a corresponding error indication is returned to the served mobile subscriber that CFB registration was not successful. Error values are specified in GSM 04.80. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 17 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = RegisterSS (CFB, BasicServiceCode, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = RegisterSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If BasicServiceCode is not included it applies to all basic services. The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. The SS-Status may not be included in all cases, see text. Figure 2.5: Registration of call forwarding on mobile subscriber busy The SS-Code may indicate the code for "all forwarding SS", as specified in subclause 1.2.1. The SS-Code may indicate the code for "all conditional forwarding SS". In this case the return result shall contain the information for any conditional call forwarding services which the subscriber has provisioned. 2.3 Erasure A previous registration can be erased in one of three ways: - the subscriber can specifically erase a previous registration with an appropriate control procedure; - the subscriber can register information for CFB for the specific basic service to another directory number, thus causing the previous registration of CFB to be overridden; - all information is erased as a result of withdrawal of the supplementary service (administrative handling). 2.3.1 Erasure by the served mobile subscriber A CFB erasure request from a mobile subscriber may include the BasicServiceCode. If this is not the case, the erasure applies to all basic services. If the erasure is successful, the CFB service will be erased (and automatically 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 BasicService (group) Code for which CFB was erased. The result may also contain an SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS-Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS-Status in the result is optional. If the SS-Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS-Status parameter if one is received. See figure 2.6. Note that the use of SS-Status is to provide backwards compatibility with phase 1. - If the request did not include a BasicServiceCode, and the erasure 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 network cannot accept the erasure request, the status of CFB in the network remains unchanged. An error indication will then be returned to the served mobile subscriber that erasure of CFB was unsuccessful. Error values are specified in GSM 04.80. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 18 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = EraseSS (CFB, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = EraseSS (BasicServiceCode, SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If BasicServiceCode is not included it applies to all basic services. The SS-Code may also indicate the code for "all conditional forwarding SS" or the code for "all forwarding SS". The SS-Status may not be included in all cases, see text. Figure 2.6: Erasure of call forwarding on mobile subscriber busy 2.4 Activation An explicit CFB activation request shall contain the SS-Code of the supplementary service to be activated and possibly the BasicServiceCode the request applies to. If a BasicServiceCode is not included in the activation request the request applies to all basic services against which CFB forwarded-to number is registered. The user shall receive appropriate notification of acceptance, rejection or partial acceptance of the CFB activation request, see figure 2.7. Error values to be used in the two latter situations are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = ActivateSS (CFB, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = ActivateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may also indicate the code "all conditional forwarding SS" group, as specified in subclause 2.2.1, or the "all forwarding SS" group, as specified in subclause 1.2.1. Figure 2.7: Activation of call forwarding on mobile subscriber busy 2.5 Deactivation An explicit CFB deactivation request shall contain the SS-Code of the supplementary service to be deactivated and possibly the BasicServiceCode the request applies to. If a BasicServiceCode is not included in the deactivation request the request applies to all basic services against which CFB is activated. The user shall receive appropriate notification of acceptance or rejection of the CFB deactivation request, see figure 2.8. Error values to be used in the latter situation are specified in GSM 04.80. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 19 3G TS 24.082 version 3.0.0 Deactivation shall not lead to erasure of the information registered in the network. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = DeactivateSS (CFB, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = DeactivateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may also indicate the "all conditional forwarding SS" group or the "all forwarding SS" group. Figure 2.8: Deactivation of call forwarding on mobile subscriber busy 2.6 Interrogation Data request The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return the following information: - in response to a general data request (i.e. not including a BasicServiceCode) the served mobile subscriber should be given the following data for each basic service group to which CFB is registered: - the SS-Status indicating whether the supplementary service is "not active", "active and operative" or "active and quiescent"; - the associated ForwardedToNumber which shall not be accompanied by a ForwardedToSubAddress, see figure 2.9. If CFB is not registered for any basic service groups, only the SS-Status parameter indicating "not registered" is returned. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 20 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CFB)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The ForwardedToNumber shall not be accompanied by a ForwardedToSubAddress. The return result may consist of a list of parameters, each relating to a specific basic service group. Figure 2.9: Interrogation of active call forwarding on mobile subscriber busy for all basic services - in response to a specific request (i.e. containing one particular BasicService (group) Code, the served mobile subscriber should receive the SS-Status parameter, indicating whether or not CFB is registered, including information as to whether or not it is active and operative or active and quiescent for that basic service group. If CFB is registered, the associated ForwardedToNumber shall be given, see figure 2.10. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. If CFB is not registered for the interrogated BasicService (group) code, only the SS-Status parameter indicating "not registered" is returned. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CFB, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. Figure 2.10: Interrogation of active call forwarding on mobile subscriber busy for one particular basic service The values "all forwarding SS" and "all conditional forwarding SS" shall not be sent over the air interface by the MS in an interrogation. If an interrogation is received containing one of these codes the network shall send a return error component. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 21 3G TS 24.082 version 3.0.0 2.7 Cross phase compatibility 2.7.1 Network only supports protocol version 1 control of SS by the subscriber A CFB registration request which contains a ForwardedToSubaddress shall be rejected by the network if any network element involved is of protocol version 1. Note that a CFB activation or deactivation request will be rejected by the network is any network element involved is of protocol version 1. 2.7.2 MS only supports protocol version 1 control of SS by the subscriber In response to a CFB interrogation request, where the SS Version Indicator is not received from the MS, the network shall only return data for basic service groups to which CFB is activated and operative. Data shall not be returned for basic service groups to which CFB is deactivated. This means that the subscriber is not always aware of the true state of the service. In response to a CFB registration or erasure request, where the SS Version Indicator is not received from the MS, the network shall always include the SS-Status parameter. 3 Call Forwarding on No Reply (CFNRy) 3.1 Normal operation 3.1.1 Served mobile subscriber side When call forwarding on no reply is active, all incoming calls for the specified basic service(s) that are not answered within the period defined by the no reply condition timer, will be forwarded. When an incoming call is forwarded on no reply the served mobile subscriber can, as a subscription option, receive a NotifySS operation containing the SS-Notification indicating that a call has been forwarded, see figure 3.1. MS Network FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFNRy, SS-Notification)) Figure 3.1: Notification to the served mobile subscriber that the call is forwarded on no reply When CFNRy is active, the ability of the served mobile subscriber to originate calls is not affected. However, a NotifySS operation containing the SS-Status indicating that a conditional call forwarding supplementary service is currently active and operative will be sent to the served mobile subscriber each time an outgoing call is made, see figure 3.2. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> e.g. ALERTING <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (SS-Code, SS-Status)) NOTE: The SS-Code will be the common SS-Code for all conditional call forwarding services. Figure 3.2: Notification to the served mobile subscriber that a conditional call forwarding service is active ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 22 3G TS 24.082 version 3.0.0 3.1.2 Forwarded-to mobile subscriber side The forwarded-to mobile subscriber will receive a NotifySS operation containing the SS-Notification indicating that the incoming call is a forwarded call. When available, the SS-Code of the invoked forwarding service is also included, see figure 3.3. When multiple forwarding occurs the value of the SS-Code shall relate to the last invoked forwarding service. In addition the forwarded-to mobile subscriber will receive the redirecting party BCD number and optionally, a redirecting party subaddress. The redirecting party BCD number information element is made up of a number of information units as indicated in GSM 04.08. In addition to or instead of the redirecting party's digits, the subscriber may be given the following information: - screening indicator; - presentation indicator. Indicator values are given in GSM 04.08. The redirecting party subaddress information element is made up of a number of information units as indicated in GSM 04.08. MS Network SETUP <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFNRy, SS-Notification)) Redirecting party BCD number (screening indicator, presentation indicator, redirecting party digits), Redirecting party subaddress NOTE: If the specific call forwarding service is not known the common SS-Code for "all forwarding SS" will be used. Figure 3.3: Notification to the forwarded-to mobile subscriber that the incoming call is a forwarded call 3.1.3 Calling mobile subscriber side As a subscription option, the served mobile subscriber can request that the calling mobile subscriber receives a NotifySS operation containing the SS-Notification indicating that the call has been forwarded. When available, the SS-Code of the invoked forwarding service is also included, see figure 3.4. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFNRy, SS-Notification)) NOTE: If the specific call forwarding service is not known the common SS-Code for "all forwarding SS" will be used. Figure 3.4: Notification to the calling mobile subscriber that the call is forwarded ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 23 3G TS 24.082 version 3.0.0 3.2 Registration The following information has to be registered in the network: - the ForwardedToNumber, which may be accompanied by a ForwardedToSubAddress; - information as to whether all calls or all calls of a specific basic service should be forwarded; - the duration of the no reply condition timer. 3.2.1 Registration by the served mobile subscriber A CFNRy registration request from a mobile user shall include the SS-Code of the forwarding service to be registered and possibly the applicable BasicServiceCode and NoReplyConditionTime. If the BasicServiceCode is not included, the request applies to all basic services. If the NoReplyConditionTime is not included, the previous value set by the mobile user or network operator applies. If the registration is successful, the CFNRy service will be registered and activated. The network will then send a return result indicating acceptance of the request, including the ForwardedToNumber and possibly the applicable BasicService (group) code and NoReplyConditionTime. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. The result may also contain an SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS-Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS-Status in the result is optional. If the SS-Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS-Status parameter if one is received. See figure 3.5. Note that the use of SS-Status is to provide backwards compatibility with phase 1. If the system cannot accept a registration request, a corresponding error indication is returned to the served mobile subscriber that CFNRy registration was not successful. Error values are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = RegisterSS (CFNRy, BasicServiceCode, ForwardedToNumber, ForwardedToSubAddress, NoReplyConditionTime)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = RegisterSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress, NoReplyConditionTime)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If BasicServiceCode is not included it applies to all basic services. If NoReplyConditionTime is not included the value previously registered in the network applies. The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. The SS-Code may also indicate the code for "all conditional forwarding SS", as specified in subclause 2.2.1, or the code for "all forwarding SS", as specified in subclause 1.2.1. The SS-Status may not be included in all cases, see text. Figure 3.5: Registration of call forwarding on no reply ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 24 3G TS 24.082 version 3.0.0 3.3 Erasure A previous registration can be erased in one of three ways: - the subscriber can specifically erase a previous registration with an appropriate control procedure; - the subscriber can register information for CFNRy for the specific basic service to another directory number, thus causing the previous registration of CFNRy to be overridden; - all information is erased as a result of withdrawal of the supplementary service (administrative handling). 3.3.1 Erasure by the served mobile subscriber A CFNRy erasure request from a mobile subscriber may include the BasicServiceCode. If this is not the case, the erasure applies to all basic services. If the erasure is successful, the CFNRy service will be erased (and automatically 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 BasicService (group) Code for which CFNRy was erased. The result may also contain an SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS-Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS-Status in the result is optional. If the SS-Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS-Status parameter if one is received. See figure 3.6. Note that the use of SS-Status is to provide backwards compatibility with phase 1. - If the request did not include a BasicServiceCode, and the erasure 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 network cannot accept the erasure request, the status of CFNRy in the network remains unchanged. An error indication will then be returned to the served mobile subscriber that erasure of CFNRy was unsuccessful. Error values are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = EraseSS (CFNRy, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = EraseSS (BasicServiceCode, SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If BasicServiceCode is not included it applies to all basic services. The SS-Code may also indicate the code for "all conditional forwarding SS" or the code for "all forwarding SS". The SS-Status may not be included in all cases, see text. Figure 3.6: Erasure of call forwarding on no reply ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 25 3G TS 24.082 version 3.0.0 3.4 Activation An explicit CFNRy activation request shall contain the SS-Code of the supplementary service to be activated and possibly the BasicServiceCode the request applies to. If a BasicServiceCode is not included in the activation request the request applies to all basic services against which a CFNRy forwarded-to number is registered. The user shall receive appropriate notification of acceptance, rejection or partial acceptance of the CFNRy activation request, see figure 3.7. Error values (which are used in the two latter situations) are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = ActivateSS (CFNRy, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = ActivateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may also indicate the code "all conditional forwarding SS" group, as specified in subclause 2.2.1, or the "all forwarding SS" group, as specified in subclause 1.2.1. Figure 3.7: Activation of call forwarding on no reply 3.5 Deactivation An explicit CFNRy deactivation request shall contain the SS-Code of the supplementary service to be deactivated and possibly the BasicServiceCode the request applies to. If a BasicServiceCode is not included in the deactivation request the request applies to all basic services against which CFNRy is activated. The user shall receive appropriate notification of acceptance or rejection of the CFNRy deactivation request, see figure 3.8. Error values to be used in the latter situation are specified in GSM 04.80. Deactivation shall not lead to erasure of the information registered in the network. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = DeactivateSS (CFNRy, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = DeactivateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may also indicate "all conditional forwarding SS" group or the "all forwarding SS" group. Figure 3.8: Deactivation of call forwarding on no reply ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 26 3G TS 24.082 version 3.0.0 3.6 Interrogation Data request The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return the following information: - in response to a general data request (i.e. not including a BasicServiceCode) the served mobile subscriber should be given the following data for each basic service group to which CFNRy is registered: - the SS-Status indicating whether the supplementary service is "not active", "active and operative" or "active and quiescent"; - the associated ForwardedToNumber which shall not be accompanied by a ForwardedToSubAddress; - the duration of the no reply condition timer, see figure 3.9. If CFNRy is not registered for any basic service groups, only the SS-Status parameter indicating "not registered" is returned. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CFNRy)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber, NoReplyConditionTime)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The ForwardedToNumber shall not be accompanied by a ForwardedToSubAddress. The return result may consist of a list of parameters, each relating to a specific basis service group. Figure 3.9: Interrogation of active call forwarding on no reply for all basic services - in response to a specific request (i.e. containing one particular BasicService (group) code, the served mobile subscriber should receive the SS-Status parameter, indicating whether or not CFNRy is registered, including information as to whether or not it is active and operative or active and quiescent for that basic service group. If CFNRy is registered for the interrogated basic service group, the associated ForwardedToNumber and the duration of the no reply condition timer shall be given, see figure 3.10. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. If CFNRy is not registered for the interrogated BasicService (group) code, only the SS-Status parameter indicating "not registered" is returned. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 27 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CFNRy, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress, NoReplyConditionTime)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. Figure 3.10: Interrogation of active call forwarding on no reply for one particular basic service The values "all forwarding SS" and "all conditional forwarding SS" shall not be sent over the air interface by the MS in an interrogation. If an interrogation is received containing one of these codes the network shall send a return error component. 3.7 Cross phase compatibility 3.7.1 Network only supports protocol version 1 control of SS by the subscriber A CFNRy registration request which contains a ForwardedToSubaddress shall be rejected by the network if any network element involved is of protocol version 1. Note that a CFNRy activation or deactivation request will be rejected by the network is any network element involved is of protocol version 1. 3.7.2 MS only supports protocol version 1 control of SS by the subscriber In response to a CFNRy interrogation request, where the SS Version Indicator is not received from the MS, the network shall only return data for basic service groups to which CFNRy is activated and operative. Data shall not be returned for basic service groups to which CFNRy is deactivated. This means that the subscriber is not always aware of the true state of the service. In response to a CFNRy registration or erasure request, where the SS Version Indicator is not received from the MS, the network shall always include the SS-Status parameter. 4 Call Forwarding on mobile subscriber Not Reachable (CFNRc) 4.1 Normal operation 4.1.1 Served mobile subscriber side When call forwarding on mobile subscriber not reachable, all incoming calls for the specified basic service(s) when the mobile subscriber is not reachable, will be forwarded without being offered to the served mobile subscriber. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 28 3G TS 24.082 version 3.0.0 When CFNRc is active, the ability of the served mobile subscriber to originate calls is not affected. However, a NotifySS operation containing the SS-Status indicating that a conditional call forwarding service is currently active and operative will be sent to the served mobile subscriber each time an outgoing call is made, see figure 4.1. MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> e.g. ALERTING <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (SS-Code, SS-Status)) NOTE: The SS-Code will be the common SS-Code for all conditional call forwarding services. Figure 4.1: Notification to the served mobile subscriber that a conditional call forwarding service is active 4.1.2 Forwarded-to mobile subscriber side The forwarded-to mobile subscriber will receive a NotifySS operation containing the SS-Notification indicating that the incoming call is a forwarded call. When available, the SS-Code of the invoked forwarding service is also included, see figure 4.2. When multiple forwarding occurs the value of the SS-Code shall relate to the last invoked forwarding service. In addition the forwarded-to mobile subscriber will receive the redirecting party BCD number and optionally, a redirecting party subaddress. The redirecting party BCD number information element is made up of a number of information units as indicated in GSM 04.08. In addition to or instead of the redirecting party's digits, the subscriber may be given the following information: - screening indicator; - presentation indicator. Indicator values are given in GSM 04.08. The redirecting party subaddress information element is made up of a number of information units as indicated in GSM 04.08. MS Network SETUP <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFNRc, SS-Notification)) Redirecting party BCD number (screening indicator, presentation indicator, redirecting party digits), Redirecting party subaddress NOTE: If the specific call forwarding service is not known the common SS-Code for call forwarding SS will be used. Figure 4.2: Notification to the forwarded-to mobile subscriber that the incoming call is a forwarded call 4.1.3 Calling mobile subscriber side As a subscription option, the served mobile subscriber can request that the calling mobile subscriber receives a NotifySS operation containing the SS-Notification indicating that the call has been forwarded. When available, the SS-Code of the invoked forwarding service is also included, see figure 4.3. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 29 3G TS 24.082 version 3.0.0 MS Network SETUP ------------------------------------------------------------------------------------------------------------------------> FACILITY <------------------------------------------------------------------------------------------------------------------------ Facility (Invoke = NotifySS (CFNRc, SS-Notification)) NOTE: If the specific call forwarding service is not known the common SS-Code for all forwarding SS will be used. Figure 4.3: Notification to the calling mobile subscriber that the call is forwarded 4.2 Registration The following information has to be registered in the network: - the ForwardedToNumber which may be accompanied by a ForwardedToSubAddress; - information as to whether all calls or all calls of a specific basic service should be forwarded. 4.2.1 Registration by the served mobile subscriber A CFNRc registration request from a mobile user shall include the SS-Code of the forwarding service to be registered and possibly the BasicServiceCode the request applies to. If the BasicServiceCode is not included, the request applies to all basic services. If the registration is successful, the CFNRc will be registered and activated. The network will then send a return result indicating of acceptance of the request, including the ForwardedToNumber and possibly the applicable BasicService (group) code to which CFNRc is registered. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. The result may also contain an SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS-Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS-Status in the result is optional. If the SS-Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS-Status parameter if one is received. See figure 4.4. Note that the use of SS-Status is to provide backwards compatibility with phase 1. If the registration is successful, the CFNRc will be registered and activated. The network will then send a return result indicating of acceptance of the request, including the ForwardedToNumber to which CFNRc is registered. If no BasicServiceCode was included in the registration request it is not included in the return result either, see figure 4.4. If the system cannot accept a registration request, a corresponding error indication is returned to the served mobile subscriber that CFNRc registration was not successful. Error values are specified in GSM 04.80. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 30 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = RegisterSS (CFNRc, BasicServiceCode, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = RegisterSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If BasicServiceCode is not included it applies to all basic services. The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. The SS-Code may also indicate the code for "all conditional forwarding SS", as specified in subclause 2.2.1, or the code for "all forwarding SS", as specified in subclause 1.2.1. The SS-Status may not be included in all cases, see text. Figure 4.4: Registration of call forwarding on mobile subscriber not reachable 4.3 Erasure A previous registration can be erased in one of three ways: - the subscriber can specifically erase a previous registration with an appropriate control procedure; - the subscriber can register information for CFNRc for the specific basic service to another directory number, thus causing the previous registration of CFNRc to be overridden; - all information is erased as a result of withdrawal of the supplementary service (administrative handling). 4.3.1 Erasure by the served mobile subscriber A CFNRc erasure request from a mobile subscriber may include the BasicServiceCode. If this is not the case, the erasure applies to all basic services. If the erasure is successful, the CFNRc service will be erased (and automatically 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 BasicService (group) Code for which CFNRc was erased. The result may also contain an SS-Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS-Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS-Status in the result is optional. If the SS-Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS-Status parameter if one is received. See figure 4.5. Note that the use of SS-Status is to provide backwards compatibility with phase 1. - If the request did not include a BasicServiceCode, and the erasure 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 network cannot accept the erasure request, the status of CFNRc in the network remains unchanged. An error indication will then be returned to the served mobile subscriber that erasure of CFNRc was unsuccessful. Error values are specified in GSM 04.80. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 31 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = EraseSS (CFNRc, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = EraseSS (BasicServiceCode, SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: If BasicServiceCode is not included it applies to all basic services. The SS-Code may also indicate the code for "all conditional forwarding SS" or the code for "all forwarding SS". The SS-Status may not be included in all cases, see text. Figure 4.5: Erasure of call forwarding on mobile subscriber not reachable 4.4 Activation An explicit CFNRc activation request shall contain the SS-Code of the supplementary service to be activated and possibly the BasicServiceCode the request applies to. If a BasicServiceCode is not included in the activation request the request applies to all basic services against which a CFNRc forwarded-to number is registered. The user shall receive appropriate notification of acceptance, rejection or partial acceptance of the CFNRc activation request, see figure 4.6. Error values (which are used in the two latter situations) are specified in GSM 04.80. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = ActivateSS (CFNRc, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = ActivateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may also indicate the code "all conditional forwarding SS" group, as specified in subclause 2.2.1, or the "all forwarding SS" group, as specified in subclause 1.2.1. Figure 4.6: Activation of call forwarding on mobile subscriber not reachable 4.5 Deactivation An explicit CFNRc deactivation request shall contain the SS-Code of the supplementary service to be deactivated and possibly the BasicServiceCode the request applies to. If a BasicServiceCode is not included in the deactivation request the request applies to all basic services against which CFNRc is activated. The user shall receive appropriate notification of acceptance or rejection of the CFNRc deactivation request, see figure 4.7. Error values to be used in the latter situation are specified in GSM 04.80. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 32 3G TS 24.082 version 3.0.0 Deactivation shall not lead to erasure of the information registered in the network. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = DeactivateSS (CFNRc, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = DeactivateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The SS-Code may also indicate the "all conditional forwarding SS" group or the "all forwarding SS" group. Figure 4.7: Deactivation of call forwarding on mobile subscriber not reachable 4.6 Interrogation Data request The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return the following information: - in response to a general data request (i.e. not including a BasicServiceCode) the served mobile subscriber should be given the following data for each basic service group to which CFNRc is registered: - the SS-Status indicating whether the supplementary service is "not active", "active and operative" or "active and quiescent"; - the associated ForwardedToNumber which shall not be accompanied by a ForwardedToSubAddress, see figure 4.8. If CFNRc is not registered for any basic service groups, only the SS-Status parameter indicating "not registered" is returned. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 33 3G TS 24.082 version 3.0.0 MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CFNRc)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The ForwardedToNumber shall not be accompanied by a ForwardedToSubAddress. The return result may consist of a list of parameters, each relating to a specific basic service group. Figure 4.8: Interrogation of call forwarding on mobile subscriber not reachable active for all basic services - in response to a specific request (i.e. containing one particular BasicService (group) code), the served mobile subscriber should receive the SS-Status parameter, indicating whether or not CFNRc is registered, including information as to whether or not it is active and operative or active and quiescent for that basic service group. If CFNRc is registered, the associated ForwardedToNumber shall be given, see figure 4.9. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. If CFNRc is not registered for the interrogated BasicService (group) code, only the SS-Status parameter indicating "not registered" is returned. MS Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CFNRc, BasicServiceCode)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) NOTE: The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. Figure 4.9: Interrogation of active call forwarding on mobile subscriber not reachable for one particular basic service The values "all forwarding SS" and "all conditional forwarding SS" shall not be sent over the air interface by the MS in an interrogation. If an interrogation is received containing one of these codes the network shall send a return error component. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 34 3G TS 24.082 version 3.0.0 4.7 Cross phase compatibility 4.7.1 Network only supports protocol version 1 control of SS by the subscriber A CFNRc registration request which contains a ForwardedToSubaddress shall be rejected by the network if any network element involved is of protocol version 1. Note that a CFNRc activation or deactivation request will be rejected by the network is any network element involved is of protocol version 1. 4.7.2 MS only supports protocol version 1 control of SS by the subscriber In response to a CFNRc interrogation request, where the SS Version Indicator is not received from the MS, the network shall only return data for basic service groups to which CFNRc is activated and operative. Data shall not be returned for basic service groups to which CFNRc is deactivated. This means that the subscriber is not always aware of the true state of the service. In response to a CFNRc registration or erasure request, where the SS Version Indicator is not received from the MS, the network shall always include the SS-Status parameter. ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 24.082 V3.0.0 (1999-05) 35 3G TS 24.082 version 3.0.0 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 04.82 7.0.0 Transferred to 3GPP CN1 CN#03 24.082 3.0.0 Approved at CN#03 ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) ETSI 36 ETSI ETSI TS 124 082 V3.0.0 (2000-01) (3G TS 24.082 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
0 Scope
|
........................................................................................................................................................5
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
0.1 References
|
.......................................................................................................................................................... 5
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
0.2 Abbreviations
|
..................................................................................................................................................... 6
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
1 Calling Line Identification Presentation (CLIP)
|
......................................................................................6
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
1.1 Normal operation
|
............................................................................................................................................... 6
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
1.2 Interrogation
|
...................................................................................................................................................... 7
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
1.3 Activation, deactivation, registration and erasure
|
.............................................................................................. 7
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
2 Calling Line Identification Restriction (CLIR)
|
........................................................................................7
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
2.1 Normal Operation
|
.............................................................................................................................................. 7
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
2.2 Requesting presentation of CLI
|
......................................................................................................................... 8
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
2.3 Requesting restriction of CLI presentation
|
........................................................................................................ 8
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
2.4 Interrogation
|
...................................................................................................................................................... 8
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
2.5 Activation, deactivation, registration and erasure
|
.............................................................................................. 9
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
3 Connected Line Identification Presentation (COLP)
|
...............................................................................9
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
3.1 Normal operation
|
............................................................................................................................................... 9
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
3.2 Interrogation
|
.................................................................................................................................................... 10
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
3.3 Activation, deactivation, registration and erasure
|
............................................................................................ 10
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
4 Connected Line Identification Restriction (COLR)
|
...............................................................................10
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
4.1 Normal operation
|
............................................................................................................................................. 10
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
4.2 Interrogation
|
.................................................................................................................................................... 10
|
7be78a47afae26bd71de9acea1d7fa92
|
124 081
|
4.3 Activation, deactivation, registration and erasure
|
............................................................................................ 11 Annex A: Change history ..............................................................................................................................12 ETSI ETSI TS 124 081 V3.1.0 (2000-06) 4 3G TS 24.081 version 3.1.0 Release 99 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 line identification 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 ETSI TS 124 081 V3.1.0 (2000-06) 5 3G TS 24.081 version 3.1.0 Release 99 0 Scope The present document specifies the procedures used at the radio interface for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of line identification 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 3G TS 24.010 the general aspects of the specification of supplementary services at the layer 3 radio interface are given. 3G TS 24.080 specifies the formats and coding for the supplementary services. Definitions and descriptions of supplementary services are given in 3G TS 22.004 and 3G TS 22.08x and 3G TS 22.09x-series. 3G TS 22.081 is related specially to line identification supplementary services. Technical realization of supplementary services is described in 3G TS 23.011 and 3G TS 23.08x and 3G TS 23.09x-series. 3G TS 23.081 is related specially to line identification supplementary services. The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in 3G TS 24.007 and 3G TS 24.008. The following supplementary services belong to the line identification supplementary services and are described in the present document: - Calling line identification presentation (CLIP) (clause 1); - Calling line identification restriction (CLIR) (clause 2); - Connected line identification presentation (COLP) (clause 3); - Connected line identification restriction (COLR) (clause 4). 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.02: "Digital cellular telecommunications system (Phase 2+); General description of a GSM Public Land Mobile Network (PLMN)". [2] 3G TS 22.081: "General on supplementary services". [3] 3G TS 22.081: "Line identification supplementary services - Stage 1". [4] 3G TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1". [5] 3G TS 22.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1". [6] 3G TS 22.084: "MultiParty (MPTY) supplementary services - Stage 1". [7] 3G TS 22.085: "Closed User Group (CUG) supplementary services - Stage 1". [8] 3G TS 22.086: "Advice of Charge (AoC) supplementary services - Stage 1". ETSI ETSI TS 124 081 V3.1.0 (2000-06) 6 3G TS 24.081 version 3.1.0 Release 99 [9] 3G TS 22.088: "Call Barring (CB) supplementary services - Stage 1". [10] 3G TS 22.090: "Unstructured Supplementary Service Data (USSD) - Stage 1". [11] 3G TS 23.011: "Technical realization of supplementary services". [12] 3G TS 23.081: "Line identification supplementary services - Stage 2". [13] 3G TS 23.082: "Call Forwarding (CF) supplementary services - Stage 2". [14] 3G TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2". [15] 3G TS 23.084 "MultiParty (MPTY) supplementary services - Stage 2". [16] 3G TS 23.085: "Closed User Group (CUG) supplementary services - Stage 2". [17] 3G TS 23.086: "Advice of Charge (AoC) supplementary services - Stage 2". [18] 3G TS 23.088: "Call Barring (CB) supplementary services - Stage 2". [19] 3G TS 23.090: "Unstructured supplementary services operation - Stage 2". [20] 3G TS 24.007: "Mobile radio interface signalling layer 3; General aspects". [21] 3G TS 24.008: "Mobile radio interface layer 3 specification". [22] 3G TS 24.010: "Mobile radio interface layer 3; Supplementary services specification; General aspects". [23] 3G TS 24.080: "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 and 3G TR 21.905. 1 Calling Line Identification Presentation (CLIP) 1.1 Normal operation The calling line identity consists of a calling party BCD number and optionally, a calling party subaddress and/or a cause of no CLI. The calling party BCD number information element is made up of a number of information units as indicated in 3G TS 24.008. In addition to or instead of the calling party's digits, the subscriber may be given the following information: - screening indicator; - presentation indicator. Indicator values are given in 3G TS 24.008. The calling party subaddress information element is made up of a number of information units as indicated in 3G TS 24.008. The cause of no CLI information element is made up of a detailed cause of no CLI as indicated in TS 24.008. A called mobile subscriber subscribing to calling line identification presentation service receives the call with the information indicated above, see figure 1.1. MSb Network ETSI ETSI TS 124 081 V3.1.0 (2000-06) 7 3G TS 24.081 version 3.1.0 Release 99 SETUP <------------------------------------------------------------------------------------------------------------------------ Calling party BCD number (screening indicator, presentation indicator, calling party digits), Calling party subaddress, Cause of No CLI NOTE: The calling party subaddress is passed to MSb if it is received from the originating network. Figure 1.1: Notification by the network to the called mobile subscriber When the calling line identity is not available, the presentation indicator which is given to the called mobile subscriber takes the value of "number not available". 1.2 Interrogation Status Check The mobile subscriber can request the status of the supplementary service and be informed if the service is provided to him. MSa Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CLIP)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return Result = InterrogateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return Error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) Figure 1.2: Interrogation of calling line identification presentation 1.3 Activation, deactivation, registration and erasure Activation, deactivation, registration and erasure of the supplementary service calling line identification presentation are not applicable. 2 Calling Line Identification Restriction (CLIR) 2.1 Normal Operation When calling line identification restriction is applicable, the originating network provides the destination network with a notification that the calling party's ISDN number, with possible additional address information, is not allowed to be presented to the called party. If the called mobile user subscribes to calling line identification presentation and the calling party has calling line identification restriction applied, the called mobile party shall receive the presentation indicator showing "presentation restricted" in the calling party BCD field of the SETUP message, see figure 1.1. In this case, the calling party's number (digits) will not be sent towards the called subscriber. ETSI ETSI TS 124 081 V3.1.0 (2000-06) 8 3G TS 24.081 version 3.1.0 Release 99 2.2 Requesting presentation of CLI When the CLIR presentation mode is temporary (presentation restricted), it is possible for the subscriber to present his CLI on a per call basis. The MS shall send a CLIR suppression information element to the network. If the subscriber tries to override CLIR (i.e. requests that the CLI is displayed), when he has subscribed to permanent mode a NotifySS shall be sent to the MS in order to inform that the override has not been performed and the call set-up shall continue. MSa Network SETUP ------------------------------------------------------------------------------------------------------------------------> CLIR suppression FACILITY <- - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Invoke = NotifySS (CLIR, CLIR Suppression Rejected)) Figure 2.1: Requesting presentation of CLI 2.3 Requesting restriction of CLI presentation When the CLIR presentation mode is temporary (presentation allowed), it is possible for the subscriber to restrict the CLI on a per call basis. The MS shall send a CLIR invocation information element to the network. If the subscriber has not subscribed to CLIR and tries to invoke CLIR (i.e. requests that the CLI is not displayed), the SETUP shall be rejected. The MS and the network shall act in accordance with 3G TS 24.008 network initiated call clearing procedure, see figure 2.2. MSa Network SETUP ------------------------------------------------------------------------------------------------------------------------> CLIR invocation DISCONNECT/RELEASE/RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cause #50 (Facility not subscribed, diagnostic = CLIR not subscribed) Figure 2.2: Requesting restriction of CLI presentation 2.4 Interrogation Data request The mobile subscriber can request the data of the supplementary service. If the service is not provisioned the network shall sent a return result including the SS-Status parameter. If the service is provisioned the network shall sent a return result including the SS-Status and the CLI Restriction Option parameters. ETSI ETSI TS 124 081 V3.1.0 (2000-06) 9 3G TS 24.081 version 3.1.0 Release 99 MSa Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (CLIR)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return Result = InterrogateSS (SS-Status, CLI Restriction Option)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return Error (Error)) RELEASE COMPLETE <- - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) Figure 2.3: Interrogation of calling line identification restriction 2.5 Activation, deactivation, registration and erasure Activation, deactivation, registration and erasure of the supplementary service calling line identification restriction are not applicable. 3 Connected Line Identification Presentation (COLP) 3.1 Normal operation The connected line identity consists of a connected number and optionally, a connected subaddress. The connected number is made up of a number of information units as indicated in 3G TS 24.008. In addition to or instead of the connected number digits, the subscriber may be given the following information: - screening indicator; - presentation indicator. Indicator values are given in 3G TS 24.008. In the call set-up phase the calling mobile subscriber receives the information at the end of the call set-up. The connected subaddress information element is made up of a number of information units as indicated in 3G TS 24.008. A calling mobile subscriber subscribing to connected line identification presentation receives a message with the information indicated above, see figure 3.1. MSa Network CONNECT <------------------------------------------------------------------------------------------------------------------------ Connectednumber (Screening-indicator, Presentation-indicator, Connected number digits), Connected subaddress NOTE: The connected subaddress is passed to MSa if it is received from the terminating network. Figure 3.1: Notification by the network to the calling mobile subscriber When the connected line identity is not available (due to interworking or presentation restrictions), appropriate indication information is given to the calling mobile subscriber. ETSI ETSI TS 124 081 V3.1.0 (2000-06) 10 3G TS 24.081 version 3.1.0 Release 99 3.2 Interrogation Status Check The mobile subscriber can request the status of the supplementary service and be informed if the service is provided to him. MSa Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (COLP)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return Result = Interrogate SS (SS-status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return Error (Error)) RELEASE COMPLETE <- - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) Figure 3.2: Interrogation of connected line identification presentation 3.3 Activation, deactivation, registration and erasure Activation, deactivation, registration and erasure of the supplementary service connected line identification presentation is not applicable. 4 Connected Line Identification Restriction (COLR) 4.1 Normal operation When connected line identification restriction is applicable the destination network provides the originating network with a notification that the connected party's ISDN number, with possible additional address information, is not allowed to be presented to the calling party. If the calling mobile user subscribes to connected line identification presentation and the connected party has connected line identification restriction applied, the calling mobile party shall receive the presentation indicator showing "presentation restricted", see figure 3.1. In this case, the connected number will not be sent towards the calling subscriber. 4.2 Interrogation Status Check The mobile subscriber can request the status of the supplementary service and be informed if the service is provided to him. ETSI ETSI TS 124 081 V3.1.0 (2000-06) 11 3G TS 24.081 version 3.1.0 Release 99 MSa Network REGISTER ------------------------------------------------------------------------------------------------------------------------> Facility (Invoke = InterrogateSS (COLR)) RELEASE COMPLETE <------------------------------------------------------------------------------------------------------------------------ Facility (Return Result = InterrogateSS (SS-Status)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return Error (Error)) RELEASE COMPLETE <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem)) Figure 4.1: Interrogation of connected line identification restriction Activation, deactivation, registration and erasure of the supplementary service connected line identification restriction are not applicable. ETSI ETSI TS 124 081 V3.1.0 (2000-06) 12 3G TS 24.081 version 3.1.0 Release 99 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 04.81 6.0.0 Transferred to 3GPP CN1 CN#03 24.081 3.0.0 Approved at CN#03 CN#08 24.081 3.0.0 001 R99 3.1.0 Cause of no CLI indication 13 ETSI ETSI TS 124 081 V3.1.0 (2000-06) 3G TS 24.081 version 3.1.0 Release 1999 History Document history V3.0.0 January 2000 Publication V3.1.0 June 2000 Publication
|
978af1c18778834eb7125515246ae9af
|
122 121
|
1 Scope
|
........................................................................................................................................................5
|
978af1c18778834eb7125515246ae9af
|
122 121
|
2 References
|
................................................................................................................................................5
|
978af1c18778834eb7125515246ae9af
|
122 121
|
2.1 Normative references
|
......................................................................................................................................... 5
|
978af1c18778834eb7125515246ae9af
|
122 121
|
2.2 Informative references
|
....................................................................................................................................... 5
|
978af1c18778834eb7125515246ae9af
|
122 121
|
3 Definitions and abbreviations
|
..................................................................................................................6
|
978af1c18778834eb7125515246ae9af
|
122 121
|
3.1 Definitions
|
......................................................................................................................................................... 6
|
978af1c18778834eb7125515246ae9af
|
122 121
|
3.2 Abbreviations
|
..................................................................................................................................................... 6
|
978af1c18778834eb7125515246ae9af
|
122 121
|
4 General Description of the VHE
|
..............................................................................................................7
|
978af1c18778834eb7125515246ae9af
|
122 121
|
5 Framework for Services
|
...........................................................................................................................8
|
978af1c18778834eb7125515246ae9af
|
122 121
|
5.1 Ways to realise services
|
................................................................................................................................... 10
|
978af1c18778834eb7125515246ae9af
|
122 121
|
6 User Requirements of VHE
|
...................................................................................................................11
|
978af1c18778834eb7125515246ae9af
|
122 121
|
6.1 Personal Service Environment
|
......................................................................................................................... 11
|
978af1c18778834eb7125515246ae9af
|
122 121
|
6.1.1 User Profiles
|
............................................................................................................................................... 12
|
978af1c18778834eb7125515246ae9af
|
122 121
|
6.1.2 User Profiles and Multiple Subscriptions
|
................................................................................................... 13
|
978af1c18778834eb7125515246ae9af
|
122 121
|
6.1.3 Management of the user profile
|
.................................................................................................................. 13
|
978af1c18778834eb7125515246ae9af
|
122 121
|
6.1.4 Requirements for Standardisation
|
.............................................................................................................. 13
|
978af1c18778834eb7125515246ae9af
|
122 121
|
7 Home Environment Requirements for VHE Provision
|
..........................................................................13
|
978af1c18778834eb7125515246ae9af
|
122 121
|
8 Serving Network Requirements for VHE Provision
|
..............................................................................14
|
978af1c18778834eb7125515246ae9af
|
122 121
|
9 VASP Relationship to VHE
|
...................................................................................................................14
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10 Service Capability Features
|
...................................................................................................................14
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10.1 Framework service capability features
|
............................................................................................................ 15
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10.1.1 Authentication service capability feature
|
................................................................................................... 15
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10.1.2 Authorisation service capability feature
|
..................................................................................................... 15
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10.1.3 Registration service capability feature
|
....................................................................................................... 16
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10.1.4 Discovery service capability feature
|
.......................................................................................................... 16
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10.1.5 Notification service capability feature
|
........................................................................................................ 16
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10.2 Non-Framework service capability features
|
.................................................................................................... 16
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10.2.1 Session Control service capability features
|
................................................................................................ 16 10.2.2 Security/Privacy service capability features............................................................................................... 17
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10.2.3 (Void)
|
......................................................................................................................................................... 17
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10.2.4 User Location service capability features
|
................................................................................................... 17
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10.2.5 User Status service capability features
|
....................................................................................................... 18
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10.2.6 Terminal Capabilities service capability features
|
....................................................................................... 18
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10.2.7 Information Transfer service capability features
|
........................................................................................ 18
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10.2.8 Reserved section
|
......................................................................................................................................... 19
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10.2.9 User Profile Management service capability features
|
................................................................................ 19
|
978af1c18778834eb7125515246ae9af
|
122 121
|
10.2.10 Charging service capability features
|
.......................................................................................................... 19
|
978af1c18778834eb7125515246ae9af
|
122 121
|
11 Service execution environment
|
..............................................................................................................19
|
978af1c18778834eb7125515246ae9af
|
122 121
|
12 Charging requirements
|
...........................................................................................................................19
|
978af1c18778834eb7125515246ae9af
|
122 121
|
13 Security requirements
|
............................................................................................................................20 Annex A (informative): Service examples to be considered in VHE................................................21 Annex B (informative): Change history...............................................................................................22 ETSI ETSI TS 122 121 V3.3.0 (2000-06) 4 3G TS 22.121 version 3.3.0 Release 1999 Foreword This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). 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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater 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 document. ETSI ETSI TS 122 121 V3.3.0 (2000-06) 5 3G TS 22.121 version 3.3.0 Release 1999 1 Scope The present document specifies the content of the stage one requirement for realisation of VHE. Virtual Home Environment (VHE) is defined as a concept for personal service environment (PSE) portability across network boundaries and between terminals. The concept of the VHE is such that users are consistently presented with the same personalised features, User Interface customisation and services in whatever network and whatever terminal (within the capabilities of the terminal and the network), wherever the user may be located. A key feature to support VHE is the ability to build services using a standardised application interface. Requirements not applicable for R99 will be explicitly indicated. 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. 2.1 Normative references [1] GSM 01.04 (ETR 350): "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.57: "Digital cellular telecommunication system (Phase 2+); Mobile Station Application Execution Environment (MExE); Service description". [3] GSM 02.78: "Digital cellular telecommunication system (Phase 2+); Customised Applications for Mobile network Enhanced Logic (CAMEL); Service definition - Stage 1". [4] GSM 11.14: "Digital cellular telecommunication system (Phase 2+); Specification of the SIM Application Toolkit for the Subscriber Identity Module - Mobile Equipment; (SIM - ME) interface". [5] 3G TS 22.01: "Universal Mobile Telecommunications System (UMTS): Service Aspects; Service Principles". [6] 3G TS 22.05: "Universal Mobile Telecommunications System (UMTS); Services and Service Capabilities". [7] ITU-T Recommendation Q.1701: "Framework for IMT-2000 networks". [8] ITU-T Recommendation Q.1711: "Network Functional Model for IMT-2000". [9] 3G TS 22.00 UMTS phase 1. [10] 3G TS 23.127 “Virtual Home Environment/Open Service Architecture” 2.2 Informative references [1] 3G TR 22.70: "Universal Mobile Telecommunications System (UMTS); Virtual Home Environment". ETSI ETSI TS 122 121 V3.3.0 (2000-06) 6 3G TS 22.121 version 3.3.0 Release 1999 [2] World Wide Web Consortium Composite Capability/Preference Profiles (CC/PP): A user side framework for content negotiation (www.w3.org). 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: HE-VASP: Home Environment Value Added Service Provider. This is a VASP that has an agreement with the Home Environment to provide services. Local Service: service, which can be exclusively provided in the current serving network by a Value added Service Provider. Service Capabilities: bearers defined by parameters, and/or mechanisms needed to realise services. These are within networks and under network control. Service Capability Feature: functionality offered by service capabilities that are accessible via the standardised application interface. Services: services are made up of different service capability features. Service Execution Environment: service execution environment is a platform on which an application or programme is authorised to perform a number of functionalities; examples of service execution environments are the user equipment, integrated circuit card and a network platform or any other server. Applications / Clients: these are services, which are designed using service capability features. Application Interface: standardised Interface used by application/clients to access service capability features. Personal Service Environment: contains personalised information defining how subscribed services are provided and presented towards the user. The Personal Service Environment is defined in terms of one or more User Profiles. Home Environment: responsible for overall provision of services to users. User: is a logical entity, which uses UMTS services. User Interface Profile: contains information to present the personalised user interface within the capabilities of the terminal and serving network. User Services Profile: contains identification of subscriber services, their status and reference to service preferences. User Profile: this is a label identifying a combination of one user interface profile, and one user services profile. Value Added Service Provider: provides services other than basic telecommunications service for which additional charges may be incurred. Virtual Home Environment: concept for personal service environment portability across network boundaries and between terminals. Further UMTS related definitions are given in 3G TS 22.101. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: API Application Programming Interface CAMEL Customised Application For Mobile Network Enhanced Logic CAP Camel Application Part CORBA Common Object Request Broker Architecture CSE Camel Service Environment ETSI ETSI TS 122 121 V3.3.0 (2000-06) 7 3G TS 22.121 version 3.3.0 Release 1999 FFS For Further Study GSN GPRS Support Nodes HE Home Environment HE-VASP Home Environment Value Added Service Provider HLR Home Location Register LCS LoCation Services MAP Mobile Application Part ME Mobile Equipment MExE Mobile Station (Application) Execution Environment MMI Man Machine Interface MS Mobile Station MSC Mobile Switching Centre OSA Open Service Architecture PLMN Public Land Mobile Network PSE Personal Service Environment SAT SIM Application Tool-Kit SIM Subscriber Identity Module SMS Short Message Service SSF Service Switching Function USIM User Service Identity Module USSD Unstructured Supplementary Service Data VASP Value Added Service Provider VHE Virtual Home Environment Further GSM related abbreviations are given in GSM 01.04. Further UMTS related abbreviations are given in UMTS TS 22.01. 4 General Description of the VHE Virtual Home Environment (VHE) is defined as a concept for personal service environment portability across network boundaries and between terminals. The concept of the VHE is such that users are consistently presented with the same personalised features, User Interface customisation and services in whatever network and whatever terminal (within the capabilities of the terminal and network), where ever the user may be located. The key requirements of the VHE are to provide a user with a personal service environment which consist of: - personalised services; - personalised User Interface (within the capabilities of terminals); - consistent set of services from the user's perspective irrespective of access e.g. (fixed, mobile, wireless etc. Global service availability when roaming. The standards supporting VHE requirements should be flexible enough such that VHE can be applicable to all types of future networks as well as providing a framework for the evolution of existing networks. Additionally the standards should have global significance so that user's can avail of their services irrespective of their geographical location. This implies that VHE standards should: - provide a common access for services in future networks; - enable the support of VHE by future networks; - enable the creation of services; - enable personal service environment to be recoverable (e.g in the case of loss/damage of user equipment). Roles and components involved in realisation of VHE consist of the following also see figure 1: - home environment; - user identifiers; - users; ETSI ETSI TS 122 121 V3.3.0 (2000-06) 8 3G TS 22.121 version 3.3.0 Release 1999 - terminals (simultaneous activation of terminals providing the same service per single subscription is not allowed); - serving networks; - subscriptions; - possibly value added service providers; - personal service environment; - user profiles. USER Personal Service Environment Home Environment Provided and Controlled by User Profile Contains 1:N Value Added Service Provider HE Value Added Service Provider N:N Figure 1: Service Provisioning From User's point of View The Home Environment provides and controls services to the user in a consistent manner. The User's personal service environment is a combination of services and personalisation information (described in the user profile). The user may have a number of user profiles which enable her to manage communications according to different situations or needs, for example being at work, in the car or at home. Services provisioned to the user may allow or require personalisation by the user. The Home Environment provides services to the user in a managed way, possibly by collaborating with HE-VASPs, but this is transparent to the user. The same service could be provided by more than one HE-VASP and HE-VASP can provide more than one service. Additionally, but not subject to standardisation, the user may access services directly from Value Added Service Providers. The Home Environment does not manage services obtained directly from VASPs. A mechanism may be provided which allows the user to automate access to those services obtained directly from VASPs and personalise those services. However such a mechanism is outside of the scope of the present document. 5 Framework for Services The implementation of VHE in UMTS release 99 shall support both GSM phase 2+ release 99 teleservices, bearer services and supplementary services as applied in 3G TS 22.100 and new services built by service capability features. Later UMTS developments will provide support for a wider range of services in later releases. ETSI ETSI TS 122 121 V3.3.0 (2000-06) 9 3G TS 22.121 version 3.3.0 Release 1999 Service Capabilities Application Interface Proprietary Service Capability Feature Proprietary Service Capability Pre-set by Standards, e.g. CAMEL, SAT, MExE, access to bearers etc. Service Capability Features Accessible to Applications/Clients via Standardised Application Interface Built using Service Capability Features Applications/Clients Proprietary Service Personal Service Environment Personal Service Environment (Customised/Portable) Standardised Figure 2: Framework for Services The goal of standardisation in UMTS with respect to services is to provide a framework within which services can be created based on standardised service capability features see figures 2 and 3. UMTS services will generally not rely on the traditional detailed service engineering (evident for supplementary services in second-generation systems), but instead provides services using generic toolkits. Services can be built using service capability features ([1], [2], [3], [4], [9], [10]), which are accessed via a standardised interface. An example of how a service can be built on service capability features could be "call to nearest restaurant", this will make use of call set-up, authorisation, location and database lookup. The available service capability features are visible to applications through the standardised application interface. The application interface can be realised in a non-generic way (implying applications must have knowledge of the underlying mechanisms used) and/or a generic way (implying applications need not have knowledge of underlying mechanisms used). The functionality provided in both cases is the same and both solutions are independent of vendor specific solution. For example, in the non-generic way, the User Location service capability features can be provided by a location server (e.g HLR, LCS). In the generic way the application will only see a single User Location service capability feature and does not know which location server provides it. - the standardised application interface shall be:Independent of vendor specific solutions; - independent of programming languages, operating systems etc used in the service capabilities; - secure scalable and extensible. In the case of realising the standardised application interface in the generic way, the following additional requirements apply: - independent of the location where service capabilities are implemented; - independent of supported server capabilities in the network; and - Access to Service Capability Features shall be realised using modern state of the art access technologies, e.g. distributed object oriented technique might be considered. ETSI ETSI TS 122 121 V3.3.0 (2000-06) 10 3G TS 22.121 version 3.3.0 Release 1999 5.1 Ways to realise services The information contained in this clause is only to aid understanding and is not an extensive list. Figure 3 illustrates how the concept of VHE makes use of the standardised application interface and how that fits to the service capability features and service capabilities for release 99. Note that the Service Capabilities (SCx) shown below are representatives of the different possible capabilities. It is not to be implied as the agreed architecture as this is a stage 2 issue. Network terminal view clientn client2 ... API (e.g. MExE, SAT) GSM/GPRS/UMTS protocol(*) (*) ... standardised interfaces (+) ... to bestandardised GSM/GPRS/UMTS protocols, CAP/MAP(*) SC 2 SC 3 SC n Applications / Clients MS functionality, Standardized Services Service capabilities SC 1 ervice apability eatures (+) Application Interface SC 4 Figure 3: Possible realisation of Framework for Services STANDARDISED SERVICES (Supplementary Services, Tele-Services, etc.) are implemented on existing GSM/UMTS entities (e.g. HLR , MSC/VLR and terminal) on a vendor specific basis, using standardised interfaces (MAP, etc.) for service communication (e.g. downloading of service data). Availability and maintenance of these Services is also vendor dependent. OPERATOR SPECIFIC SERVICES (OSS) are not standardised and could be implemented at the GSM/UMTS entities (e.g. HLR) on a vendor specific basis or using GSM ph 2+ mechanisms (CAMEL, SAT, MExE). These tool-kits use standardised interfaces to the underlying network (e.g. CAP, MAP) or use GSM Bearers to transport applications and data, for example, from the MexE service environment of SAT server to the MS/SIM. The implementation of these operator specific services on the different platforms (CSE, MExE service environment /SAT Server, MSs) is done in a completely vendor specific way and uses only proprietary interfaces. Other APPLICATIONS are like OSS not standardised. These applications will be implemented using standardised interfaces to the Service Capabilities (Bearers, Mechanisms). The functionality offered by the different Service Capabilities are defined by Service Capability Features. These Service Capability Features will be standardised and can be used by the application designers to build their applications. Within the terminals Service Capabilities are accessible via APIs, for example, MExE and SAT APIs, i.e. there will be no service capability features within the terminal. The terminal can communicate, using GSM/UMTS bearers, with applications in the network via the service capability features which may be optionally realised for MExE service environment and SAT-servers. ETSI ETSI TS 122 121 V3.3.0 (2000-06) 11 3G TS 22.121 version 3.3.0 Release 1999 General User Preferences and Subscribed Service USER Personal Service Environment Home Environment Provided and controlled by User Profile Contains 1:N Contains 1:N Value Added Service Provider HE Value Added Service Provider N:N The set of services from the Users point of view Service Profile, i.e. Specific Service Preferences Service Figure 4 6 User Requirements of VHE The user shall have the possibility to manage services as well as the appearance of the services. It shall be possible for the user to: - personalise services; - Personalised User Interface (within the capabilities of terminals); - access services from any network or terminal subject to network capabilities, terminal capabilities and any restrictions imposed by the home environment; - use services in a consistent manner irrespective of serving network and terminal, within the technical limitations; - access new services in the Home Environment; - modify a user profile(for example to include new services) from any location; - activate or deactivate user services; - discover which local services are available; - access local services in a secure manner; - interrogate current user service and user interface settings; - select a particular User Profile; - indicate (on a session by session basis if necessary) to which subscription charges are to be applied to; - recover MS resident User Profile information to protect against loss or damage of user equipment. Be aware of limitations of services, which may result from different terminals and or serving network capabilities. 6.1 Personal Service Environment The Personal Service Environment describes how the user wishes to manage and interact with their communications services. The PSE is a combination of a list of subscriptions (detailing provisioned services), preferences associated ETSI ETSI TS 122 121 V3.3.0 (2000-06) 12 3G TS 22.121 version 3.3.0 Release 1999 with those services, terminal interface preferences and other information related to the user's experience of the system. Within the PSE the user can manage multiple subscriptions e.g. both business and personal, multiple terminal types and express location and temporal preferences. The Personal Service Environment is defined in terms of one or more User Profiles. 6.1.1 User Profiles A combination of different preferences is described by a User Profile. The user can define one or more User Profiles according to their needs. Each User Profile consists of two kinds of information: - interface related information (User Interface Profile); - services related information (User Services Profile). A User Interface Profile consists of the following type of information: - menu settings, e.g. menu items shown, menu structure, the placement of icons; - terminal settings, e.g. ringing tone and volume, font type and size, screen and text colour, language, content types and sizes accepted; - network related preferences e.g. language used for announcements. (editor's note: for clarification) A User Services Profile consists of the following information: - a list of services subscribed to and references to Service Preferences for each of those services if applicable. Service Preferences could be information such as redirection numbers, redirection conditions, caller screening lists, time-of-day variations etc; - service status (active/deactive). The user may define one or more User Interface Profiles and many User Services Profiles, but a given User Profile consists of a single combination of these. In this way a user could for example have a different User Profile to suit each of the three different terminals she owns. The User Services Profile is the same in each case but the User Interface Profile is different to suit the display capabilities of each terminal. User Profiles could also exist which use the same User Interface Profile but different User Services Profiles. This might simply imply that business calls are forwarded to an answering service when the user leaves the office because a new User Profile is now active. Where the user has more than one User Profile the activation of a particular one could be done in the following ways: - Statically: the user explicit selects one of the User Profiles as the active one; - Dynamically: the appropriate User Profile is selected automatically based upon some criteria such as time of day, location, terminal used or many other possibilities. Each User Profile must have an identity. For UMTS Release '99 the information in the User Profiles enables the service capabilities SAT, MExE and CAMEL toolkits in R'99 and existing GSM services to support the user's PSE across network boundaries and between different terminals. It shall be possible for the service capabilities to access the user profile information from the home environment if appropriate. ETSI ETSI TS 122 121 V3.3.0 (2000-06) 13 3G TS 22.121 version 3.3.0 Release 1999 6.1.2 User Profiles and Multiple Subscriptions The user may wish to manage more than one subscription in their PSE. This would allow them to have a single USIM but specify different preferences for the services provisioned in each subscription. In this case the User Services Profile will need to detail all of the services provided per subscription and provide references to the service preferences for each service. When initiating a chargeable event the user will need to indicate which subscription the charges should be applied to. 6.1.3 Management of the user profile The user and the home environment may modify the user's characterisation of the Personal Service Environment as described in the User Profiles at any time, and changes become effective at the earliest possible opportunity. The home environment shall be able to update distributed User Profiles to reflect any user or home environment modification of the user's Personal Service Environment. The User Profiles may be stored in the Mobile Station (the SIM or the ME), and/or the home environment. The information in User Services Profiles is distributed between the home environment and the MS. In the event of loss/damage of mobile station (SIM or ME), the User Profiles must be fully recoverable and be used to reconfigure a new mobile station. Some aspects of the User Profiles such as aspects related to terminal configuration, must be stored in a standardised format to support VHE. NOTE: To ensure that User Profiles are applicable to as wide a community of terminal and network types as possible, existing work on this topic in other standards fora should be considered. One possibility is the work of the World Wide Web Consortium on the Composite Capability/Preference Profile [2]. 6.1.4 Requirements for Standardisation To facilitate the provision of PSE and User Profiles the standard shall: - uniquely identify User Profiles; - provide a standardised format for describing terminal configuration preferences; 7 Home Environment Requirements for VHE Provision It shall be possible for the home environment to: - control access to services depending on the location of the user, and serving network; - control access to services on a per user basis e.g subject to subscription; - control access to services depending on available service capabilities in the serving network, and terminals; - manage service delivery based on for example end to end capabilities and/or user preferences; - request version of specific services supported in serving network and terminal; - request details (e.g. protocol versions and API versions) of available service capabilities supported in the serving network, and terminals; - define the scope for management of services by the user, for services provided by the HE; - handle charging for services (as defined in clause 11); - inform the serving network of the type of charging (i.e. prepaid or/and postpaid) for any required service; - inform the serving network of the threshold set for a given service required by the user and charged on a prepaid account; - inform the serving network how to manage a service for which the threshold has been reached; ETSI ETSI TS 122 121 V3.3.0 (2000-06) 14 3G TS 22.121 version 3.3.0 Release 1999 - manage the prepaid accounts (e.g. increase, decrease the credit, or pass the information to any application which manages the credit); - deploy services to users or groups of users; - manage provision of services to users or groups of users. 8 Serving Network Requirements for VHE Provision The serving network should not need to be aware of the services offered via the home environment. The user/home environment may request capabilities which are necessary to support home environment services. It shall be possible for the serving network to perform the following: - the serving network shall support user access to services in the home environment; - the serving network shall provide the necessary service capabilities to support the services from the home environment as far as possible; - dynamically provide information on the available service capabilities in the serving network; - provide transparent communication between clients and servers in terminals and networks; - request the charging information (type of charging, threshold for prepaid services and behaviour if the threshold is reached) for any service possibly required by the user; - handle the call according to the instructions received by the home environment regarding charging activities; - inform the home environment of the chargeable events (e.g. send CDRs, …). 9 VASP Relationship to VHE The user may access services directly from Value Added Service Providers. Services obtained directly from VASPs are not managed by the Home Environment and therefore are not part of the VHE offered by the Home Environment. A mechanism should be provided which allows the user to automate access to those services obtained directly from VASPs and personalise those services. However such a mechanism is outside of the scope of the present document. There may be some information, which is shared between the Home Environment and the HE-VASP (for example current capabilities). The Home Environment may grant the HE-VASP access to standardised service capabilities in order to allow the development and deployment of services on behalf of the Home Environment. There are no VASP requirements to support VHE. 10 Service Capability Features Services Capability Features are open, technology independent building blocks accessible via a standardised application interface. This interface shall be applicable for a number of different business and applications domains (including besides the telecommunication network operators also service provider, third party service providers acting as HE-VASPs, etc.). All of these businesses have different requirements, ranging from simple telephony and call routing, virtual private networks, fully interactive multimedia to using MS based applications. The service capability features shall enable applications to make use of the service capabilities (e.g. CAMEL, MExE, etc.) of the underlying UMTS network in an open and secure way. ETSI ETSI TS 122 121 V3.3.0 (2000-06) 15 3G TS 22.121 version 3.3.0 Release 1999 Application/Clients access the service capability features via the standardised application interface. This means that a single service capability feature is accessible and visible to application/clients via the method/operation invocations in the interface. Two different types of service capability features can be distinguished: - Framework service capability feature: this shall provide commonly used utilities, necessary for the non- framework service capability features to be accessible, secure, resilient and manageable; - Non-Framework service capability features: these shall enable the applications to make use of the functionality of the underlying network capabilities (e.g. User Location service capability features). 10.1 Framework service capability features The framework service capability features will be used e.g. for authentication, authorization, registration, notification, etc. and provide functionality that is independent of any particular type of service. Other commonly used features are described in more detail within TS 23.127, such as: - Trust and Security Management: It provides mechanisms for applications and framework to initiate communications, authenticate each other and mechanisms for applications to be authorised and access network capability features. - Integrity Management: It provides the support of integrity for both the OSA APIs and the Applications (e.g. load manager, fault manager, OAM and Heartbeat manager). 10.1.1 Authentication service capability feature Authentication is used to verify the identity of an entity (user, network, and application). Three types of authentication are distinguished: - User-Network Authentication: before a user can access her subscribed applications, the user has to be authenticated by the network that provides access to the application. This allows the network to check to what applications the user has subscribed to. User-network authentication is handled within the network and therefore outside the scope of the present document. - Application-Network Authentication: before an application can use the capabilities from the network, a service agreement has to be established between the application and the network. Establishment of such a service agreement starts with the mutual authentication between application and network. If a service agreement already exists, modification might be needed or a new agreement might supersede the existing. - User-Application Authentication: before a user can use an application or perform other activities (e.g. modifying profile data) the application provider must authenticate the user. When the network already authenticates the user, authentication is not needed anymore. When the network is transparent and the user accesses an application directly, authentication is needed between user and application but this is outside the scope of the present document. 10.1.2 Authorisation service capability feature Authorisation is the activity of determining what an authenticated entity (user, network, and application) is allowed to do. NOTE: Authentication must therefore precede authorisation. Two types of authorisation are distinguished: - Application-Network Authorisation: the network verifies what non-framework service capability features s (or even some framework service capability feature) the application is allowed to use. Once an application has been authorised to use one, more or all (non-framework) service capability features no further authorisation is required as long as the "allowed" (non-framework) service capability features are used. ETSI ETSI TS 122 121 V3.3.0 (2000-06) 16 3G TS 22.121 version 3.3.0 Release 1999 - User-Application Authorisation: the application verifies what actions the user is allowed to perform (e.g. deactivation of functionality, modification of application data). This is transparent to the network and therefore outside the scope of the present document. 10.1.3 Registration service capability feature The Registration service capability feature enables the non-framework service capability features (e.g. User Location) to register at the Framework. Registration must take place before authorised applications can find out from the Framework which non-framework service capability features are available. This means that the non-framework service capability features must be registered before they can be discovered and used by authorised applications. Note that only the non-framework service capability features have to be registered. The Framework service capability features (defined in subclause 10.1) are available by default since they provide basic mechanisms. 10.1.4 Discovery service capability feature The Discovery service capability feature enables the application to identify the total collection of service capability features that it can use. Upon request of the application, the Discovery service capability feature will indicate the non- framework service capability features that are available for the application. The list of available service capability features is created through the Registration process described in subclause 10.1.3. This means that a service capability feature must be registered at the Framework before it can be discovered by the application. 10.1.5 Notification service capability feature The Notification service capability feature allows applications to enable, disable and receive notifications of application related events that have occurred in the underlying GSM/UMTS network, e.g. indication that a new call is set-up or a message is received. NOTE: It should be further studied if Notification is only a Framework service capability feature or also specialised as non-framework service capability features (e.g. for notifications on location update, disconnected party etc.). 10.2 Non-Framework service capability features The Non-Framework service capability features represent the total collection of service capability features that are not included in the Framework. These non-framework service capability features enable the application to make use of the functionality provided by the network and service capabilities. Service capability features shall be defined as much as possible in a generic way to hide the network specific implementation. To achieve this, it is necessary to identify the functionality that is provided by more than one service capabilities. For example, User Location can be produced in several underlying ways. This functionality can be captured once when defined the service capability features in a generic way. It is important that the generic part becomes as large as possible. When applications use the generic service capability features, these applications become independent of (portable over) underlying service capabilities. Applications shall however still be able to request service capability features specific to a service capability (e.g. Call Setup from CAMEL). This will increase dependency of the used service capability. The following subclauses define generic service capability features e.g. for Session Control and Message Transfer. 10.2.1 Session Control service capability features This subclause details the Session Control related service capability features. Session Control service capability features shall offer the functionality to establish, maintain, modify and release bearers to/from other parties or entities. Herein, the term "session" can mean anything from a simple voice call to a complex multimedia "call" (including exchange of non delay-sensitive data). To define the necessary service capability features it is proposed to use a generic model (including the "session party handling"). For example, the following Session Control service capability features shall be provided (the list is not exhaustive): ETSI ETSI TS 122 121 V3.3.0 (2000-06) 17 3G TS 22.121 version 3.3.0 Release 1999 - allow the session to continue with modified information (e.g. changed destination number); - release the session (i.e. removing all parties from the session); - request session information (i.e. information like session duration, session end time); - supervise session (e.g. monitor for session duration or data volume, tariff switching moments and changes in QoS); - presentation of, or restriction of, information associated with a party involved in a session (e.g. calling line ID, calling name); - collect information from user (i.e the application shall be able to request data from the user. For example, the user might enter some code number). For each session it shall be possible to specify: - the events on which monitoring is required ([3]). NOTE: The mapping to service capabilities is for further study (it shall be investigated to which extend the requirements above fit to CAMEL, MEXE and other service capabilities). 10.2.2 Security/Privacy service capability features For the Security/Privacy the following service capability features shall be supported: - encryption of user data and signalling. 10.2.3 (Void) 10.2.4 User Location service capability features The User Location service capability features provide an application with information concerning the user's location. The user location information contains the following attributes: - location (e.g. in terms of universal latitude and longitude co-ordinates); - accuracy (value depending on local regulatory requirements and level of support in serving/home networks; note that the accuracy of the serving network might differ from that in the home environment); - age of location information (last known date/time made available in GMT). The following service capability features shall be provided: - report of location information: - the application shall be able to request user location information; - by default the location information is provided once; the application may also request periodic location reporting (i.e. multiple reports spread over a period of time). - notification of location update: - the application shall be able to request to be notified when the user's location changes, i.e. when: - the user enters or leaves a specified geographic area; - the user's location changes more than a specified lower boundary. The lower boundary can be selected from the options provided by the network. The application shall be able for each user to start/stop receipt of notifications and to modify the required accuracy by selecting another option from the network provided options. - Access control to location information: ETSI ETSI TS 122 121 V3.3.0 (2000-06) 18 3G TS 22.121 version 3.3.0 Release 1999 - the user shall be able to restrict/allow access to the location information. The restriction can be overridden by the network operator when appropriate (e.g. emergency calls). 10.2.5 User Status service capability features The User Status service capability features enable an application to retrieve the user's status, i.e. to find out on which terminals the user is available. The following service capability features shall be provided: - retrieval of User Status: - the application shall be able to retrieve the status of the user. - notification of User Status Change: - the application shall receive notifications when the user's terminal attaches or detaches: - detach: the user's terminal is switched on or the network initiates detach upon location update failure; - attach: the user's terminal is switched on or there has been a successful location update after network initiated detach. The application shall be able for each terminal to start/stop receipt of notifications. 10.2.6 Terminal Capabilities service capability features The Terminal Capabilities service capability features enable the application to find out what capabilities the user's terminal supports (note: "terminal" covers both (mobile) equipment and USIM). The following service capability features shall be provided: - retrieval of Terminal Capabilities: the application shall be able to retrieve the capabilities of the terminal. This includes: - the media that the terminal is capable to deal with (e.g. audio, video, PC data, WAP data; this information is needed by the application e.g. when the user wants to download messages from the mailbox); - the number of calls that the terminal can deal with simultaneously. Note: In Release 99 Terminal Capabilities can be provided by the Terminal Capability SCF only if the terminal is capable to supply them. Terminals (e.g. MEXE-, WAP clients) may provide their Terminal Capabilities to the server (e.g. MEXE service environment or WAP gateway) either spontaneously or on request. 10.2.7 Information Transfer service capability features The Information Transfer service capability feature shall enable an application to indicate to a user respectively an application in the UE or USIM about the presence of existing information for her. Physically, this indication may be sent by the underlying network e.g. as a SMS or USSD message to the terminal. The Information Transfer service capability feature provides the means to inform the underlying network that an indication shall be sent to the user. NOTE: For UMTS release 99 mechanisms like USSD or SMS may be employed to transfer the indication to the users terminal. The following service capability feature shall be supported: - send information notification: - the Send information notification service capability feature provides the means to inform the underlying network that an indication shall be sent to a user respectively an application in the UE or USIM about the presence of existing information for her; ETSI ETSI TS 122 121 V3.3.0 (2000-06) 19 3G TS 22.121 version 3.3.0 Release 1999 - this indication shall contain sufficient information for the receiving entity to react in an appropriate manner, e.g. an announcement ID, URL, a string, etc. In addition the application or execution environment in the terminal (e.g. MExE SAT), that is to display this information, needs to be referenced. - request message receipt notification: - the application can request to receive a notification every time a message is received in the mailbox for the user. This allows the application to take the appropriate action, e.g. informing the user. 10.2.8 Reserved section 10.2.9 User Profile Management service capability features The User Profile Management service capability features allow the application to retrieve the user profile (see subclause 6.1 for more information on user profiles). For release 99 the following information could be retrieved by an application: - terminal capabilities, as described in the proper section, - user information provided by and limited to CAMEL 3 R99 functionalities (ATI, ATN, ATM). 10.2.10 Charging service capability features The Charging service capability features enable the application to instruct the network and inform the user with charging information and to add some additional charging information to the network generated Call Detail Records. The following service capability features shall be provided: - define and manage the threshold (e.g. session duration, data volume) for the required service; - send charging data (this data is included in a "free format" field in the network generated Call Detail Records. It may contain information like a application generated Call Id, used by the application provider to relate application generated charging information to the network generated charging information); - transfer of Advice of Charge data (as defined in GSM02.24) to the terminal. 11 Service execution environment The following service execution environments shall be standardised and could be used to provide a VHE for the user: - user equipment execution environment; - IC card execution environment; - network execution environment not required for R99. For UMTS release 99 one or more of the following shall provide the execution environments: - MExE; - SIM Application Tool kit (SAT); - CAMEL. 12 Charging requirements Services, which are provided as part of the VHE, may be subject to charge at the discretion of the home environment ETSI ETSI TS 122 121 V3.3.0 (2000-06) 20 3G TS 22.121 version 3.3.0 Release 1999 There are several forms of charging which shall be available to the home environment. It shall be possible for the home environment to charge in the following instances: - subscription: - the user's registration to use services may be subject to charge. - service transfer: - the transfer of services and/or information to the user MS or USIM may be subject to charge. - service upgrading: - the upgrading of previously transferred services to the user's MS or USIM may be subject to charge (automated upgrading of services may be subject to a different charge). - service usage: - the usage of services by a user may be subject to a charge. - roaming: - the usage of VHE services when roaming may be subject to additional charges. Refer to UMTS 22.15 for further details. Other charging requirements may be identified and are for FFS. The mechanisms supporting VHE shall maintain a secure environment for the user and home environment. The specific security requirements are FFS. ETSI ETSI TS 122 121 V3.3.0 (2000-06) 21 3G TS 22.121 version 3.3.0 Release 1999 Annex A (informative): Service examples to be considered in VHE The following table shows the service examples to be considered in VHE. Table A.1 Benchmark Services Abb Priority Abbreviated Dialling ABD A Account Card Calling ACC B Automatic Alternative Billing AAB A Call Distribution CD A Call Forwarding CF A Call Hold CH A Call Rerouting Distribution CRD A Call Transfer TRA A Call Waiting CW A Completion of Call to Busy Subscriber CCBS A Conference Calling CON A Credit Card Calling CCC B Destination Call Routing DCR A Follow-Me Diversion FMD A Freephone FPH A Global Virtual Network Service GVNS A Hot Line HOT A International Telecommunication Charge Card ITCC B Internetwork Freephone IFPH A Internetwork Mass Calling IMAS A Internetwork Premium Rate IPRM A Internetwork Televoting IVOT A Malicious Call Identification MCID A Mass Calling MAS A Message store and forward MSF A Multimedia MMD B Originating Call Screening OCS A Premium Rate PRM A Security Screening SEC A Selective Call Forward on Busy / Dont' answer SCF A Split Charging SPL A Televoting VOT A Terminating Call Screening TCS A Terminating Key Code Protection TCKP B Universal Access Number UAN B Universal Personal Telecommunication UPT A User-Defined Routing UDR B (FFS) Virtual Private Network VPN A Benchmark services listed above could be realised by service capability features. ETSI ETSI TS 122 121 V3.3.0 (2000-06) 22 3G TS 22.121 version 3.3.0 Release 1999 Annex B (informative): Change history Version Date Comment 0.0.0 Sep 1998 Initial Draft at Ipswich 0.1.0 Oct 1998 Initial Draft at Uxbridge Meeting 0.2.0 Nov 1998 Draft at Newbury Meeting 0.3.0 Jan 1999 Draft after Stockholm meeting 0.4.0 Jan 1999 Draft to include requirement for R99 0.5.0 Feb 1999 Draft to include corrections from Ericsson and TTC requirements 0.6.0 Feb 1999 Draft to include changes made after adhoc meeting in Vienna 0.7.0 March 1999 Change to include text to fig 2 and 3 and for presentation to v1.0 1.0.0 March 12/99 Input text to state the inclusion of OSA requirements 1.1.0 March 17/99 Addition of Annex B, OSA text 1.2.0 April 30/99 Modification after Dublin Meeting 1.3.0 May 19/99 Modification after Hampton CT. 2.0.0 June 99 Modification at Sophia Antipolis 3.0.0 June 99 Approved Specification at SA#4 in Miami 3.1.0 October 1999 Inclusion of 3 CRs at SA#5, Kyongju, Korea 3.2.0 March 2000 Inclusion of CRs at SA#7, Madrid, Spain TSG SA# SA Doc. SA1 Doc Spec CR Rev Rel Cat Subject/Comment Old New SA#04 22.121 3.0.0 SP-05 SP-99442 S1-99809 22.121 002 R99 B Virtual Home Environment. 3.0.0 3.1.0 SP-05 SP-99442 S1-99845 22.121 003 R99 B Addition of IP4 Addressing 3.0.0 3.1.0 SP-05 SP-99442 S1-99535 22.121 004 R99 B Charging capabilities 3.0.0 3.1.0 SP-07 SP-000067 S1-000107 22.121 005 R99 F Clarification of service capabilities 3.1.0 3.2.0 SP-07 SP-000067 S1-000156 22.121 006 R99 C Information Transfer service capability feature 3.1.0 3.2.0 SP-08 SP-000204 S1-000267 22.121 007 R99 F Modification of section 10.2.6 on reducing the scope of the VHE/OSA reqirements 3.2.0 3.3.0 SP-08 SP-000204 S1-000283 22.121 008 R99 F Removal of section 10.2.3 Address Translation SCF 3.2.0 3.3.0 SP-08 SP-000204 S1-000285 22.121 009 R99 F Modification of section 10.2.9 to reduce scope of User Profile Management service capabilities 3.2.0 3.3.0 SP-08 SP-000204 S1-000334 22.121 010 R99 F Alignment of VHE Stage 1 top VHE/OSA Stage 2 and stage 3 3.2.0 3.3.0 23 ETSI ETSI TS 122 121 V3.3.0 (2000-06) 3G TS 22.121 version 3.3.0 Release 1999 History Document history V3.1.0 January 2000 Publication V3.2.0 March 2000 Publication V3.3.0 June 2000 Publication
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
1 Scope
|
........................................................................................................................................................7
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
2 References
|
................................................................................................................................................7
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
3 Definitions and abbreviations
|
..................................................................................................................8
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
3.1 Definitions
|
......................................................................................................................................................... 8
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
3.2 Abbreviations
|
..................................................................................................................................................... 8
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
4 Introduction
|
..............................................................................................................................................8
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
5 Roaming Scenario
|
....................................................................................................................................8
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
5.1 Relationship between GLR and HLR
|
................................................................................................................ 9
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
5.2 Relationship between GLR and VLR
|
................................................................................................................ 9
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
5.3 Roaming to VPLMN with GLR from HPLMN without GLR
|
......................................................................... 10
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
5.4 Intra-VPLMN with GLR roaming
|
................................................................................................................... 10
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
5.5 Inter-VPLMNs with GLR Roaming
|
................................................................................................................ 11
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
5.6 Roaming to VPLMN without GLR from VPLMN with GLR
|
......................................................................... 11
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
6 Logical Network Model
|
.........................................................................................................................12
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
6.1 GLR
|
................................................................................................................................................................. 12
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
6.2 Intermediate MSC
|
............................................................................................................................................ 12
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
6.3 Intermediate GSN
|
............................................................................................................................................ 13
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
6.4 Gate Node
|
........................................................................................................................................................ 13
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7 Functional Description
|
...........................................................................................................................13
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7.1 Logical Functions
|
............................................................................................................................................ 13
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7.1.1 Message Relay Function
|
............................................................................................................................ 13
|
1893565a4caa844326e5878da4f18a3d
|
123 119
|
7.1.2 Address Conversion Function
|
.................................................................................................................... 13
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.