OrganizedProgrammers/ETSISpecContent · Datasets at Hugging Face

hash stringlengths 32 32	doc_id stringlengths 7 13	section stringlengths 3 121	content stringlengths 0 3.82M
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.2.1 Description	................................................................................................................................................... 6
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.2.2 Applicability to telecommunication services	............................................................................................... 6
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.3 Normal procedures with successful outcome	..................................................................................................... 6
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.3.1 Provision	...................................................................................................................................................... 6
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.3.2 Withdrawal	................................................................................................................................................... 7
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.3.3 Registration	.................................................................................................................................................. 7
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.3.4 Erasure	......................................................................................................................................................... 7
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.3.5 Activation	..................................................................................................................................................... 7
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.3.6 Deactivation	................................................................................................................................................. 7
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.3.7 Invocation	..................................................................................................................................................... 7
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.3.8 Normal operation with successful outcome	................................................................................................. 7
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.3.9 Interrogation	................................................................................................................................................. 7
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.4 Exceptional procedures or unsuccessful outcome	.............................................................................................. 8
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.5 Alternate procedures	.......................................................................................................................................... 8
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.6 Interactions with other supplementary services	................................................................................................. 8
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.6.1 Calling Line Identification Presentation (CLIP)	.......................................................................................... 8
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.6.2 Calling Line Identification Restriction (CLIR)	............................................................................................ 8
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.6.3 Call Forwarding Unconditional (CFU)	........................................................................................................ 8
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.6.4 Call Forwarding on mobile subscriber Busy (CFB)	..................................................................................... 8
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.6.4.1 Network Determined User Busy (NDUB)	.............................................................................................. 8
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.6.4.2 User Determined User Busy (UDUB)	.................................................................................................... 9
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.6.5 Call Forwarding on No Reply (CFNRy)	...................................................................................................... 9
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.6.6 Call Forwarding on mobile subscriber Not Reachable (CFNRc)	................................................................. 9
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.6.7 Call Waiting (CW)	....................................................................................................................................... 9
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.6.9 Explicit Call Transfer (ECT)	........................................................................................................................ 9
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.6.10 Support of Private Numbering Plan (SPNP)	................................................................................................ 9
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.6.11 Completion of Calls to Busy Subscriber (CCBS)	........................................................................................ 9
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.6.12 enhanced Multi-Level Precedence and Pre-emption (eMLPP)	.................................................................... 9
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.7 Service functions for roamers	............................................................................................................................ 9
c4dcc5fb97678154a0beb0ac23aec589	122 096	4.8 Interworking considerations	............................................................................................................................... 9 Annex A (informative): Change history.......................................................................................................10 History..............................................................................................................................................................11 ETSI TS 122.096 V3.0.1 (2000-01) (3G TS 22.096 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.096 V3.0.1 (1999-10) 4 3G TS 22.096 version 3.0.1 Foreword This Technical Specification has been produced by the 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 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 122.096 V3.0.1 (2000-01) 3G TS 22.096 version 3.0.1 (3G TS 22.096 version 3.0.1 Release 1999) ETSI ETSI 3GPP 3G TS 22.096 V3.0.1 (1999-10) 5 3G TS 22.096 version 3.0.1 1 Scope The present document describes the supplementary services belonging to the group Name Identification supplementary services. The general aspects, including definitions and recommended provision, of the description of the supplementary services are given in TS 22.004. The group of Name Identification supplementary services is divided into the following supplementary services: CNAP Calling Name Presentation (clause 4). 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. • For this Release 1999 document, references to GSM documents are for Release 1999 versions (version 8.x.y). [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] TS 22.004: "General on Supplementary Services". [3] TS 22.081: "Line Identification Supplementary Services - Stage 1". [4] TR 21.905: "Vocabulary for 3GPP Specifications". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following definitions apply: Definition of name identity: The name identity is made up of the following information unit: - The name of the mobile subscriber for the purpose of calling name presentation - up to 80 characters of information associated with a specific calling party. The calling name identity is the name identity of the calling party. Definition of Presentation Indicator: In addition to or instead of the name identity, the network may give a Presentation Indicator (PI) to the called mobile subscriber of the CNAP service. The following information may be given: - Presentation Indicator (PI) showing: a) presentation restricted, or ETSI TS 122.096 V3.0.1 (2000-01) 3G TS 22.096 version 3.0.1 (3G TS 22.096 version 3.0.1 Release 1999) ETSI ETSI 3GPP 3G TS 22.096 V3.0.1 (1999-10) 6 3G TS 22.096 version 3.0.1 b) name unavailable. The name identity of a PLMN subscriber shall always be provided by the network. Calling Party: The calling party is the originating party. Called Party: The called party is the terminating party. The CNAP service is provided to the called party. Calling Name Information: The calling name information of the calling party includes either the calling name identity or an indication of privacy or unavailability. 3.2 Abbreviations In addition to the following abbreviations used in the present document, abbreviations are listed in GSM 01.04. CNAP Calling Name Presentation 4 Calling Name Presentation (CNAP) 4.1 Definition The CNAP supplementary service enables the called party to receive the calling name information of the calling party. 4.2 Description 4.2.1 Description This supplementary service provides for the ability to indicate the name information of the calling party to the called party at call set-up time for all incoming calls. The calling party takes no action to activate, initiate, or in any manner provide Calling Name Identification Presentation. However, the delivery of the calling name to the called party may be affected by other services subscribed to by the calling party. For example, if the calling party has subscribed to Calling Line Identification Restriction (CLIR), then the calling line identity as well as the calling name identity shall not be presented to the called party. 4.2.2 Applicability to telecommunication services The applicability of this supplementary service is defined in TS 22.004 [2]. CNAP is applicable to all telecommunication services except Short Message service. (for further study) 4.3 Normal procedures with successful outcome 4.3.1 Provision This supplementary service is provisioned for all Basic Services subscribed to and to which it is applicable, i.e. not provisioned for any subset of these Basic Services. This service shall be provided after pre-arrangement with the service provider. It may be provided on a subscription basis or be generally available. ETSI TS 122.096 V3.0.1 (2000-01) 3G TS 22.096 version 3.0.1 (3G TS 22.096 version 3.0.1 Release 1999) ETSI ETSI 3GPP 3G TS 22.096 V3.0.1 (1999-10) 7 3G TS 22.096 version 3.0.1 The override category controlling the name information is separate from the override category for the line identity information. It is left to the CNAP service provider to ensure that no discrepancy between these two override categories occurs. The handling of override category within a PLMN or between PLMNs shall follow the rules applying to the override category of the line identification services TS 22.081 [3]. 4.3.2 Withdrawal The CNAP supplementary service shall be withdrawn at the customer's request or for administrative reasons. 4.3.3 Registration Not applicable. 4.3.4 Erasure Not applicable. 4.3.5 Activation The CNAP supplementary service is activated as a result of provision. 4.3.6 Deactivation The CNAP supplementary service is deactivated as a result of withdrawal. 4.3.7 Invocation The network shall automatically invoke the CNAP supplementary service in the call set-up phase to the terminating CNAP subscriber. CNAP is invoked when the Calling Name Information associated with an incoming call is available and can be presented to the called party which has subscribed to CNAP. 4.3.8 Normal operation with successful outcome A user who has subscribed to the CNAP supplementary service and receives a call shall also receive the calling name information of the calling party, if available. The calling party takes no action to activate, initiate, or in any manner provide the calling name identity. When the CNAP service is subscribed and activated, the destination network provides the called subscriber with calling name information at call set-up on all incoming calls or during an active call for that particular call. In addition to, or instead of, the calling name identity, the subscriber may be given a presentation indicator with the relevant information. 4.3.9 Interrogation Status check The mobile subscriber can, by the appropriate control procedure, request from the network the status of this supplementary service. Upon receiving an interrogation request, the network shall send the status of this supplementary service to the subscriber. The information sent to the subscriber shall indicate whether the service is provided to her. The information sent in response to the interrogation of this supplementary service shall not imply the status of any other supplementary service. ETSI TS 122.096 V3.0.1 (2000-01) 3G TS 22.096 version 3.0.1 (3G TS 22.096 version 3.0.1 Release 1999) ETSI ETSI 3GPP 3G TS 22.096 V3.0.1 (1999-10) 8 3G TS 22.096 version 3.0.1 4.4 Exceptional procedures or unsuccessful outcome If the name identity for a specific caller is not available, then the CNAP subscriber shall be sent an indication that the name is unavailable. If the network has been unable to determine the appropriate name information within a predefined time, then the CNAP subscriber shall be sent an indication that the name is unavailable. The predefined time is a network dependent value such that the called user may receive the name in a timely manner prior to answer. If the calling name information is not available due to a system problem, such as signalling inter-working, then a standard error treatment shall be provided, which may be a visual display to the subscriber indicating the name is unavailable. 4.5 Alternate procedures The decision of whether the user-defined name stored in the handset should take precedence over the calling name identity provided by the network is a handset implementation issue. 4.6 Interactions with other supplementary services Only those supplementary services for which CNAP has any interactions are detailed in this clause. For all other supplementary services not mentioned in this clause no interactions were identified. 4.6.1 Calling Line Identification Presentation (CLIP) No interaction. 4.6.2 Calling Line Identification Restriction (CLIR) The CLIR supplementary service shall take precedence over the CNAP supplementary service, unless the called user has an override category. In this latter case, it is assumed that the override category for name information has been set so that the name information is presented to the called user. The Calling Line Identification Restriction (CLIR) information shall be used to restrict the delivery of the calling name to the called subscriber. That is, if the calling party has activated CLIR then instead of the calling name, a privacy indication shall be provided to the called subscriber, which may be a visual display indicating “private” (or Restricted) name. This method of restricting calling name shall not restrict the use or implementation of other calling name restriction methods when the calling party is a fixed subscriber. These methods used by fixed subscribers are outside the scope of this specification. 4.6.3 Call Forwarding Unconditional (CFU) For an incoming call to a subscriber with both CNAP and Call Forwarding Unconditional activated, the calling party name information shall not be displayed at the forwarding subscribers terminal. When a call has been forwarded and the forwarded-to user has been provided with the CNAP supplementary service, the forwarded-to user shall receive the name of the original calling party, if the calling party has not subscribed to or invoked the CLIR supplementary service. 4.6.4 Call Forwarding on mobile subscriber Busy (CFB) 4.6.4.1 Network Determined User Busy (NDUB) Same as the interaction with call forwarding unconditional. ETSI TS 122.096 V3.0.1 (2000-01) 3G TS 22.096 version 3.0.1 (3G TS 22.096 version 3.0.1 Release 1999) ETSI ETSI 3GPP 3G TS 22.096 V3.0.1 (1999-10) 9 3G TS 22.096 version 3.0.1 4.6.4.2 User Determined User Busy (UDUB) Same as interaction with call forwarding no reply. 4.6.5 Call Forwarding on No Reply (CFNRy) For an incoming call to a subscriber with both CNAP and Call Forwarding on No Reply activated, the calling party name information shall be displayed by the predefined time while the call is alerting. 4.6.6 Call Forwarding on mobile subscriber Not Reachable (CFNRc) Same as the interaction with call forwarding unconditional. 4.6.7 Call Waiting (CW) If the served mobile subscriber is provisioned with the CNAP service, the calling party name information shall be displayed to the subscriber at the notification of an incoming (waiting) call as for a normal incoming call. 4.6.9 Explicit Call Transfer (ECT) For Further Study. 4.6.10 Support of Private Numbering Plan (SPNP) The public number corresponding to the used PNP number is used to obtain the calling name information for delivery to the called party’s terminal. 4.6.11 Completion of Calls to Busy Subscriber (CCBS) No interaction. 4.6.12 enhanced Multi-Level Precedence and Pre-emption (eMLPP) No interaction. 4.7 Service functions for roamers CNAP should be available to a roaming subscriber. However, the serving system may elect to not offer the CNAP service to any subscriber. According to national network specific rules, the CNAP supplementary services need not be applicable, if at least one of the two parties is not an ISDN or PLMN subscriber. ETSI TS 122.096 V3.0.1 (2000-01) 3G TS 22.096 version 3.0.1 (3G TS 22.096 version 3.0.1 Release 1999) ETSI ETSI 3GPP 3G TS 22.096 V3.0.1 (1999-10) 10 3G TS 22.096 version 3.0.1 Annex A (informative): Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.96 7.0.0 Transferred to 3GPP SA1 SA#04 22.096 3.0.0 SA#05 22.096 3.0.0 001 R99 3.0.1 Editorial update of references for GSM/3GPP use. ETSI TS 122.096 V3.0.1 (2000-01) 3G TS 22.096 version 3.0.1 (3G TS 22.096 version 3.0.1 Release 1999) ETSI ETSI 11 ETSI ETSI TS 122 096 V3.0.1 (2000-01) (3G TS 22.096 version 3.0.1 Release 1999) History Document history V3.0.1 January 2000 Publication
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	2 References	................................................................................................................................................5
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	2.1 Normative references	......................................................................................................................................... 5
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	3 Definitions, symbols and abbreviations	...................................................................................................6
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	3.1 Definitions	......................................................................................................................................................... 6
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	3.2 Abbreviations	..................................................................................................................................................... 6
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	4 Description	...............................................................................................................................................6
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	4.1 Normal Operation	.............................................................................................................................................. 7
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	5 Applicability to telecommunication services	...........................................................................................7
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	6 Normal procedures with successful outcome	...........................................................................................8
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	6.1 Provision	............................................................................................................................................................ 8
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	6.2 Withdrawal	........................................................................................................................................................ 8
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	6.3 Registration	........................................................................................................................................................ 8
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	6.4 Erasure	............................................................................................................................................................... 9
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	6.5 Activation	.......................................................................................................................................................... 9
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	6.6 Deactivation	....................................................................................................................................................... 9
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	6.7 Invocation	.......................................................................................................................................................... 9
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	6.8 Interrogation	...................................................................................................................................................... 9
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	7 Exceptional procedures or unsuccessful outcome	.................................................................................10
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	7.1 Registration	...................................................................................................................................................... 10
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	7.2 Erasure	............................................................................................................................................................. 10
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	7.3 Interrogation	.................................................................................................................................................... 10
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	7.4 Invocation	........................................................................................................................................................ 11
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	8 Alternate procedures	..............................................................................................................................11
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	9 Charging requirements	...........................................................................................................................11
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	10 Interactions with supplementary services	..............................................................................................11
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	10.1 Call Forwarding unconditional	........................................................................................................................ 11
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	11 Interaction with Operator Determined barring	.......................................................................................11
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	12 Interaction with Optimal Routeing	........................................................................................................11
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	13 Interaction with CAMEL	.......................................................................................................................11
9e591c1fc23f1acc54fc8a7384f9a3d7	122 094	14 Interworking considerations	..................................................................................................................12 Annex A (informative) : Change history......................................................................................................13 History..............................................................................................................................................................14 ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 4 3G TS 22.094 version 3.1.0 Foreword This Technical Specification has been produced by the 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 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 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 5 3G TS 22.094 version 3.1.0 1 Scope The present document specifies the stage 1 description for the Follow Me feature. The Follow Me feature enables a mobile subscriber A to manipulate the Follow Me data of a party B in such a way that - under certain conditions - subsequent calls directed to party B will be forwarded to subscriber A. The feature is described from the service subscriber's and user's point of view, in particular: - the procedure for normal operation with successful outcome; - the action to be taken in exceptional circumstances; - the interaction with other GSM services and features. This TS does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate specifications. Any interaction with other services and/or networks not dealt with in this specification are outside the scope of this TS. 2 References References may be made to: a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in which case, subsequent revisions to the referenced document do not apply; or b) all versions up to and including the identified version (identified by "up to and including" before the version identity); or c) all versions subsequent to and including the identified version (identified by "onwards" following the version identity); or d) publications without mention of a specific version, in which case the latest version applies. A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. For this Release 1999 document, references to GSM documents are for Release 1999 versions (version 8.x.y). 2.1 Normative references This TS incorporates by dated and undated reference, provisions from other publications. These normative references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to or revisions of any of these publications apply to this TS only when incorporated in it by amendment or revision. For undated references, the latest edition of the publication referred to applies. [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Definitions, abbreviations and acronyms". [2] TS 22.004: "General on supplementary services". [4] TS 22.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)". [5] TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1". [6] TS 22.085: "Closed User Group (CUG) supplementary services - Stage 1". [7] TS 22.041: "Closed User Group (CUG) supplementary services - Stage 1". ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 6 3G TS 22.094 version 3.1.0 [8] TS 22.078: " Customized Applications for Mobile network Enhanced Logic (CAMEL); Service definition (Stage 1). [9] TS 22.079: "Support of Optimal Routeing (SOR); Service definition (Stage 1)". [10] TS 22.090: " Unstructured Supplementary Service Data (USSD) Stage 1" [11] GSM 02.31: "Fraud Information Gathering System (FIGS); Service description - Stage 1" [12] TS 22.101: "UMTS Service Principles". 3 Definitions, symbols and abbreviations 3.1 Definitions initiating subscriber: the mobile subscriber which modifies the Follow Me data of the remote party. remote party: Is characterised by a number in E.164 format defined in the numbering plan of a PLMN operator. The Follow Me feature enables the initiating subscriber to modify the Follow Me data associated with this number. In general this number is not assigned to a subscriber. In particular cases the remote party is a subscriber of the PLMN and the number denotes her basic MSISDN. FM service supervisor: Is an initiating subscriber who is allowed to modify the Follow Me data of a remote party who has been registered to another initiating subscriber for the Follow Me application. The FM service supervisor shall be authorised by her network operator. 3.2 Abbreviations For the purposes of this TS the following abbreviations apply, in addition, abbreviations used in this TS are listed in GSM 01.04 [1]. FM Follow Me feature 4 Description Follow Me enables an initiating mobile subscriber A to have control over the Follow Me data of a remote party B. Initiating Subscriber A shall be able to manipulate the Follow Me data of remote party B such that subsequent calls directed to remote party B are forwarded to initiating subscriber A. Initiating subscriber A needs to have FM provisioned by her service provider. In case remote party B is a subscriber she needs to have FM provisioned by her service provider too. The FM service supervisor shall be able to modify the Follow Me data of the remote party who has been registered to another initiating subscriber. It remains in the responsibility of a FM provisioning service provider to confine a.) the range of remote parties for which a FM provisioned subscriber may become initiating subscriber b.) the range of potential initiating subscribers for a remote party. The mobile subscriber who has been provisioned Follow Me is able to use the following control operations: Registration available to the initiating subscriber Interrogation available to the initiating and remote party in case the remote party corresponds to a subscriber Erasure available to the initiating and remote party in case the remote party corresponds to a subscriber ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 7 3G TS 22.094 version 3.1.0 (There is no explicit activation or deactivation.) The FM service supervisor is able to use the following control operations: Interrogation Erasure (forced erasure) NOTE 1: The functionality of the Follow Me feature is equivalent to the Call Forwarding Unconditional Supplementary Service (see TS 22.082 [5]), controlled by initiating subscriber A and effecting remote party B. NOTE 2: The Follow Me feature is designed in such a way that the requirements of "functional addressing", which is needed for GSM-Railway operators, can be met. The concept of "functional addressing" enables a subscriber to set up a call to a "function" - e.g. the conductor - on a "train". The Follow Me feature identifies this "function" with the remote party B. Consequently a "functional number" is the equivalent to the number of remote party B (e.g. the MSISDN of a subscriber B). A call to that "functional number" (the conductor on a particular train - to stay with the example) will be forwarded to the MS of the person, who is on duty as a conductor at this time for this train. In the context of the Follow Me feature, this person (the train conductor) constitutes the "initiating subscriber" A, who has registered Follow Me with respect to the remote party B (the "function" train conductor). 4.1 Normal Operation Due to reduced security requirements to the Follow Me feature the service shall not be offered in standard operations of public GSM networks. In railway operations it must be enabled by definitive action on the part of the operator. Fraud Information Gathering System (FIGS) as specified in [11] can be used to protect in CAMEL based inter-working networks. The Follow Me feature shall be controlled by means of Subscriber Controlled Input using USSD. 5 Applicability to telecommunication services GSM 02.01 describes the principles of the Telecommunication services provided in a GSM PLMN. It also defines the concepts of Telecommunication services and describes their characterization by appropriate attributes. Bearer services and Teleservices, which are offered by a PLMN in connection with other networks, are defined in TS 22.002, GSM 02.03 and TS 22.101. A list of basic service groups can be found in GSM TS 22.004. Follow Me is applicable to the following telecommunication services: ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 8 3G TS 22.094 version 3.1.0 Table 1: Applicability of the Follow Me feature to telecommunication services Feature Telephony Emergency Call SMS PTP SMS-CB Fax cct Data PAD/Packet Access Voice Group Services TS11 TS12 TS21 TS22 TS 23 TS 6x BS2x, BS3x BS4x BS5x TS 91 TS 92 Follow Me Yes Yes Yes No1 No1 NOTE 1: The feature is in general not applicable for Voice Group Services. However a dispatcher may be an initiating subscriber or a remote party for the Follow Me feature. EDITOR's Note: The applicability of FM to SMS is for further study. 6 Normal procedures with successful outcome 6.1 Provision Follow Me shall be provided after prior arrangement with the service provider. Follow Me will be provisioned for all Basic Services subscribed to and to which it is applicable. NOTES: - A Follow Me provision is required for the initiating subscriber and for the remote party in case the remote party corresponds to a subscriber. - If Follow Me is provisioned for a mobile subscriber she may assume the role of an initiating subscriber and/or the role of a remote party. - A Follow Me provisioning service provider may confine: a.) the range of remote parties for which a FM provisioned subscriber may become initiating subscriber b.) the range of potential initiating subscribers for a remote party. c) the range of remote parties for which a FM provisioned subscriber may become FM service supervisor. NOTE: (Health warning on security) The Follow Me feature is designed in such a way as to meet the security requirements of GSM-Railway operators. If the Follow Me feature is to be used by other operators - in particular if the remote party corresponds to a subscriber - operators are strongly advised to care for additional suitable security mechanisms to protect the remote party from potential harm by misuse of FM. These mechanisms are out of scope of this specification. To support such mechanisms the possibility is foreseen to convey additional operator-specific information in the registration, interrogation and erasure procedures to the PLMN of the remote party. It should however be noted, that this is not a very secure mechanism. Operators should try to use existing security mechanisms where possible 6.2 Withdrawal Follow Me will be withdrawn at the subscriber's request or for administrative reasons. 6.3 Registration Follow Me shall be registered with an appropriate control procedure by the initiating subscriber. The initiating Subscriber registers the Follow Me feature with respect to a particular remote party. The initiating subscriber shall provide the following information to the network: the number of the remote party (e.g. the Basic MSISDN of a subscriber); ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 9 3G TS 22.094 version 3.1.0 The initiating subscriber shall receive an indication if the FM registration request was accepted or rejected by the network. As an operator's option additional information (such as passwords) for registration may be required from the initiating subscriber. The registration procedure shall transport this information from the initiating subscriber to the network of the remote party. This information shall be coded as a USSD string with a length not exceeding 30 characters. The content of this information and the use of it are out of scope of this specification. NOTE 1: The Follow Me feature may, at an instant, be registered to an initiating subscriber with respect to several remote parties. Conversely, a remote party can be registered only to one initiating subscriber at a time. 6.4 Erasure A previous FM registration can be erased in either of the following ways: a) The initiating subscriber can specifically erase her previous registration with an appropriate control procedure. b) In case the remote party corresponds to a subscriber the remote party can erase any previous registration with an appropriate control procedure. c) The FM service supervisor can erase any previous registration to any remote party with an appropriate control procedure (forced erasure). The subscriber who initiates the FM erase request shall be informed of the outcome of the request by the network. As an operator's option additional information (such as passwords) for erasure may be required from the subscriber. The registration procedure shall transport this information from the subscriber to the network of the remote party. This information shall be coded as a USSD string with a length not exceeding 30 characters. The content of this information and the use of it are out of scope of this specification. 6.5 Activation Follow Me is activated by registration. 6.6 Deactivation Follow Me is deactivated by erasure. 6.7 Invocation Follow Me is automatically invoked by the network if it was previously registered. If Follow Me is registered all incoming calls to the remote party will be forwarded to the initiating subscriber by network invocation. When Follow Me is active and operative and if the remote party is a subscriber, the ability of the remote party to originate calls is not affected. 6.8 Interrogation An initiating subscriber (also the FM service supervisor) shall be able to interrogate the Follow Me data of any remote party, for which she is authorised to become initiating subscriber. In case the remote party corresponds to a subscriber the remote party shall be able to interrogate her own Follow Me data stored in the network. The network shall return the basic MSISDN of the initiating subscriber for which the remote party is registered to Follow Me. ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 10 3G TS 22.094 version 3.1.0 As an operator's option additional information (such as passwords) for interrogation may be required from the subscriber. The registration procedure shall transport this information from the subscriber to the network of the remote party. This information shall be coded as a USSD string with a length not exceeding 30 characters. The content of this information and the use of it are out of scope of this specification. 7 Exceptional procedures or unsuccessful outcome 7.1 Registration If the system cannot accept a registration request, the initiating subscriber shall receive a notification that Follow Me registration was not successful. Possible causes are: - insufficient information; - feature not provisioned to initiating subscriber; - feature not provisioned to remote party (in case the remote party is a subscriber); - conflicting situation with supplementary services (e.g. incoming call barring has been activated); – remote party already registered to a different initiating subscriber – insufficient authorisation for initiating subscriber or remote party 7.2 Erasure If the network cannot accept a mobile initiating or remote subscriber's request for erasure, cause will be returned to the subscriber, such as: - insufficient information; - remote party not registered – remote party registered to a different initiating subscriber – insufficient authorisation for initiating subscriber or remote party - feature not provisioned to initiating subscriber; - feature not provisioned to remote party (in case the remote party is a subscriber); 7.3 Interrogation If the network cannot accept a mobile initiating or remote subscriber's request for interrogation, cause will be returned to the subscriber, such as: - insufficient information; – insufficient authorisation for initiating subscriber or remote party – feature not provisioned to initiating subscriber; - feature not provisioned to remote party (in case the remote party is a subscriber); ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 11 3G TS 22.094 version 3.1.0 7.4 Invocation Within a PLMN or different PLMNs the number of tandem forwarding connections (including call forwarding, call deflection, Follow Me) should be limited. The maximum number of tandem forwarding connections should be limited to a value between 1 and 5. This is to prevent infinite looping. If the limit of successive forwardings of a call has already been reached, an unsuccessful call set up indication is sent backwards. If the call cannot be completed to the Follow Me destination, then the network will clear the forwarded part of the call and an unsuccessful call set up indication is sent backwards. 8 Alternate procedures None identified. 9 Charging requirements None identified. 10 Interactions with supplementary services Interactions of the Follow Me feature with supplementary services may occur only for the remote party. The interactions of the Follow Me feature with supplementary services other than Call Forwarding Unconditional (CFU) are the same as the interactions of CFU with supplementary services (see TS 22.082 [5]). NOTE: The “served mobile subscriber” in TS 22.082 [5] corresponds to the “remote party” in this document. The “forwarded-to subscriber” in TS 22.082 [5] corresponds to the “initiating subscriber” in this document 10.1 Call Forwarding unconditional Follow Me and the Call Forwarding Unconditional Supplementary Service are mutually exclusive. That is: If Follow Me is registered with respect to a remote party, registration or activation of Call forwarding unconditional by the remote party is rejected. The remote party shall be informed of this incompatibility. If Call forwarding unconditional is registered or active for the remote party, registration of Follow Me is rejected. The initiating subscriber shall be informed of this incompatibility. 11 Interaction with Operator Determined barring Same as interaction between Operator Determined barring and call forwarding unconditional as defined in TS 22.041. 12 Interaction with Optimal Routeing Same as interaction between Optimal Routeing and call forwarding unconditional as defined in TS 22.079. 13 Interaction with CAMEL Same as interaction between CAMEL and call forwarding unconditional as defined in TS 22.078. ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 12 3G TS 22.094 version 3.1.0 If a forwarded call due to invocation of Follow Me meets an interworking situation, then an interworking indication should be sent to the calling party. When interworking with non-PLMN or non-ISDN networks, tones and announcements will be required. NOTE1: The number of times a call has been forwarded once it has exited the PLMN or ISDN may not be limited. NOTE2: Tones and/or announcements should not be provided to the calling party if the information transfer capability is set to UDI. ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 13 3G TS 22.094 version 3.1.0 Annex A (informative) : Change history Change history SMG No. / TSG SA# TDoc. No. CR. No. Section affected New version Subject/Comments TSGT SA#6 SP99-595 001 3.1, 4, 6.1, 6.4, 6.8 Version 3.1.0 Introduction of the rôle of a “ Follow Me service supervisor:” ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 14 ETSI ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) History Document history V3.1.0 January 2000 Publication
e36388c5c871ca9e9c179d4fdecef43c	122 093	1 Scope	........................................................................................................................................................5
e36388c5c871ca9e9c179d4fdecef43c	122 093	2 References	................................................................................................................................................6
e36388c5c871ca9e9c179d4fdecef43c	122 093	3 Definitions and abbreviations	..................................................................................................................6
e36388c5c871ca9e9c179d4fdecef43c	122 093	3.1 Definitions	......................................................................................................................................................... 6
e36388c5c871ca9e9c179d4fdecef43c	122 093	3.2 Abbreviations	..................................................................................................................................................... 7
e36388c5c871ca9e9c179d4fdecef43c	122 093	4 Description	...............................................................................................................................................8
e36388c5c871ca9e9c179d4fdecef43c	122 093	4.1 Applicability to telecommunications services	................................................................................................... 8
e36388c5c871ca9e9c179d4fdecef43c	122 093	5 Normal procedures with successful outcome	...........................................................................................8
e36388c5c871ca9e9c179d4fdecef43c	122 093	5.1 Provision	............................................................................................................................................................ 8
e36388c5c871ca9e9c179d4fdecef43c	122 093	5.1.1 Subscriber A	................................................................................................................................................. 8
e36388c5c871ca9e9c179d4fdecef43c	122 093	5.1.2 Subscriber B	................................................................................................................................................. 8
e36388c5c871ca9e9c179d4fdecef43c	122 093	5.2 Withdrawal	........................................................................................................................................................ 8
e36388c5c871ca9e9c179d4fdecef43c	122 093	5.3 Registration	........................................................................................................................................................ 8
e36388c5c871ca9e9c179d4fdecef43c	122 093	5.4 Erasure	............................................................................................................................................................... 8
e36388c5c871ca9e9c179d4fdecef43c	122 093	5.5 Activation	.......................................................................................................................................................... 8
e36388c5c871ca9e9c179d4fdecef43c	122 093	5.6 Deactivation	....................................................................................................................................................... 9
e36388c5c871ca9e9c179d4fdecef43c	122 093	5.7 Invocation and operation	................................................................................................................................... 9
e36388c5c871ca9e9c179d4fdecef43c	122 093	5.8 Interrogation	.................................................................................................................................................... 10
e36388c5c871ca9e9c179d4fdecef43c	122 093	6 Exceptional procedures or unsuccessful outcome	.................................................................................10
e36388c5c871ca9e9c179d4fdecef43c	122 093	6.1 Registration	...................................................................................................................................................... 10
e36388c5c871ca9e9c179d4fdecef43c	122 093	6.2 Erasure	............................................................................................................................................................. 10
e36388c5c871ca9e9c179d4fdecef43c	122 093	6.3 Activation	........................................................................................................................................................ 10
e36388c5c871ca9e9c179d4fdecef43c	122 093	6.4 Deactivation	..................................................................................................................................................... 11
e36388c5c871ca9e9c179d4fdecef43c	122 093	6.5 Invocation and operation	................................................................................................................................. 11
e36388c5c871ca9e9c179d4fdecef43c	122 093	6.5.1 Exceptional situation at destination B's side:	............................................................................................. 11
e36388c5c871ca9e9c179d4fdecef43c	122 093	6.5.2 Exceptional situation at subscriber A's side:	.............................................................................................. 12
e36388c5c871ca9e9c179d4fdecef43c	122 093	6.5.3 Exceptional situations in the network	........................................................................................................ 13
e36388c5c871ca9e9c179d4fdecef43c	122 093	7 Interaction with other supplementary services	......................................................................................14
e36388c5c871ca9e9c179d4fdecef43c	122 093	7.1 Calling line identification presentation	............................................................................................................ 14
e36388c5c871ca9e9c179d4fdecef43c	122 093	7.2 Calling line identification restriction	............................................................................................................... 14
e36388c5c871ca9e9c179d4fdecef43c	122 093	7.3 Connected line identification presentation	....................................................................................................... 14
e36388c5c871ca9e9c179d4fdecef43c	122 093	7.4 Connected line identification restriction	.......................................................................................................... 14
e36388c5c871ca9e9c179d4fdecef43c	122 093	7.5 Call Forwarding Unconditional (CFU)	............................................................................................................ 14
e36388c5c871ca9e9c179d4fdecef43c	122 093	7.6 Call Forwarding on mobile subscriber Busy (CFB)	........................................................................................ 14
e36388c5c871ca9e9c179d4fdecef43c	122 093	7.7 Call Forwarding on No Reply (CFNRy)	.......................................................................................................... 15
e36388c5c871ca9e9c179d4fdecef43c	122 093	7.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc)	..................................................................... 15
e36388c5c871ca9e9c179d4fdecef43c	122 093	7.9 Call waiting	...................................................................................................................................................... 15
e36388c5c871ca9e9c179d4fdecef43c	122 093	7.10 Call hold	.......................................................................................................................................................... 15
e36388c5c871ca9e9c179d4fdecef43c	122 093	7.11 Multiparty services	.......................................................................................................................................... 15
e36388c5c871ca9e9c179d4fdecef43c	122 093	7.12 Closed user group	............................................................................................................................................ 15

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.2.1 Description

................................................................................................................................................... 6

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.2.2 Applicability to telecommunication services

............................................................................................... 6

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.3 Normal procedures with successful outcome

..................................................................................................... 6

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.3.1 Provision

...................................................................................................................................................... 6

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.3.2 Withdrawal

................................................................................................................................................... 7

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.3.3 Registration

.................................................................................................................................................. 7

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.3.4 Erasure

......................................................................................................................................................... 7

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.3.5 Activation

..................................................................................................................................................... 7

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.3.6 Deactivation

................................................................................................................................................. 7

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.3.7 Invocation

..................................................................................................................................................... 7

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.3.8 Normal operation with successful outcome

................................................................................................. 7

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.3.9 Interrogation

................................................................................................................................................. 7

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.4 Exceptional procedures or unsuccessful outcome

.............................................................................................. 8

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.5 Alternate procedures

.......................................................................................................................................... 8

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.6 Interactions with other supplementary services

................................................................................................. 8

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.6.1 Calling Line Identification Presentation (CLIP)

.......................................................................................... 8

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.6.2 Calling Line Identification Restriction (CLIR)

............................................................................................ 8

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.6.3 Call Forwarding Unconditional (CFU)

........................................................................................................ 8

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.6.4 Call Forwarding on mobile subscriber Busy (CFB)

..................................................................................... 8

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.6.4.1 Network Determined User Busy (NDUB)

.............................................................................................. 8

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.6.4.2 User Determined User Busy (UDUB)

.................................................................................................... 9

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.6.5 Call Forwarding on No Reply (CFNRy)

...................................................................................................... 9

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.6.6 Call Forwarding on mobile subscriber Not Reachable (CFNRc)

................................................................. 9

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.6.7 Call Waiting (CW)

....................................................................................................................................... 9

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.6.9 Explicit Call Transfer (ECT)

........................................................................................................................ 9

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.6.10 Support of Private Numbering Plan (SPNP)

................................................................................................ 9

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.6.11 Completion of Calls to Busy Subscriber (CCBS)

........................................................................................ 9

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.6.12 enhanced Multi-Level Precedence and Pre-emption (eMLPP)

.................................................................... 9

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.7 Service functions for roamers

............................................................................................................................ 9

c4dcc5fb97678154a0beb0ac23aec589

122 096

4.8 Interworking considerations

............................................................................................................................... 9 Annex A (informative): Change history.......................................................................................................10 History..............................................................................................................................................................11 ETSI TS 122.096 V3.0.1 (2000-01) (3G TS 22.096 version 3.0.1 Release 1999) ETSI 3GPP 3G TS 22.096 V3.0.1 (1999-10) 4 3G TS 22.096 version 3.0.1 Foreword This Technical Specification has been produced by the 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 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 122.096 V3.0.1 (2000-01) 3G TS 22.096 version 3.0.1 (3G TS 22.096 version 3.0.1 Release 1999) ETSI ETSI 3GPP 3G TS 22.096 V3.0.1 (1999-10) 5 3G TS 22.096 version 3.0.1 1 Scope The present document describes the supplementary services belonging to the group Name Identification supplementary services. The general aspects, including definitions and recommended provision, of the description of the supplementary services are given in TS 22.004. The group of Name Identification supplementary services is divided into the following supplementary services: CNAP Calling Name Presentation (clause 4). 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. • For this Release 1999 document, references to GSM documents are for Release 1999 versions (version 8.x.y). [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] TS 22.004: "General on Supplementary Services". [3] TS 22.081: "Line Identification Supplementary Services - Stage 1". [4] TR 21.905: "Vocabulary for 3GPP Specifications". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following definitions apply: Definition of name identity: The name identity is made up of the following information unit: - The name of the mobile subscriber for the purpose of calling name presentation - up to 80 characters of information associated with a specific calling party. The calling name identity is the name identity of the calling party. Definition of Presentation Indicator: In addition to or instead of the name identity, the network may give a Presentation Indicator (PI) to the called mobile subscriber of the CNAP service. The following information may be given: - Presentation Indicator (PI) showing: a) presentation restricted, or ETSI TS 122.096 V3.0.1 (2000-01) 3G TS 22.096 version 3.0.1 (3G TS 22.096 version 3.0.1 Release 1999) ETSI ETSI 3GPP 3G TS 22.096 V3.0.1 (1999-10) 6 3G TS 22.096 version 3.0.1 b) name unavailable. The name identity of a PLMN subscriber shall always be provided by the network. Calling Party: The calling party is the originating party. Called Party: The called party is the terminating party. The CNAP service is provided to the called party. Calling Name Information: The calling name information of the calling party includes either the calling name identity or an indication of privacy or unavailability. 3.2 Abbreviations In addition to the following abbreviations used in the present document, abbreviations are listed in GSM 01.04. CNAP Calling Name Presentation 4 Calling Name Presentation (CNAP) 4.1 Definition The CNAP supplementary service enables the called party to receive the calling name information of the calling party. 4.2 Description 4.2.1 Description This supplementary service provides for the ability to indicate the name information of the calling party to the called party at call set-up time for all incoming calls. The calling party takes no action to activate, initiate, or in any manner provide Calling Name Identification Presentation. However, the delivery of the calling name to the called party may be affected by other services subscribed to by the calling party. For example, if the calling party has subscribed to Calling Line Identification Restriction (CLIR), then the calling line identity as well as the calling name identity shall not be presented to the called party. 4.2.2 Applicability to telecommunication services The applicability of this supplementary service is defined in TS 22.004 [2]. CNAP is applicable to all telecommunication services except Short Message service. (for further study) 4.3 Normal procedures with successful outcome 4.3.1 Provision This supplementary service is provisioned for all Basic Services subscribed to and to which it is applicable, i.e. not provisioned for any subset of these Basic Services. This service shall be provided after pre-arrangement with the service provider. It may be provided on a subscription basis or be generally available. ETSI TS 122.096 V3.0.1 (2000-01) 3G TS 22.096 version 3.0.1 (3G TS 22.096 version 3.0.1 Release 1999) ETSI ETSI 3GPP 3G TS 22.096 V3.0.1 (1999-10) 7 3G TS 22.096 version 3.0.1 The override category controlling the name information is separate from the override category for the line identity information. It is left to the CNAP service provider to ensure that no discrepancy between these two override categories occurs. The handling of override category within a PLMN or between PLMNs shall follow the rules applying to the override category of the line identification services TS 22.081 [3]. 4.3.2 Withdrawal The CNAP supplementary service shall be withdrawn at the customer's request or for administrative reasons. 4.3.3 Registration Not applicable. 4.3.4 Erasure Not applicable. 4.3.5 Activation The CNAP supplementary service is activated as a result of provision. 4.3.6 Deactivation The CNAP supplementary service is deactivated as a result of withdrawal. 4.3.7 Invocation The network shall automatically invoke the CNAP supplementary service in the call set-up phase to the terminating CNAP subscriber. CNAP is invoked when the Calling Name Information associated with an incoming call is available and can be presented to the called party which has subscribed to CNAP. 4.3.8 Normal operation with successful outcome A user who has subscribed to the CNAP supplementary service and receives a call shall also receive the calling name information of the calling party, if available. The calling party takes no action to activate, initiate, or in any manner provide the calling name identity. When the CNAP service is subscribed and activated, the destination network provides the called subscriber with calling name information at call set-up on all incoming calls or during an active call for that particular call. In addition to, or instead of, the calling name identity, the subscriber may be given a presentation indicator with the relevant information. 4.3.9 Interrogation Status check The mobile subscriber can, by the appropriate control procedure, request from the network the status of this supplementary service. Upon receiving an interrogation request, the network shall send the status of this supplementary service to the subscriber. The information sent to the subscriber shall indicate whether the service is provided to her. The information sent in response to the interrogation of this supplementary service shall not imply the status of any other supplementary service. ETSI TS 122.096 V3.0.1 (2000-01) 3G TS 22.096 version 3.0.1 (3G TS 22.096 version 3.0.1 Release 1999) ETSI ETSI 3GPP 3G TS 22.096 V3.0.1 (1999-10) 8 3G TS 22.096 version 3.0.1 4.4 Exceptional procedures or unsuccessful outcome If the name identity for a specific caller is not available, then the CNAP subscriber shall be sent an indication that the name is unavailable. If the network has been unable to determine the appropriate name information within a predefined time, then the CNAP subscriber shall be sent an indication that the name is unavailable. The predefined time is a network dependent value such that the called user may receive the name in a timely manner prior to answer. If the calling name information is not available due to a system problem, such as signalling inter-working, then a standard error treatment shall be provided, which may be a visual display to the subscriber indicating the name is unavailable. 4.5 Alternate procedures The decision of whether the user-defined name stored in the handset should take precedence over the calling name identity provided by the network is a handset implementation issue. 4.6 Interactions with other supplementary services Only those supplementary services for which CNAP has any interactions are detailed in this clause. For all other supplementary services not mentioned in this clause no interactions were identified. 4.6.1 Calling Line Identification Presentation (CLIP) No interaction. 4.6.2 Calling Line Identification Restriction (CLIR) The CLIR supplementary service shall take precedence over the CNAP supplementary service, unless the called user has an override category. In this latter case, it is assumed that the override category for name information has been set so that the name information is presented to the called user. The Calling Line Identification Restriction (CLIR) information shall be used to restrict the delivery of the calling name to the called subscriber. That is, if the calling party has activated CLIR then instead of the calling name, a privacy indication shall be provided to the called subscriber, which may be a visual display indicating “private” (or Restricted) name. This method of restricting calling name shall not restrict the use or implementation of other calling name restriction methods when the calling party is a fixed subscriber. These methods used by fixed subscribers are outside the scope of this specification. 4.6.3 Call Forwarding Unconditional (CFU) For an incoming call to a subscriber with both CNAP and Call Forwarding Unconditional activated, the calling party name information shall not be displayed at the forwarding subscribers terminal. When a call has been forwarded and the forwarded-to user has been provided with the CNAP supplementary service, the forwarded-to user shall receive the name of the original calling party, if the calling party has not subscribed to or invoked the CLIR supplementary service. 4.6.4 Call Forwarding on mobile subscriber Busy (CFB) 4.6.4.1 Network Determined User Busy (NDUB) Same as the interaction with call forwarding unconditional. ETSI TS 122.096 V3.0.1 (2000-01) 3G TS 22.096 version 3.0.1 (3G TS 22.096 version 3.0.1 Release 1999) ETSI ETSI 3GPP 3G TS 22.096 V3.0.1 (1999-10) 9 3G TS 22.096 version 3.0.1 4.6.4.2 User Determined User Busy (UDUB) Same as interaction with call forwarding no reply. 4.6.5 Call Forwarding on No Reply (CFNRy) For an incoming call to a subscriber with both CNAP and Call Forwarding on No Reply activated, the calling party name information shall be displayed by the predefined time while the call is alerting. 4.6.6 Call Forwarding on mobile subscriber Not Reachable (CFNRc) Same as the interaction with call forwarding unconditional. 4.6.7 Call Waiting (CW) If the served mobile subscriber is provisioned with the CNAP service, the calling party name information shall be displayed to the subscriber at the notification of an incoming (waiting) call as for a normal incoming call. 4.6.9 Explicit Call Transfer (ECT) For Further Study. 4.6.10 Support of Private Numbering Plan (SPNP) The public number corresponding to the used PNP number is used to obtain the calling name information for delivery to the called party’s terminal. 4.6.11 Completion of Calls to Busy Subscriber (CCBS) No interaction. 4.6.12 enhanced Multi-Level Precedence and Pre-emption (eMLPP) No interaction. 4.7 Service functions for roamers CNAP should be available to a roaming subscriber. However, the serving system may elect to not offer the CNAP service to any subscriber. According to national network specific rules, the CNAP supplementary services need not be applicable, if at least one of the two parties is not an ISDN or PLMN subscriber. ETSI TS 122.096 V3.0.1 (2000-01) 3G TS 22.096 version 3.0.1 (3G TS 22.096 version 3.0.1 Release 1999) ETSI ETSI 3GPP 3G TS 22.096 V3.0.1 (1999-10) 10 3G TS 22.096 version 3.0.1 Annex A (informative): Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.96 7.0.0 Transferred to 3GPP SA1 SA#04 22.096 3.0.0 SA#05 22.096 3.0.0 001 R99 3.0.1 Editorial update of references for GSM/3GPP use. ETSI TS 122.096 V3.0.1 (2000-01) 3G TS 22.096 version 3.0.1 (3G TS 22.096 version 3.0.1 Release 1999) ETSI ETSI 11 ETSI ETSI TS 122 096 V3.0.1 (2000-01) (3G TS 22.096 version 3.0.1 Release 1999) History Document history V3.0.1 January 2000 Publication

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

2 References

................................................................................................................................................5

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

2.1 Normative references

......................................................................................................................................... 5

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

3 Definitions, symbols and abbreviations

...................................................................................................6

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

3.1 Definitions

......................................................................................................................................................... 6

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

3.2 Abbreviations

..................................................................................................................................................... 6

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

4 Description

...............................................................................................................................................6

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

4.1 Normal Operation

.............................................................................................................................................. 7

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

5 Applicability to telecommunication services

...........................................................................................7

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

6 Normal procedures with successful outcome

...........................................................................................8

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

6.1 Provision

............................................................................................................................................................ 8

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

6.2 Withdrawal

........................................................................................................................................................ 8

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

6.3 Registration

........................................................................................................................................................ 8

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

6.4 Erasure

............................................................................................................................................................... 9

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

6.5 Activation

.......................................................................................................................................................... 9

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

6.6 Deactivation

....................................................................................................................................................... 9

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

6.7 Invocation

.......................................................................................................................................................... 9

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

6.8 Interrogation

...................................................................................................................................................... 9

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

7 Exceptional procedures or unsuccessful outcome

.................................................................................10

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

7.1 Registration

...................................................................................................................................................... 10

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

7.2 Erasure

............................................................................................................................................................. 10

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

7.3 Interrogation

.................................................................................................................................................... 10

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

7.4 Invocation

........................................................................................................................................................ 11

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

8 Alternate procedures

..............................................................................................................................11

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

9 Charging requirements

...........................................................................................................................11

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

10 Interactions with supplementary services

..............................................................................................11

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

10.1 Call Forwarding unconditional

........................................................................................................................ 11

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

11 Interaction with Operator Determined barring

.......................................................................................11

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

12 Interaction with Optimal Routeing

........................................................................................................11

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

13 Interaction with CAMEL

.......................................................................................................................11

9e591c1fc23f1acc54fc8a7384f9a3d7

122 094

14 Interworking considerations

..................................................................................................................12 Annex A (informative) : Change history......................................................................................................13 History..............................................................................................................................................................14 ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 4 3G TS 22.094 version 3.1.0 Foreword This Technical Specification has been produced by the 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 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 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 5 3G TS 22.094 version 3.1.0 1 Scope The present document specifies the stage 1 description for the Follow Me feature. The Follow Me feature enables a mobile subscriber A to manipulate the Follow Me data of a party B in such a way that - under certain conditions - subsequent calls directed to party B will be forwarded to subscriber A. The feature is described from the service subscriber's and user's point of view, in particular: - the procedure for normal operation with successful outcome; - the action to be taken in exceptional circumstances; - the interaction with other GSM services and features. This TS does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate specifications. Any interaction with other services and/or networks not dealt with in this specification are outside the scope of this TS. 2 References References may be made to: a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in which case, subsequent revisions to the referenced document do not apply; or b) all versions up to and including the identified version (identified by "up to and including" before the version identity); or c) all versions subsequent to and including the identified version (identified by "onwards" following the version identity); or d) publications without mention of a specific version, in which case the latest version applies. A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. For this Release 1999 document, references to GSM documents are for Release 1999 versions (version 8.x.y). 2.1 Normative references This TS incorporates by dated and undated reference, provisions from other publications. These normative references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to or revisions of any of these publications apply to this TS only when incorporated in it by amendment or revision. For undated references, the latest edition of the publication referred to applies. [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Definitions, abbreviations and acronyms". [2] TS 22.004: "General on supplementary services". [4] TS 22.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)". [5] TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1". [6] TS 22.085: "Closed User Group (CUG) supplementary services - Stage 1". [7] TS 22.041: "Closed User Group (CUG) supplementary services - Stage 1". ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 6 3G TS 22.094 version 3.1.0 [8] TS 22.078: " Customized Applications for Mobile network Enhanced Logic (CAMEL); Service definition (Stage 1). [9] TS 22.079: "Support of Optimal Routeing (SOR); Service definition (Stage 1)". [10] TS 22.090: " Unstructured Supplementary Service Data (USSD) Stage 1" [11] GSM 02.31: "Fraud Information Gathering System (FIGS); Service description - Stage 1" [12] TS 22.101: "UMTS Service Principles". 3 Definitions, symbols and abbreviations 3.1 Definitions initiating subscriber: the mobile subscriber which modifies the Follow Me data of the remote party. remote party: Is characterised by a number in E.164 format defined in the numbering plan of a PLMN operator. The Follow Me feature enables the initiating subscriber to modify the Follow Me data associated with this number. In general this number is not assigned to a subscriber. In particular cases the remote party is a subscriber of the PLMN and the number denotes her basic MSISDN. FM service supervisor: Is an initiating subscriber who is allowed to modify the Follow Me data of a remote party who has been registered to another initiating subscriber for the Follow Me application. The FM service supervisor shall be authorised by her network operator. 3.2 Abbreviations For the purposes of this TS the following abbreviations apply, in addition, abbreviations used in this TS are listed in GSM 01.04 [1]. FM Follow Me feature 4 Description Follow Me enables an initiating mobile subscriber A to have control over the Follow Me data of a remote party B. Initiating Subscriber A shall be able to manipulate the Follow Me data of remote party B such that subsequent calls directed to remote party B are forwarded to initiating subscriber A. Initiating subscriber A needs to have FM provisioned by her service provider. In case remote party B is a subscriber she needs to have FM provisioned by her service provider too. The FM service supervisor shall be able to modify the Follow Me data of the remote party who has been registered to another initiating subscriber. It remains in the responsibility of a FM provisioning service provider to confine a.) the range of remote parties for which a FM provisioned subscriber may become initiating subscriber b.) the range of potential initiating subscribers for a remote party. The mobile subscriber who has been provisioned Follow Me is able to use the following control operations: Registration available to the initiating subscriber Interrogation available to the initiating and remote party in case the remote party corresponds to a subscriber Erasure available to the initiating and remote party in case the remote party corresponds to a subscriber ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 7 3G TS 22.094 version 3.1.0 (There is no explicit activation or deactivation.) The FM service supervisor is able to use the following control operations: Interrogation Erasure (forced erasure) NOTE 1: The functionality of the Follow Me feature is equivalent to the Call Forwarding Unconditional Supplementary Service (see TS 22.082 [5]), controlled by initiating subscriber A and effecting remote party B. NOTE 2: The Follow Me feature is designed in such a way that the requirements of "functional addressing", which is needed for GSM-Railway operators, can be met. The concept of "functional addressing" enables a subscriber to set up a call to a "function" - e.g. the conductor - on a "train". The Follow Me feature identifies this "function" with the remote party B. Consequently a "functional number" is the equivalent to the number of remote party B (e.g. the MSISDN of a subscriber B). A call to that "functional number" (the conductor on a particular train - to stay with the example) will be forwarded to the MS of the person, who is on duty as a conductor at this time for this train. In the context of the Follow Me feature, this person (the train conductor) constitutes the "initiating subscriber" A, who has registered Follow Me with respect to the remote party B (the "function" train conductor). 4.1 Normal Operation Due to reduced security requirements to the Follow Me feature the service shall not be offered in standard operations of public GSM networks. In railway operations it must be enabled by definitive action on the part of the operator. Fraud Information Gathering System (FIGS) as specified in [11] can be used to protect in CAMEL based inter-working networks. The Follow Me feature shall be controlled by means of Subscriber Controlled Input using USSD. 5 Applicability to telecommunication services GSM 02.01 describes the principles of the Telecommunication services provided in a GSM PLMN. It also defines the concepts of Telecommunication services and describes their characterization by appropriate attributes. Bearer services and Teleservices, which are offered by a PLMN in connection with other networks, are defined in TS 22.002, GSM 02.03 and TS 22.101. A list of basic service groups can be found in GSM TS 22.004. Follow Me is applicable to the following telecommunication services: ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 8 3G TS 22.094 version 3.1.0 Table 1: Applicability of the Follow Me feature to telecommunication services Feature Telephony Emergency Call SMS PTP SMS-CB Fax cct Data PAD/Packet Access Voice Group Services TS11 TS12 TS21 TS22 TS 23 TS 6x BS2x, BS3x BS4x BS5x TS 91 TS 92 Follow Me Yes Yes Yes No1 No1 NOTE 1: The feature is in general not applicable for Voice Group Services. However a dispatcher may be an initiating subscriber or a remote party for the Follow Me feature. EDITOR's Note: The applicability of FM to SMS is for further study. 6 Normal procedures with successful outcome 6.1 Provision Follow Me shall be provided after prior arrangement with the service provider. Follow Me will be provisioned for all Basic Services subscribed to and to which it is applicable. NOTES: - A Follow Me provision is required for the initiating subscriber and for the remote party in case the remote party corresponds to a subscriber. - If Follow Me is provisioned for a mobile subscriber she may assume the role of an initiating subscriber and/or the role of a remote party. - A Follow Me provisioning service provider may confine: a.) the range of remote parties for which a FM provisioned subscriber may become initiating subscriber b.) the range of potential initiating subscribers for a remote party. c) the range of remote parties for which a FM provisioned subscriber may become FM service supervisor. NOTE: (Health warning on security) The Follow Me feature is designed in such a way as to meet the security requirements of GSM-Railway operators. If the Follow Me feature is to be used by other operators - in particular if the remote party corresponds to a subscriber - operators are strongly advised to care for additional suitable security mechanisms to protect the remote party from potential harm by misuse of FM. These mechanisms are out of scope of this specification. To support such mechanisms the possibility is foreseen to convey additional operator-specific information in the registration, interrogation and erasure procedures to the PLMN of the remote party. It should however be noted, that this is not a very secure mechanism. Operators should try to use existing security mechanisms where possible 6.2 Withdrawal Follow Me will be withdrawn at the subscriber's request or for administrative reasons. 6.3 Registration Follow Me shall be registered with an appropriate control procedure by the initiating subscriber. The initiating Subscriber registers the Follow Me feature with respect to a particular remote party. The initiating subscriber shall provide the following information to the network: the number of the remote party (e.g. the Basic MSISDN of a subscriber); ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 9 3G TS 22.094 version 3.1.0 The initiating subscriber shall receive an indication if the FM registration request was accepted or rejected by the network. As an operator's option additional information (such as passwords) for registration may be required from the initiating subscriber. The registration procedure shall transport this information from the initiating subscriber to the network of the remote party. This information shall be coded as a USSD string with a length not exceeding 30 characters. The content of this information and the use of it are out of scope of this specification. NOTE 1: The Follow Me feature may, at an instant, be registered to an initiating subscriber with respect to several remote parties. Conversely, a remote party can be registered only to one initiating subscriber at a time. 6.4 Erasure A previous FM registration can be erased in either of the following ways: a) The initiating subscriber can specifically erase her previous registration with an appropriate control procedure. b) In case the remote party corresponds to a subscriber the remote party can erase any previous registration with an appropriate control procedure. c) The FM service supervisor can erase any previous registration to any remote party with an appropriate control procedure (forced erasure). The subscriber who initiates the FM erase request shall be informed of the outcome of the request by the network. As an operator's option additional information (such as passwords) for erasure may be required from the subscriber. The registration procedure shall transport this information from the subscriber to the network of the remote party. This information shall be coded as a USSD string with a length not exceeding 30 characters. The content of this information and the use of it are out of scope of this specification. 6.5 Activation Follow Me is activated by registration. 6.6 Deactivation Follow Me is deactivated by erasure. 6.7 Invocation Follow Me is automatically invoked by the network if it was previously registered. If Follow Me is registered all incoming calls to the remote party will be forwarded to the initiating subscriber by network invocation. When Follow Me is active and operative and if the remote party is a subscriber, the ability of the remote party to originate calls is not affected. 6.8 Interrogation An initiating subscriber (also the FM service supervisor) shall be able to interrogate the Follow Me data of any remote party, for which she is authorised to become initiating subscriber. In case the remote party corresponds to a subscriber the remote party shall be able to interrogate her own Follow Me data stored in the network. The network shall return the basic MSISDN of the initiating subscriber for which the remote party is registered to Follow Me. ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 10 3G TS 22.094 version 3.1.0 As an operator's option additional information (such as passwords) for interrogation may be required from the subscriber. The registration procedure shall transport this information from the subscriber to the network of the remote party. This information shall be coded as a USSD string with a length not exceeding 30 characters. The content of this information and the use of it are out of scope of this specification. 7 Exceptional procedures or unsuccessful outcome 7.1 Registration If the system cannot accept a registration request, the initiating subscriber shall receive a notification that Follow Me registration was not successful. Possible causes are: - insufficient information; - feature not provisioned to initiating subscriber; - feature not provisioned to remote party (in case the remote party is a subscriber); - conflicting situation with supplementary services (e.g. incoming call barring has been activated); – remote party already registered to a different initiating subscriber – insufficient authorisation for initiating subscriber or remote party 7.2 Erasure If the network cannot accept a mobile initiating or remote subscriber's request for erasure, cause will be returned to the subscriber, such as: - insufficient information; - remote party not registered – remote party registered to a different initiating subscriber – insufficient authorisation for initiating subscriber or remote party - feature not provisioned to initiating subscriber; - feature not provisioned to remote party (in case the remote party is a subscriber); 7.3 Interrogation If the network cannot accept a mobile initiating or remote subscriber's request for interrogation, cause will be returned to the subscriber, such as: - insufficient information; – insufficient authorisation for initiating subscriber or remote party – feature not provisioned to initiating subscriber; - feature not provisioned to remote party (in case the remote party is a subscriber); ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 11 3G TS 22.094 version 3.1.0 7.4 Invocation Within a PLMN or different PLMNs the number of tandem forwarding connections (including call forwarding, call deflection, Follow Me) should be limited. The maximum number of tandem forwarding connections should be limited to a value between 1 and 5. This is to prevent infinite looping. If the limit of successive forwardings of a call has already been reached, an unsuccessful call set up indication is sent backwards. If the call cannot be completed to the Follow Me destination, then the network will clear the forwarded part of the call and an unsuccessful call set up indication is sent backwards. 8 Alternate procedures None identified. 9 Charging requirements None identified. 10 Interactions with supplementary services Interactions of the Follow Me feature with supplementary services may occur only for the remote party. The interactions of the Follow Me feature with supplementary services other than Call Forwarding Unconditional (CFU) are the same as the interactions of CFU with supplementary services (see TS 22.082 [5]). NOTE: The “served mobile subscriber” in TS 22.082 [5] corresponds to the “remote party” in this document. The “forwarded-to subscriber” in TS 22.082 [5] corresponds to the “initiating subscriber” in this document 10.1 Call Forwarding unconditional Follow Me and the Call Forwarding Unconditional Supplementary Service are mutually exclusive. That is: If Follow Me is registered with respect to a remote party, registration or activation of Call forwarding unconditional by the remote party is rejected. The remote party shall be informed of this incompatibility. If Call forwarding unconditional is registered or active for the remote party, registration of Follow Me is rejected. The initiating subscriber shall be informed of this incompatibility. 11 Interaction with Operator Determined barring Same as interaction between Operator Determined barring and call forwarding unconditional as defined in TS 22.041. 12 Interaction with Optimal Routeing Same as interaction between Optimal Routeing and call forwarding unconditional as defined in TS 22.079. 13 Interaction with CAMEL Same as interaction between CAMEL and call forwarding unconditional as defined in TS 22.078. ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 12 3G TS 22.094 version 3.1.0 If a forwarded call due to invocation of Follow Me meets an interworking situation, then an interworking indication should be sent to the calling party. When interworking with non-PLMN or non-ISDN networks, tones and announcements will be required. NOTE1: The number of times a call has been forwarded once it has exited the PLMN or ISDN may not be limited. NOTE2: Tones and/or announcements should not be provided to the calling party if the information transfer capability is set to UDI. ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 3GPP 3G TS 22.094 V3.1.0 (1999-12) 13 3G TS 22.094 version 3.1.0 Annex A (informative) : Change history Change history SMG No. / TSG SA# TDoc. No. CR. No. Section affected New version Subject/Comments TSGT SA#6 SP99-595 001 3.1, 4, 6.1, 6.4, 6.8 Version 3.1.0 Introduction of the rôle of a “ Follow Me service supervisor:” ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) ETSI 14 ETSI ETSI TS 122 094 V3.1.0 (2000-01) (3G TS 22.094 version 3.1.0 Release 1999) History Document history V3.1.0 January 2000 Publication