hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
b41ec63634464ce43ed14dff853f0b01
|
122 079
|
5.3.2 Non-support of SOR in the HPLMN of the B subscriber
|
........................................................................... 13
|
b41ec63634464ce43ed14dff853f0b01
|
122 079
|
5.3.3 Non support of SOR in the VPLMN of the B subscriber
|
........................................................................... 13
|
b41ec63634464ce43ed14dff853f0b01
|
122 079
|
5.3.4 Calls to special mobile network numbers
|
................................................................................................... 13
|
b41ec63634464ce43ed14dff853f0b01
|
122 079
|
6 Interactions of Optimal Routing with Supplementary Services
|
.............................................................14
|
b41ec63634464ce43ed14dff853f0b01
|
122 079
|
6.1 Call Forwarding
|
............................................................................................................................................... 14
|
b41ec63634464ce43ed14dff853f0b01
|
122 079
|
6.2 Call Barring
|
..................................................................................................................................................... 14
|
b41ec63634464ce43ed14dff853f0b01
|
122 079
|
6.3 Call Transfer
|
.................................................................................................................................................... 14
|
b41ec63634464ce43ed14dff853f0b01
|
122 079
|
6.4 Call Deflection
|
................................................................................................................................................. 14
|
b41ec63634464ce43ed14dff853f0b01
|
122 079
|
6.5 Advice of Charge
|
............................................................................................................................................. 14
|
b41ec63634464ce43ed14dff853f0b01
|
122 079
|
7 Interactions of Optimal Routing with Operator Determined Barring (ODB)
|
........................................14
|
b41ec63634464ce43ed14dff853f0b01
|
122 079
|
8 Interactions of Optimal Routing with CAMEL
|
.....................................................................................14 Annex A: Change history ..............................................................................................................................15 History..............................................................................................................................................................16 (3G TS 22.079 version 3.0.1 Release 1999) ETSI TS 122 079 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.079 V3.0.1 (1999-10) 4 3G TS 22.079 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; (3G TS 22.079 version 3.0.1 Release 1999) ETSI TS 122 079 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.079 V3.0.1 (1999-10) 5 3G TS 22.079 version 3.0.1 1 Scope This Stage 1 description of the first phase of Support of Optimal Routing (SOR): - compiles the basic service requirements for SOR; - describes the interactions for Supplementary Services (SS) in order to cater for SOR; - refers to modifications to network features required by SOR. This specification does not address the following: - There is no need for optimisation of the routing of calls originally directed to a fixed network subscriber, because the physical address of a fixed network terminating line cannot differ from its logical address. - SOR in non-PLMNs is not a subject of this TS, but might be possible by bilateral arrangement between PLMN operators and those non-PLMN operators. The purpose of SOR is to reduce the number of unnecessary inter-PLMN call legs. The first phase of SOR applies to: - OR for the benefit of the B party i.e. Mobile terminated calls with late call forwarding to the home or visited country (scenarios 1 and 2), and optionally; - OR for the benefit of the A party, e.g. Mobile to mobile calls where both mobile subscribers are in the same country (scenarios 3 to 10). The complete set of scenarios included in the phase 1 of OR is presented in the paragraph for normal procedures. All other scenarios are excluded from Phase 1 of OR. Note that Optimal Routing is applicable to national roaming situations, that is to calls directed to a mobile subscriber roaming in her home country, but registered in a PLMN different from her HPLMN. All further call scenarios, including multiple call forwarding, are left to subsequent phases of SOR. Subsequent phases of SOR shall be backwards compatible with this first phase. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. • For this Release 1999 document, references to GSM documents are for Release 1999 versions (version 8.x.y). [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". [2] TR 21.905: "Vocabulary for 3GPP Specifications". (3G TS 22.079 version 3.0.1 Release 1999) ETSI TS 122 079 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.079 V3.0.1 (1999-10) 6 3G TS 22.079 version 3.0.1 3 Definitions and abbreviations Administrative PLMN: The complete set of all functional entities normally regarded as a single PLMN. Basic OR : Routeing of a call by the direct route when no forwarding occurs. Direct route: A call uses the direct route if it is routed from the serving network of the original calling party to the serving network of the ultimate called party without any intermediate PLMN. HPLMN route: A call uses the HPLMN route if the destination is deduced from the MSISDN of the called party. This forces the call to be routed via the HPLMN of the called party. HPLMN leg: The HPLMN leg is that part of the HPLMN route from the IPLMN to the HPLMN of the called party. IPLMN: An IPLMN is a PLMN which interrogates the HPLMN of a called party in order to determine the whereabouts of that party. Early Call Forwarding : Early Call Forwarding is Call Forwarding performed from the IPLMN before the call has been extended to the VPLMN of the forwarding subscriber (i.e. Call Forwarding Unconditional and Conditional Call Forwarding on Not Reachable known at the IPLMN before extension of the call) Functional PLMN: For the purposes of this description the Administrative PLMN is divided into functional PLMNs that represent different aspects of the Optimal Routeing functionality. Late Call Forwarding: Late Call Forwarding is Call Forwarding performed after the call has been extended to the VPLMN of the forwarding subscriber (i.e. Conditional Call Forwarding on Busy, Conditional Call Forwarding on No Reply and Conditional Call Forwarding on Not Reachable detected in the VPLMN of the forwarding subscriber). Late Call Forwarding may be invoked in the IPLMN or in the VPLMN of the forwarding subscriber. Special mobile network number: For the purposes of this description special mobile network numbers are numbers belonging logically to a PLMN but not to a mobile subscriber. Examples are the customer service number or value added service numbers. Abbreviations are given in GSM 01.04 [1] and TR 21.905 [2]. 4 Description of Optimal Routing Support of Optimal Routing (SOR) is a network feature which enables the calls directed to a mobile subscriber to be routed directly to the mobile subscriber's actual location, or to her forwarded-to destination (instead of via the HPLMN or in the case of Late Call Forwarding via the VPLMN). The IPLMN handling the call shall decide whether or not to optimise the routing of the call taking into account information provided by the called mobile subscriber's HPLMN. For given subscribers, as a network option, the HPLMN may permit or deny OR on a per call basis. 5 Functional requirements 5.1 General SOR shall be provided for all circuit switched Telecommunication Services, except emergency calls, Dedicated PAD and Dedicated Packet Access (GPRS is for further study). The network feature shall be applied automatically for all calls except for those calls for which the HPLMN of the called party denies the optimal routing. (3G TS 22.079 version 3.0.1 Release 1999) ETSI TS 122 079 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.079 V3.0.1 (1999-10) 7 3G TS 22.079 version 3.0.1 5.2 Normal operation In the first phase of SOR, the routes of calls will be optimised for the cases of OR being performed within a country or towards the country where the call would have been routed normally. Under all other circumstances, the basic call routing is applied: - If the IPLMN detects that basic OR cannot be applied, the IPLMN routes the call according to the dialled number. - If the IPLMN detects that OR for Late Call Forwarding cannot be applied, the Call Forwarding will be performed in the VPLMN of the forwarding subscriber. If the serving network of the ultimate destination supports SOR, the serving network of the caller shall be able to indicate to the network visited by the ultimate destination that the call has been optimally routed and to indicate the originating PLMN of the optimally routed leg. The complete set of scenarios included in phase 1 of SOR is described below. The notation used for the scenario diagrams is defined in figure 1. T raffic route T raffic route of basic G SM routeing, not used for OR Output of call record inform ation Interrogation Functional PLM N (e.g. IPLM N, VPLM N-B) Adm inistrative PLM N, w hich m ay include tw o functional PLM Ns C all Attem pt Figure 1: Notation used in scenario diagrams If one of those scenarios occurs, SOR shall be invoked. The assumptions taken are the following : - A subscriber A sets up a call to a mobile subscriber B, who may have forwarded her calls to a subscriber C. - The C subscriber may be either a fixed subscriber or a mobile subscriber. If C is a mobile subscriber, the location of C taken into account in the following paragraphs is the location of HPLMN- C. 5.2.1 A is a fixed subscriber or a mobile subscriber who may not benefit from OR As the originating network does not have the ability to interrogate the HPLMN of the B subscriber, the normal call handling is applied. Once the HPLMN of the B subscriber has the control of the call, the call may be optimised in the case of a forwarded call towards a party located in the Home Country of the B subscriber or in the country visited by the B subscriber. NOTE: - A may be in any country. - In the two following cases, the IPLMN is HPLMN-B. (3G TS 22.079 version 3.0.1 Release 1999) ETSI TS 122 079 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.079 V3.0.1 (1999-10) 8 3G TS 22.079 version 3.0.1 IPLM N HPLM N-B VPLM N-B A Country Z Country Y C Call record: Call forw arding record OR flag Country X Scenario 1: OR for Late Call Forwarding, C is in the same country as HPLMN-B NOTE: Call records shown in the figure are only for information IPLM N HPLM N-B VPLM N-B A Country Z Country Y C Call record: Call forw arding record OR flag Country X Scenario 2: OR for Late Call Forwarding, C is in the same country as VPLMN-B NOTE: Call records shown in the figure are only for information 5.2.2 A is a mobile subscriber who may benefit from OR 5.2.2.1 Description of the call routing If A sets up a call to B, then the originating PLMN shall interrogate the HPLMN of the mobile subscriber B in order to know how to route the call. If B is registered in the same country as A, then the call shall be routed directly to B as described below. If B has activated a Call Forward to a destination located in the Home Country of B or in the country where A is registered and this leads to the invocation of Early Call Forwarding, then the call shall be routed directly from A to the forwarded-to-party. In any other cases, the call shall be routed to the mobile subscriber B via HPLMN(B). If the call cannot be completed, the originating PLMN shall receive an indication of the reason of the failure of the call completion. (3G TS 22.079 version 3.0.1 Release 1999) ETSI TS 122 079 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.079 V3.0.1 (1999-10) 9 3G TS 22.079 version 3.0.1 Thereafter, if the mobile subscriber B has activated a Conditional Call Forward to a destination located in her Home Country or to a destination in the country where A is registered and this leads to the invocation of Late Call Forwarding, then the originating PLMN shall route the call directly to the forwarded-to-party. The remaining leg of the call from the intermediate point to the ultimate destination may be optimally routed. 5.2.2.2 Call scenarios handled in OR Phase 1 In the following scenarios, the IPLMN is VPLMN-A. 1) The call from the A subscriber to the B subscriber is completed (Basic OR) a) B is located in the same country as A VPLM N-A IPLM N Country Y Country X HPLM N-B VPLM N-B A B 1 2 3 4 5 6 Call record: MO record (Dialled nmb, real destination, OR flag) Call record: MT record (OR flag) Scenario 3: BASIC OR, B in the same country as A NOTE: Call records shown in the figure are only for information b) B is located in her Home Country (Network usage optimization) (3G TS 22.079 version 3.0.1 Release 1999) ETSI TS 122 079 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.079 V3.0.1 (1999-10) 10 3G TS 22.079 version 3.0.1 VPLM N-A IPLM N Country Y Country X HPLM N-B VPLM N-B A B 1 2 3 4 5 6 Call record: MO record (Dialled nmb, real destination, OR flag) Call record: MT record (OR flag) Scenario 4: BASIC OR, B in her home country NOTE: Call records shown in the figure are only for information 2) The call set up by the subscriber A is being forwarded to a C party 2.1) Early Call Forward NOTE: for the two following scenarios, the location of B is not relevant. a) the C party is in the same country as the A subscriber, but different from HPLMN B country. VPLMN-A IPLMN Country Y Country X HPLMN-B VPLMN-B A C 1 2 3 4 5 Any country Call record: MO record (Dialled nmb, real destination, OR flag) Call record: Call forwarding record (OR flag) Scenario 5: Early CF, C in the same country as A NOTE: Call records shown in the figure are only for information. (3G TS 22.079 version 3.0.1 Release 1999) ETSI TS 122 079 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.079 V3.0.1 (1999-10) 11 3G TS 22.079 version 3.0.1 b) the C party is in the same country as HPLMN-B VPLMN-A IPLM N Country Y Country X HPLMN-B VPLMN-B A 1 2 3 4 Any country Call record: MO record (Dialled nmb, real destination, OR flag) Call record: Call forwarding record (OR flag) C 5 Scenario 6: Early CF, C in the same country as HPLMN-B NOTE: Call records shown in the figure are only for information 2.2) Late Call Forward a) B and C are in the same country as A VPLM N-A IPLM N Country Y Country X HPLM N-B VPLM N-B A C 1 2 5 6 Call record: MO record (Dialled nmb, real destination, OR flag) Call record: Call forwarding record (OR flag) 3 4 Scenario 7: BASIC OR + OR for Late Call Forwarding, B in the same country as A, C in the same country as A NOTE: Call records shown in the figure are only for information (3G TS 22.079 version 3.0.1 Release 1999) ETSI TS 122 079 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.079 V3.0.1 (1999-10) 12 3G TS 22.079 version 3.0.1 b) B is in the same country as A and C is in the same country as HPLMN-B VPLM N-A IPLM N Country Y Country X HPLM N-B VPLM N-B A C 1 2 5 6 Call record: MO record (Dialled nm b, real destination, OR flag) Call record: C all forw arding record (OR flag) 3 4 Scenario 8: BASIC OR + OR for Late Call Forwarding, B in the same country as A, C in the same country as HPLMN-B NOTE: Call records shown in the figure are only for information c) B is in her home country and C is in the same country as A VPLM N-A IPLM N Country Y Country X HPLM N-B VPLM N-B A C 1 2 5 6 Call record: MO record (Dialled nm b, real destination, O R flag) Call record: C all forw arding record (OR flag) 3 4 Scenario 9: BASIC OR + OR for Late Call Forwarding, B in the same country as HPLMN-B, C in the same country as A NOTE: Call records shown in the figure are only for information d) B and C are in the country of HPLMN-B (3G TS 22.079 version 3.0.1 Release 1999) ETSI TS 122 079 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.079 V3.0.1 (1999-10) 13 3G TS 22.079 version 3.0.1 VPLM N-A IPLM N Country Y Country X HPLM N-B VPLM N-B A C 1 2 5 6 Call record: MO record (Dialled nm b, real destination, OR flag) Call record: Call forwarding record (OR flag) 3 4 Scenario 10: BASIC OR + OR for Late Conditional Call Forwarding, B in the same country as HPLMN- B, C in the same country as HPLMN-B NOTE: Call records shown in the figure are only for information. 5.3 Exceptional procedures or unsuccessful outcome 5.3.1 Non-support of SOR in the VPLMN of the caller If subscriber A roams into a network not supporting OR, she may not benefit from OR and only scenario 1 and scenario 2 of SOR are supported. 5.3.2 Non-support of SOR in the HPLMN of the B subscriber If the HPLMN of the called party does not support SOR, SOR cannot be invoked and the route of the call as far as the called party’s VPLMN cannot be optimised (the call would normally be routed via the HPLMN of the called party). The same procedure shall be followed if the HPLMN operator denies OR on a subscriber basis. 5.3.3 Non support of SOR in the VPLMN of the B subscriber If a subscriber whose HPLMN supports SOR registers in a VPLMN which does not support SOR, only the cases of Early Forwarded calls may be optimised. 5.3.4 Calls to special mobile network numbers If the called number is a special mobile network number of the HPLMN, the HPLMN has to guarantee that the call terminates at its correct destination. This can be achieved by denying OR for this call by sending an appropriate error cause or by implementing a special handling. (3G TS 22.079 version 3.0.1 Release 1999) ETSI TS 122 079 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.079 V3.0.1 (1999-10) 14 3G TS 22.079 version 3.0.1 6 Interactions of Optimal Routing with Supplementary Services No Interaction unless it is stated differently below. 6.1 Call Forwarding Interactions between SOR and Call Forwarding are dealt with in clause 5.0. 6.2 Call Barring Outgoing Call Barring services are applied according to the dialled number. Barring of Incoming calls when Roaming outside the HPLMN country will prevent calls to a mobile subscriber who has roamed outside her HPLMN country even if OR would result in no chargeable roaming leg. The existing interactions between Call Forwardings and Call Barrings are not changed by the introduction of OR. 6.3 Call Transfer A transferred call is considered as a set of two separate calls which may be separetely optimally routed. Optimal Routing shall not be invoked as a result of the invocation of Call Transfer. 6.4 Call Deflection A deflected call is considered as a late forwarded call and as such may be optimally routed. 6.5 Advice of Charge Depending on call scenarios, AoC may not work properly. 7 Interactions of Optimal Routing with Operator Determined Barring (ODB) The principles for the interaction between operator determined barring and SOR are the same as those for the interaction between Supplementary Service Call Barring and SOR. If CAMEL has to be applied to the Mobile Originating part of the call and if CAMEL modifies the destination of the call, the OR applies to any destination introduced by CAMEL. If CAMEL has to be applied to the Mobile Terminating part of the call or a forwarding leg, the modified destination is treated for optimal routeing in the same way as a forwarded-to number. If Barring services are also applicable to the call then they have to be handled first together with CAMEL before SOR is applied. (3G TS 22.079 version 3.0.1 Release 1999) ETSI TS 122 079 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.079 V3.0.1 (1999-10) 15 3G TS 22.079 version 3.0.1 Annex A: Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.79 7.0.0 Transferred to 3GPP SA1 SA#04 22.079 3.0.0 SA#05 22.079 3.0.0 001 R99 3.0.1 Editorial update of references for GSM/3GPP use. (3G TS 22.079 version 3.0.1 Release 1999) ETSI TS 122 079 V3.0.1 (2000-01) ETSI 16 ETSI ETSI TS 122 079 V3.0.1 (2000-01) (3G TS 22.079 version 3.0.1 Release 1999) History Document history V3.0.1 January 2000 Publication
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
2 References
|
................................................................................................................................................6
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
3 Definitions and Abbreviations
|
.................................................................................................................6
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
3.1 Definitions
|
......................................................................................................................................................... 6
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
3.2 Abbreviations
|
..................................................................................................................................................... 6
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
4 Description
|
...............................................................................................................................................7
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
4.1 General Description
|
........................................................................................................................................... 7
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
4.2 Applicability to telecommunication services
|
..................................................................................................... 7
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
5 Normal Procedures with successful outcome
|
..........................................................................................7
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
5.1 Provision
|
............................................................................................................................................................ 7
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
5.2 Withdrawal
|
........................................................................................................................................................ 8
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
5.3 Registration
|
........................................................................................................................................................ 8
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
5.4 Erasure
|
............................................................................................................................................................... 8
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
5.5 Activation
|
.......................................................................................................................................................... 8
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
5.6 Deactivation
|
....................................................................................................................................................... 8
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
5.7 Invocation
|
.......................................................................................................................................................... 8
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
5.8 Interrogation
|
...................................................................................................................................................... 8
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
5.9 Normal Operation
|
.............................................................................................................................................. 8
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
5.10 Charging requirements
|
....................................................................................................................................... 9
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
6 Exceptional procedures or unsuccessful outcome
|
...................................................................................9
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
6.1 Invocation and operation
|
................................................................................................................................... 9
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7 Interactions with other supplementary services
|
.....................................................................................10
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.1 Calling Line Identification Presentation (CLIP)
|
.............................................................................................. 10
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.2 Calling Line Identification Restriction (CLIR)
|
................................................................................................ 10
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.3 Connected Line Identification Presentation (COLP)
|
....................................................................................... 10
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.4 Connected Line Identification Restriction (COLR)
|
......................................................................................... 10
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.5 Call Forwarding Unconditional (CFU)
|
............................................................................................................ 10
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.6 Call Forwarding on mobile subscriber Busy (CFB)
|
........................................................................................ 10
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.7 Call Forwarding on No Reply (CFNRy)
|
.......................................................................................................... 10
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc)
|
..................................................................... 10
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.9 Call Deflection (CD)
|
........................................................................................................................................ 10
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.10 Call Waiting (CW)
|
........................................................................................................................................... 11
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.11 Call Hold (CH)
|
................................................................................................................................................ 11
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.12 Multi-party (MPTY)
|
........................................................................................................................................ 11
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.13 Closed User Group (CUG)
|
.............................................................................................................................. 11
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.14 Advice of Charge (AoC)
|
.................................................................................................................................. 11
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.15 Barring of All Outgoing Calls (BAOC)
|
........................................................................................................... 11
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.16 Barring of all Outgoing International Calls (BOIC)
|
........................................................................................ 11 7.17 Barring of all Outgoing International Calls except those direct to the Home PLMN Country (BOIC- exHC)............................................................................................................................................................... 11
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.18 Barring of All Incoming Calls (BAIC)
|
............................................................................................................ 11
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.19 Barring of Incoming Calls when roaming outside the home PLMN country (BIC-Roam)
|
............................. 11
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.20 Explicit Call Transfer (ECT)
|
........................................................................................................................... 12
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.21 Completion of Calls to Busy Subscriber (CCBS)
|
............................................................................................ 12
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.22 Support of Private Numbering Plan (SPNP)
|
.................................................................................................... 12
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
7.23 Multiple Subscriber Profile (MSP)
|
.................................................................................................................. 12 (3G TS 22.072 version 3.0.1 Release 1999) ETSI TS 122 072 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.072 V3.0.1 (1999-10) 4 3G TS 22.072 version 3.0.1
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
8 Interactions with Customized Applications for Mobile network Enhanced Logic (CAMEL);
|
.............12
|
6047f069f50d2461aa2a700b81b9869f
|
122 072
|
9 Interworking Considerations
|
..................................................................................................................12 Annex A (informative): Deviations to the ISDN service Call Deflection...................................................13 Annex B: Change history ..............................................................................................................................13 History..............................................................................................................................................................14 (3G TS 22.072 version 3.0.1 Release 1999) ETSI TS 122 072 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.072 V3.0.1 (1999-10) 5 3G TS 22.072 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; (3G TS 22.072 version 3.0.1 Release 1999) ETSI TS 122 072 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.072 V3.0.1 (1999-10) 6 3G TS 22.072 version 3.0.1 1 Scope Call Deflection (CD) enables the served mobile subscriber to respond to an incoming call offered by the network by requesting redirection of this call to another number specified in the response. The CD supplementary service can only be invoked before the connection is established by the served mobile subscriber, i.e. in response to the offered call, or during the period that the served subscriber is being informed of the call. The served subscriber’s ability to originate calls is unaffected by the CD supplementary service. 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.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)". [4] TS 22.085: "Closed User Group (CUG) Supplementary Services - Stage 1 [5] TR 21.905: "Vocabulary for 3GPP Specifications". [6] TS 22.078: "CAMEL Phase 3; Stage 1". 3 Definitions and Abbreviations 3.1 Definitions served subscriber: The mobile subscriber to whom the CD supplementary service is provided. subscriber A: The calling subscriber in a call which is subject to diversion. The subscriber A may be a subscriber of any network. deflected-to subscriber: A subscriber to whom the call is redirected as a result of the CD supplementary service. The deflected-to subscriber may be a subscriber of any network. (call) forwarding: A general term applied to any functionality whereby a call is redirected automatically by the network to another user. The forms of forwarding are: unconditional, busy, no reply and not reachable. diversion: A general term which includes all forms of call forwarding and call deflection whereby calls are redirected by the user instead of being answered. 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] and TR 21.905 [5]. (3G TS 22.072 version 3.0.1 Release 1999) ETSI TS 122 072 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.072 V3.0.1 (1999-10) 7 3G TS 22.072 version 3.0.1 CD Call Deflection 4 Description 4.1 General Description The CD Supplementary Service enables the served mobile subscriber to respond to an incoming call offered by the network by requesting redirection of this call to another number specified in the response. The CD supplementary service can only be invoked before the connection is established by the served mobile subscriber, i.e. in response to the offered call during the period that the served subscriber is being informed of the call. The served subscriber’s ability to originate calls is unaffected by the CD supplementary service. A maximum number of diversions is permitted for each call with an upper limit of five diversions. When counting the number of diversions, all types of diversions are included. As an network operator option the maximum number of diversions shall be in the range of one to five diversions per call. If the limit of successive diversions of a call is already reached an unsuccessful call setup indication is sent backward to the network originating the call. The invocation of Call Deflection can either be an automatic response from the mobile station to the offered call (use pre-programmed information) or may be the result of an action by the served subscriber. The mobile station related procedures to pre-program and display the deflected-to number is out of the scope of this specification. If the CD service is provisioned and there is no service violation, the request will be accepted, the connection to the served mobile station will be released (with an appropriate notification) and a call towards the deflection-to subscriber will be established. 4.2 Applicability to telecommunication services The applicability of this supplementary service is defined in TS 22.004 [2]. 5 Normal Procedures with successful outcome 5.1 Provision The supplementary service will be provisioned for all Basic Services subscribed to and to which it is applicable. The service can be offered with several subscription options. Options apply to all Basic services subscribed to. For each subscription option, only one value can be selected. Subscription option: Value Calling subscriber receives notification that her call has been deflected - Yes - No MSISDN of the served subscriber can be presented to the deflected-to subscriber - Yes - No (3G TS 22.072 version 3.0.1 Release 1999) ETSI TS 122 072 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.072 V3.0.1 (1999-10) 8 3G TS 22.072 version 3.0.1 5.2 Withdrawal The supplementary service will be withdrawn at the subscriber's request or for service provider reasons. 5.3 Registration Not applicable. 5.4 Erasure Not applicable. 5.5 Activation Within the network the service is activated for the whole subscription period. This supplementary service shall be activated by the service provider as a result of provision. NOTE: No activation/deactivation procedure is needed at the user-network interface. 5.6 Deactivation This supplementary service shall be deactivated by the service provider as a result of withdrawal. 5.7 Invocation The CD supplementary service shall be invoked by the served mobile subscriber by use of a control procedure as described in TS 22.030 [3]. 5.8 Interrogation Not applicable. 5.9 Normal Operation The network offers incoming calls to the served mobile subscriber according to the normal procedure. The served subscriber can respond to the incoming call offered normally or by invoking the CD supplementary service with an appropriate message. This appropriate message will contain the call deflection request and the deflected-to number. This deflected-to number may be accompanied by a deflected-to subaddress. Two different cases of the CD invocation can be distinguished: - The invocation can be either an automatic response from the mobile station to the offered call (using pre- programmed information at the mobile station) or - may be the result of an action by the served subscriber. If the CD supplementary service is invoked and the served mobile subscriber has subscribed to the service, the network performs the call deflection towards the indicated deflected-to number and clears the call to the called (served) mobile subscriber with a positive acknowledgement. As a subscription option, the served mobile subscriber can request that the subscriber A receives a notification that the call has been deflected. (3G TS 22.072 version 3.0.1 Release 1999) ETSI TS 122 072 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.072 V3.0.1 (1999-10) 9 3G TS 22.072 version 3.0.1 The deflected-to subscriber shall receive an indication that the CD supplementary service has been invoked on the call, i.e. that call has been deflected. Depending on the value of the served subscribers subscription option, the deflected-to subscriber may also receive the MSISDN of the served subscriber. When multiple diversions occurs the reason for diversion and the MSISDN given to the deflected-to subscriber should relate to the last diverting subscriber (e.g. the subscriber who has invoked the CD supplementary service). When calls are diverted once, i.e. due to a single invocation of the CD supplementary service, the following information shall be given to subscriber A based on the value of the served mobile subscriber’s subscription option "calling subscriber receives notification that the call has been deflected": - if the value of the subscription option is "no", then no information shall be sent to subscriber A; - if the value of the subscription option is "yes ", then an indication that the call is being deflected shall be sent to subscriber A. 5.10 Charging requirements The deflecting subscriber may be charged for the deflected part of the call. 6 Exceptional procedures or unsuccessful outcome 6.1 Invocation and operation If a mobile subscriber tries to invoke the CD supplementary service while not subscribed to or the network operator cannot provide the CD supplementary service for some other reasons, an indication shall be provided to the mobile subscriber to notify her with the reason of failure. Possible causes for rejection include: - service not subscribed to; - deflected-to number invalid; - deflected-to number is barred; - use of an operator access prefix; - insufficient information; - deflected-to number is a special service code (see note 1); - deflected-to number is served mobile subscriber's number (see note 2); - the number of diversions has reached the upper limit; - supplementary services incompatibility; NOTE 1: Network operators may prevent a served subscriber from invoking the CD supplementary service when the number specified for the deflected-to subscriber has special significance, e.g. emergency services, operator services. The identification of such numbers is outside the scope of this standard. NOTE 2: The network can only check the deflected-to number against the Basic MSISDN of the served subscriber. If the deflected call cannot be completed to the deflected-to subscriber the network shall clear the call towards the subscriber A and notify the subscriber A of the rejection. (3G TS 22.072 version 3.0.1 Release 1999) ETSI TS 122 072 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.072 V3.0.1 (1999-10) 10 3G TS 22.072 version 3.0.1 7 Interactions with other supplementary services 7.1 Calling Line Identification Presentation (CLIP) When a call has been deflected and the deflected-to subscriber has been provided with the CLIP supplementary service, the deflected-to subscriber shall receive the number of the subscriber A unless the CLIR supplementary service is invoked for the subscriber A. 7.2 Calling Line Identification Restriction (CLIR) No impact, i.e. when the CLIR supplementary service is applicable and invoked for subscriber A, her line identity shall not be presented to the deflected-to subscriber unless the deflected-to subscriber has an override category. 7.3 Connected Line Identification Presentation (COLP) If the served (deflecting) subscriber selects the option that the subscriber A is not notified of call deflection, then the subscriber A shall not receive the connected line identity when the call is answered, unless the subscriber A has override capability. Otherwise, no impact. 7.4 Connected Line Identification Restriction (COLR) No impact. 7.5 Call Forwarding Unconditional (CFU) No impact. 7.6 Call Forwarding on mobile subscriber Busy (CFB) No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. NOTE: If the subscriber is not network determined user busy, then the CD supplementary service or the call forwarding on mobile subscriber busy supplementary service by indicating UDUB can be invoked, depending on the response from the served mobile subscriber. 7.7 Call Forwarding on No Reply (CFNRy) No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. NOTE: If the network indicates the arrival of an incoming call to the served mobile subscriber, then the CD supplementary service, or the call forwarding on no reply supplementary service can be invoked, depending on the response, or lack of response, from the served mobile subscriber. 7.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc) No impact, 7.9 Call Deflection (CD) Not applicable. (3G TS 22.072 version 3.0.1 Release 1999) ETSI TS 122 072 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.072 V3.0.1 (1999-10) 11 3G TS 22.072 version 3.0.1 7.10 Call Waiting (CW) When receiving the call waiting indication, the served mobile subscriber can invoke the CD supplementary service. 7.11 Call Hold (CH) No impact 7.12 Multi-party (MPTY) No impact 7.13 Closed User Group (CUG) Same as the interaction between CUG and the call forwarding supplementary services as defined in TS 22.085 [4]. 7.14 Advice of Charge (AoC) No impact NOTE: The Advice of Charge service does not provide any information about the charge of the deflected leg of the call to the deflecting subscriber. 7.15 Barring of All Outgoing Calls (BAOC) If the served subscriber has Barring of all outgoing calls active and operative the invocation of the CD supplementary service shall be rejected. 7.16 Barring of all Outgoing International Calls (BOIC) If the served subscriber has barring of all outgoing international calls active and operative, any invocation of the CD supplementary service to a number not allowed by the barring program shall be rejected. 7.17 Barring of all Outgoing International Calls except those direct to the Home PLMN Country (BOIC-exHC) If the served subscriber has barring of all outgoing international calls except those direct to the HPLMN Country active and operative, any invocation of the CD supplementary service to a number not allowed by the barring program shall be rejected. 7.18 Barring of All Incoming Calls (BAIC) No impact. 7.19 Barring of Incoming Calls when roaming outside the home PLMN country (BIC-Roam) No impact (3G TS 22.072 version 3.0.1 Release 1999) ETSI TS 122 072 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.072 V3.0.1 (1999-10) 12 3G TS 22.072 version 3.0.1 7.20 Explicit Call Transfer (ECT) No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. NOTE: Where a network supports the option to transfer a call for which the connection has been established, to a user to which the connection has not yet been established, the transferred call can be deflected if this second subscriber invokes the CD supplementary service. 7.21 Completion of Calls to Busy Subscriber (CCBS) A recall resulting from the completion of calls to busy subscribers supplementary service shall not be deflected. Subscriber A: If a call to the called subscriber (served CD subscriber) is deflected (by the served CD subscriber) to another subscriber by the CD supplementary service and the deflected-to subscriber is busy, then subscriber A shall not receive any CCBS possible indication. Served subscriber: If the called subscriber (served CD subscriber) requests invocation of the CD supplementary service on a terminating call resulting from the completion of calls to busy subscribers supplementary service, then the CCBS call shall be deflected as a normal call. 7.22 Support of Private Numbering Plan (SPNP) No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. The served subscriber shall be able to enter the deflected-to number according to the selected numbering plan. 7.23 Multiple Subscriber Profile (MSP) If a subscriber is provisioned to both the MSP and the CD service, the CD service shall be provisioned on a per profile basis. If CD is provisioned in the profile used for the incoming call, the served subscriber may invoke the CD supplementary service in the normal way. 8 Interactions with Customized Applications for Mobile network Enhanced Logic (CAMEL); The CD supplementary service shall, if invoked, take affect after the invocation of any terminating CAMEL based service. Any deflected call may cause invocation of any mobile originated CAMEL based services. If the served subscriber is provided with a Translation Information Flag (TIF-CSI, see TS 22.078 [6]) and the VPLMN supports CAMEL phase 2, then when the CD supplementary service is invoked the network shall not check the validity of the deflected-to number and shall not apply the CD interactions with Barring of all Outgoing International Calls (BOIC) and Barring of all Outgoing International Calls except those direct to the Home PLMN Country (BOIC-exHC). NOTE: This behaviour may be used to deflect a call to a destination violating the BOIC or BOIC-exHC supplementary service. The HPLMN operator should take care to avoid problems that may arise because of this interaction. Non identified. (3G TS 22.072 version 3.0.1 Release 1999) ETSI TS 122 072 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.072 V3.0.1 (1999-10) 13 3G TS 22.072 version 3.0.1 Annex A (informative): Deviations to the ISDN service Call Deflection 1) If the call deflection request of a served subscriber is accepted and CD is invoked ISDN gives two network options: a) The call to the served user is retained until the network receives an indication that the deflected-to user is informed of the call. b) First the call is removed from the served subscriber and then the connection to the deflected-to subscriber is established. PLMNs only provide network option b. 2) The service CD does not provide the subscription option "the served user's ISDN number can be presented to the deflected-to user" to the served subscriber. 3) The interaction between CD and CCBS in the PLMN is different from the interaction between CD and CCBS in ISDN. The activation of the CCBS supplementary service will not be offered to the calling subscriber if the original call is deflected to a busy user. In ISDN the CCBS request applies to the original called party. 4) The handling of notifications to subscriber A in case of multiple diversion is not described in the way as ISDN this has been done. It is the intention of this service description to retain the same handling as it is used in present call forwarding implementations. Annex B: Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.72 7.2.0 Transferred to 3GPP SA1 SA#04 22.072 3.0.0 SA#05 22.072 3.0.0 001 R99 3.0.1 Editorial update of references for GSM/3GPP use. (3G TS 22.072 version 3.0.1 Release 1999) ETSI TS 122 072 V3.0.1 (2000-01) ETSI 14 ETSI ETSI TS 122 072 V3.0.1 (2000-01) (3G TS 22.072 version 3.0.1 Release 1999) History Document history V3.0.1 January 2000 Publication
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
2 References
|
................................................................................................................................................6
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
3 Definitions and abbreviations
|
..................................................................................................................7
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
3.1 Definitions
|
......................................................................................................................................................... 7
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
3.2 Abbreviations
|
..................................................................................................................................................... 7
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
4 Description
|
...............................................................................................................................................7
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
4.1 Applicability to telecommunication services
|
................................................................................................... 10
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
5 Normal operation with successful outcome
|
...........................................................................................10
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
5.1 Provision
|
.......................................................................................................................................................... 10
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
5.2 Withdrawal
|
...................................................................................................................................................... 10
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
5.3 Registration
|
...................................................................................................................................................... 10
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
5.4 Erasure
|
............................................................................................................................................................. 10
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
5.5 Network related service configuration
|
............................................................................................................. 10
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
5.6 Activation
|
........................................................................................................................................................ 10
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
5.7 Deactivation
|
..................................................................................................................................................... 11
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
5.8 Invocation
|
........................................................................................................................................................ 11
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
5.9 Normal operation
|
............................................................................................................................................. 11
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
5.10 Interrogation
|
.................................................................................................................................................... 11
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
5.11 Charging requirements
|
..................................................................................................................................... 11
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
6 Exceptional procedures or unsuccessful outcome
|
.................................................................................11
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
7 Alternate procedures
|
..............................................................................................................................12
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8 Interaction with other supplementary services
|
......................................................................................12
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8.1 Calling Line Identification Presentation (CLIP)
|
.............................................................................................. 12
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8.2 Calling Line Identification Restriction (CLIR)
|
................................................................................................ 12
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8.3 Connected Line Identification Presentation (COLP)
|
....................................................................................... 12
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8.4 Connected Line Identification Restriction (COLR)
|
......................................................................................... 12
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8.5 Call Forwarding Unconditional (CFU)
|
............................................................................................................ 12
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8.6 Call Forwarding on mobile subscriber busy (CFB)
|
......................................................................................... 12
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8.7 Call Forwarding on No Reply (CFNRy)
|
.......................................................................................................... 12
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc)
|
..................................................................... 12
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8.9 Call Waiting (CW)
|
........................................................................................................................................... 13
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8.10 Call Hold
|
.......................................................................................................................................................... 13 8.11 Multi-party Service (MPTY) ........................................................................................................................... 13
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8.12 Closed User Group (CUG)
|
.............................................................................................................................. 13
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8.13 Advice of Charge (AoC)
|
.................................................................................................................................. 13
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8.14 Barring of Outgoing Calls (BAOC)
|
................................................................................................................. 13
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8.15 Barring of Outgoing International Calls (BOIC)
|
............................................................................................. 13 8.16 Barring of Outgoing International Calls except those to the Home PLMN country (BOIC-exHC) ................ 13
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8.17 Barring of All Incoming Calls (BAIC)
|
............................................................................................................ 13 8.18 Barring of Incoming Calls when Roaming outside the home PLMN country (BIC-Roam)............................ 13
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
8.19 Call Transfer (ECT)
|
......................................................................................................................................... 14
|
2fd13a5cb82c896569e8c6871420bfa2
|
122 067
|
9 Interworking considerations
|
..................................................................................................................14 Annex A: Change history ..............................................................................................................................15 History..............................................................................................................................................................16 (3G TS 22.067 version 3.0.1 Release 1999) ETSI ETSI TS 122 067 V3.0.1 (2000-01) 3GPP 3G TS 22.067 V3.0.1 (1999-10) 5 3G TS 22.067 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; (3G TS 22.067 version 3.0.1 Release 1999) ETSI ETSI TS 122 067 V3.0.1 (2000-01) 3GPP 3G TS 22.067 V3.0.1 (1999-10) 6 3G TS 22.067 version 3.0.1 1 Scope The present document specifies the stage 1 description of the enhanced Multi-Level Precedence and Pre-emption Service (eMLPP). This service has two parts: precedence and pre-emption. Precedence involves assigning a priority level to a call in combination with fast call set-up. Pre-emption involves the seizing of resources, which are in use by a call of a lower precedence, by a higher level precedence call in the absence of idle resources. Pre-emption can also involve the disconnection of an on-going call of lower precedence to accept an incoming call of higher precedence. The eMLPP service is provided as a network operator's option to a domain of a network. The domain can be the whole network or a subset of the network. The eMLPP service applies to all network resources in the domain that is in common use. The eMLPP service is applicable to all mobile stations in the domain with all or some mobile stations having a respective subscription assigning precedence according to the eMLPP service. eMLPP is a supplementary service and shall be provided to a subscriber for all basic services subscribed to and for which eMLPP applies. NOTE: It is under study whether normal GSM Phase 2 Mobile Stations will be able to be used for this service. The service 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 services and features. The present document does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate specifications. The present document is applicable to teleservices 1x and 6x and to all bearer services used in a mobile network if eMLPP is provided. Any interaction with other services and/or networks not dealt with in clauses 8 or 9 are outside the scope of the present document. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. • 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.024: "Description of Charge Advice Information (CAI)". [4] GSM 02.40: "Digital cellular telecommunications system (Phase 2+); Procedures for call progress indications". [5] TS 22.068: "Voice Group Call Service (VGCS) - Stage 1". (3G TS 22.067 version 3.0.1 Release 1999) ETSI ETSI TS 122 067 V3.0.1 (2000-01) 3GPP 3G TS 22.067 V3.0.1 (1999-10) 7 3G TS 22.067 version 3.0.1 [6] TS 22.069: "Voice Broadcast Service (VBS) - Stage 1". [7] GSM 03.05: "Digital cellular telecommunications system (Phase 2+); Technical performance objectives". [8] TS 23.068: "Voice Group Call Service (VGCS) - Stage 2". [9] TS 23.069: "Voice Broadcast Service (VBS) - Stage 2". [10] ITU-T Recommendation I.255.3: "ISDN Multi-Level Precedence and Pre-emption (MLPP) stage 1". [11] 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: calling subscriber: Service subscriber which invokes the eMLPP service. network operator: Entity which provides the network operating elements and resources for the execution of the enhanced Multi-Level Precedence and Pre-emption service (eMLPP). precedence: Precedence is the priority associated with a call. service provider: Entity which offers the eMLPP service for subscription. The network operator may be the service provider. service subscriber: Mobile subscriber which subscribes to the eMLPP service. In principle, if a network provides eMLPP service, all users are able to subscribe to this service. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply, in addition to those listed in GSM 01.04 and TR 21.905 [11]: eMLPP enhanced Multi-Level Precedence and Pre-emption 4 Description a) The enhanced Multi-Level Precedence and Pre-emption service (eMLPP) provides different levels of precedence for call set-up and for call continuity in case of handover. eMLPP shall be applicable also in case of roaming if supported by the related networks. The maximum precedence level of a subscriber is set at the subscription time by the service provider, based on the subscriber's need. The subscriber may select a precedence level up to and including the maximum precedence level subscribed to, on a per call basis. There are at maximum 7 priority levels. The two highest levels are reserved for network internal use, e.g. for emergency calls or the network related service configurations for specific voice broadcast or voice group call services. These two levels can only be used locally, i.e. in the domain of one MSC. The other five priority levels are offered for subscription and can be applied globally, e.g. on inter switch trunks, if supported by all related network elements, and also for interworking with ISDN networks providing the MLPP service. The seven priority levels are defined as follows: A (highest, for network internal use). (3G TS 22.067 version 3.0.1 Release 1999) ETSI ETSI TS 122 067 V3.0.1 (2000-01) 3GPP 3G TS 22.067 V3.0.1 (1999-10) 8 3G TS 22.067 version 3.0.1 B (for network internal use). 0 (for subscription). 1 (for subscription). 2 (for subscription). 3 (for subscription). 4 (lowest, for subscription). Levels A and B shall be mapped to level 0 for priority treatment outside of the MSC area in which they are applied. b) Priorities shall be treated in the network as defined for the following call scenarios: - Mobile originated calls: - The priority level depends on the calling subscriber. - If the user has no eMLPP subscription, the call shall have a default priority level defined in the network. - If the user has an eMLPP subscription, the call shall have the priority level selected by the user at set-up or the priority level predefined by the subscriber as default priority level by registration. - Mobile terminated calls: - The priority level depends on the calling party. For this, interworking with the ISDN MLPP (Multi-Level Precedence and Pre-emption) service is required. - If the call is not an ISDN MLPP call, i.e. no priority level is defined, the call shall be treated in the mobile network with a default priority level. - If the call is an ISDN MLPP call, the call shall be treated with the priority level provided by the interfacing network. - Mobile-to-mobile calls in case of roaming: The priority shall be treated for the calling subscriber as for mobile originated calls and for the called subscriber as for mobile terminated calls. - Mobile-to-mobile calls in one network: The priority shall be treated for the calling subscriber as for mobile originated calls and for the called subscriber as for mobile terminated calls. - Voice broadcast (VBS) and voice group calls (VGCS): At the first instances of the voice broadcast or voice group call, when there is only a link between the calling mobile station and the network, the call shall be treated as defined for mobile originated calls. Then, for the set-up of the voice broadcast or voice group call links in the related cells, the call shall have the priority level as defined for the related voice broadcast or voice group call in the network. c) There are three classes of set-up time performance and examples of the call set-up times are: - class 1 fast set-up 1-2 s; - class 2 normal set-up < 5 s; - class 3 slow set-up < 10 s. The achievement of the set-up times depends on technical realizations and network planning. Mechanisms shall be implemented to provide the performance defined by the service provider under normal circumstances (no congestion). They do not include any allowance for user reaction times. The call set-up time is considered to be the time from pressing the "send" button to the point at which the called party, or at least one called party in the case of a multi-party, voice group or voice broadcast call, can receive information. (3G TS 22.067 version 3.0.1 Release 1999) ETSI ETSI TS 122 067 V3.0.1 (2000-01) 3GPP 3G TS 22.067 V3.0.1 (1999-10) 9 3G TS 22.067 version 3.0.1 The class 1 figures depend on the required connection type and service and will have to be considered accordingly. It is assumed that for calls which originate or terminate in external networks, 25 % of the set-up time is spent in these external networks. The procedures assume normal operating conditions apply, e.g. GSM reference loads as defined in GSM 03.05, the mobile station is in an area of sufficient coverage, the mobile station is not busy, no call redirection is in place, etc. d) Calls with a high priority requiring a class 1 set-up may not require authentication at call set-up nor confidentiality on the radio link. e) For precedence calls, the network shall have the possibility to pre-empt on-going calls with lower priority, in ascending order of priority, in case of congestion at set-up on the radio interface or the GSM network side, respectively, or at handover of the precedence call to a congested cell. In case of necessary pre-emption of another on-going call at set-up, the successful call set-up may exceed the set-up time performance defined under c) but shall be completed as soon as possible. A call can be pre-empted any time after the precedence level of the call has been established and before call clearing has begun. Pre-emption shall only be performed to provide precedence for those priority levels which have a pre-emption capability allocated by the network operator. Priority levels with no pre-emption capability allocated shall only have queuing priority. f) A subscriber shall be able to set her mobile station to automatic answer a call if the incoming call is of or exceeds a defined priority level, respectively. In case of called mobile subscriber busy, the on-going call shall be pre-empted (or set automatically on call hold by the mobile station in case of telephony and if the subscriber is entitled to call hold services) to accept the incoming call with the priority defined for automatic answering. If the on-going call is a point-to-point call, this function is only possible if the subscriber has a subscription for Call Waiting (CW). NOTE: A pre-emption of an on-going call is not possible if the on-going call is a TS12 call (emergency call). The definition of the priority level which shall cause automatic answering of an incoming call or pre-emption of another on-going call shall be stored in the mobile station and can be changed by the subscriber. If a mobile station does not automatically accept an incoming call while being idle and the user does not accept the call, the call may be forwarded to another party if Call Forwarding on No Reply (CFNRy) applies. If a mobile station does not pre-empt an on-going point-to-point call to accept an incoming call of higher priority, the call is indicated by CW and the user may still accept the incoming call. It the user rejects CW, the call may be forwarded to another party if Call Forwarding on mobile station Busy (CFB) applies. If the mobile station does not pre-empt an on-going voice broadcast or voice group call to accept an incoming call of higher priority, the call may be forwarded to another party if CFNRy applies. g) The network operator can allocate set-up classes and resource pre-emption capabilities to each priority level. Table 1 presents an example for the assignment of priority levels and the corresponding parameters. Table 1: Example on eMLPP service composition Priority level Set-up time Pre-emption Examples A class 1 yes VBS/VGCS emergency applications B class 2 yes Operators calls 0 class 2 yes TS12 Emergency calls 1 class 3 yes Premium rate calls 2 class 3 no Standard rate calls 3 class 3 no Default for no eMLPP subscription 4 class 3 no Low tariff calls (3G TS 22.067 version 3.0.1 Release 1999) ETSI ETSI TS 122 067 V3.0.1 (2000-01) 3GPP 3G TS 22.067 V3.0.1 (1999-10) 10 3G TS 22.067 version 3.0.1 Network operators which provide the eMLPP service for subscription need to consider the interrelation of the number of subscriptions offered (possibly restricted for particular users), the technical performance and the network planning issues in order to guarantee the service performance for the subscriber. h) In case of pre-emption the pre-empted subscriber shall be provided with a suitable indication. 4.1 Applicability to telecommunication services The applicability of this supplementary service is defined in TS 22.004. The effects of the eMLPP service are applicable, potentially, to all subscribers in a network, should a precedence call set-up or handover occur and pre-emption be necessary. 5 Normal operation with successful outcome 5.1 Provision A maximum authorized precedence level is provided to a service subscriber after prior arrangements with the service provider. Service subscribers without an eMLPP subscription are assigned to a default priority level (in case of emergency calls, TS12, exceptions shall be possible). 5.2 Withdrawal The maximum authorized precedence level can be changed or the complete eMLPP service withdrawn at the subscriber's request or for administrative reasons. 5.3 Registration The definition of the priority level to be used as default level at mobile originated call establishment shall be registered in the network. This default level will be used if a subscriber has a subscription for a priority level higher than the lowest priority level and has not selected a priority level at call set-up. Registration can take place either by the service provider or with an appropriate control procedure by the subscriber. If the subscriber requests a priority level higher than the maximum entitled one then the network shall reject this registration with an appropriate indication to the subscriber. 5.4 Erasure Erasure of a default priority level is done as a result of a new registration overruling, and thus effectively erasing the previous registration. 5.5 Network related service configuration The allocation of eMLPP priority levels to the call set-up classes and the possibility of pre-emption of on-going calls in case of congestion will be arranged by the network operator for a specific composition of the eMLPP service in a network. This is not related to one specific service subscriber. An example is given in table 1 of clause 4. 5.6 Activation Not applicable. (3G TS 22.067 version 3.0.1 Release 1999) ETSI ETSI TS 122 067 V3.0.1 (2000-01) 3GPP 3G TS 22.067 V3.0.1 (1999-10) 11 3G TS 22.067 version 3.0.1 5.7 Deactivation Not applicable. 5.8 Invocation The eMLPP shall be invoked automatically by the network at call set-up. The precedence level may be selected by the user on a per call basis. The user may select any precedence level up to and including her maximum authorized precedence level. The maximum authorized precedence level shall be stored on the SIM/USIM and the mobile station shall check that only an authorized level is used for set-up. In addition, it shall be possible to verify in the network the level used at set-up against the maximum authorized level. If the user has not selected a precedence level at set-up, the network shall apply the subscriber specific default precedence level. If the user has selected a precedence level higher than the maximum authorized level, the maximum authorized precedence level shall be applied for the call. 5.9 Normal operation At invocation of the eMLPP on a call set-up, the network notes the call priority related to the call and decides on the respective actions to be taken, i.e. on queuing priority, fast call set-up procedures and possibly pre-emption in case of congestion of network resources. In case of pre-emption the network shall release the lowest lower priority call and seize the necessary resources that are required to set-up the higher priority call. Once set for a call, the precedence level cannot be changed. In the case of automatic answering of an incoming call with a sufficient priority level, the alerting indication to the calling party may not be provided in order shorten the set-up time. In case of called mobile subscriber busy, the on-going call shall be released if automatic answering applies (or set on call hold in case of a telephony call) to accept an incoming call of higher priority. When pre-emption applies, at handover to a congested cell, higher priority calls shall replace those of the lowest priority. The pre-empted user shall receive an indication for congestion as defined in GSM 02.40. 5.10 Interrogation A service subscriber may interrogate the range of priority levels he can use and the default priority level used for mobile originated call establishment. 5.11 Charging requirements The utilized precedence level shall be able to be extracted from the event records if different from the default precedence level. 6 Exceptional procedures or unsuccessful outcome When a service subscriber makes a call, he expects the network to automatically invoke the eMLPP service according to her subscription. If the network cannot provide the service for some reason an indication shall be provided to the service subscriber to notify her of the absence or modification of the priority handling. Exceptional procedures for voice group call and voice broadcast call establishment durations exceeding the specified times are given in TS 22.068 and TS 22.069, respectively. (3G TS 22.067 version 3.0.1 Release 1999) ETSI ETSI TS 122 067 V3.0.1 (2000-01) 3GPP 3G TS 22.067 V3.0.1 (1999-10) 12 3G TS 22.067 version 3.0.1 7 Alternate procedures None identified. 8 Interaction with other supplementary services 8.1 Calling Line Identification Presentation (CLIP) No interaction. 8.2 Calling Line Identification Restriction (CLIR) No interaction. 8.3 Connected Line Identification Presentation (COLP) No interaction. 8.4 Connected Line Identification Restriction (COLR) No interaction. 8.5 Call Forwarding Unconditional (CFU) The CFU service takes precedence over the eMLPP service. The precedence level of calls shall be preserved during the forwarding process. No interaction except for voice broadcast and voice group calls (see the respective stage 1 descriptions TS 22.069 and TS 22.068 ). 8.6 Call Forwarding on mobile subscriber busy (CFB) An incoming call with higher priority level shall override CFB in case of CW (see item f of clause 4). If the mobile station does not pre-empt the on-going call of lower priority and the user rejects the CW, the call may be forwarded to another party if CFB applies. 8.7 Call Forwarding on No Reply (CFNRy) If a mobile station does not automatically accept an incoming call while being idle and the user does not accept the call, the call may be forwarded to another party if CFNRy applies. 8.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc) No interaction. (3G TS 22.067 version 3.0.1 Release 1999) ETSI ETSI TS 122 067 V3.0.1 (2000-01) 3GPP 3G TS 22.067 V3.0.1 (1999-10) 13 3G TS 22.067 version 3.0.1 8.9 Call Waiting (CW) Pre-emption of on-going point-to-point calls to accept incoming calls of higher priority is only possible if the subscriber has a CW subscription. The CW indication to the mobile station shall imply the precedence level in order to enable the mobile station to decide on automatic accepting of the waiting call. 8.10 Call Hold A held call may be pre-empted due to lack of network resources. The call is cleared and the pre-empted user shall receive an appropriate indication. 8.11 Multi-party Service (MPTY) eMLPP shall apply to the different call legs of a MPTY as for other calls. 8.12 Closed User Group (CUG) No interaction. eMLPP shall not override CUG restrictions, except high priority calls shall override CUG restrictions as a network option. 8.13 Advice of Charge (AoC) No interactions. NOTE: Different charge metres for different priorities can be obtained e.g. by variation of the e1 or e2 parameters of the charge advice information according to TS 22.024. 8.14 Barring of Outgoing Calls (BAOC) High priority calls shall override BAOC as a network option. 8.15 Barring of Outgoing International Calls (BOIC) High priority calls shall override BOIC as a network option. 8.16 Barring of Outgoing International Calls except those to the Home PLMN country (BOIC-exHC) High priority calls shall override BOIC-exHC as a network option. 8.17 Barring of All Incoming Calls (BAIC) An incoming high priority call shall override BAIC as a network option. 8.18 Barring of Incoming Calls when Roaming outside the home PLMN country (BIC-Roam) See subclause 8.17. (3G TS 22.067 version 3.0.1 Release 1999) ETSI ETSI TS 122 067 V3.0.1 (2000-01) 3GPP 3G TS 22.067 V3.0.1 (1999-10) 14 3G TS 22.067 version 3.0.1 8.19 Call Transfer (ECT) For a normal call transfer, the precedence level of calls is preserved during the transfer process. Interworking of the eMLPP service with other networks shall be provided based on the MLPP service specified in ITU-T Recommendation I.255.3 or a possibly future EN related to MLPP. For this interworking it shall be considered that: - precedence levels A and B shall be mapped to precedence level 0 (see clause 4); - pre-emption of network resources and on-going calls in the interfacing network will be performed according to the MLPP service, i.e. pre-emption will only affect other MLPP subscribers; - other details in the treatment of precedence calls as specified for MLPP which are different to eMLPP. The precedence level of a call except levels A and B shall not be changed when interworking with networks providing MLPP. (3G TS 22.067 version 3.0.1 Release 1999) ETSI ETSI TS 122 067 V3.0.1 (2000-01) 3GPP 3G TS 22.067 V3.0.1 (1999-10) 15 3G TS 22.067 version 3.0.1 Annex A: Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.67 7.0.0 Transferred to 3GPP SA1 SA#04 22.067 3.0.0 SA#05 22.067 3.0.0 001 R99 3.0.1 Editorial update of references for GSM/3GPP use. (3G TS 22.067 version 3.0.1 Release 1999) ETSI ETSI TS 122 067 V3.0.1 (2000-01) 16 ETSI ETSI TS 122 067 V3.0.1 (2000-01) (3G TS 22.067 version 3.0.1 Release 1999) History Document history V3.0.1 January 2000 Publication
|
2b997f793085bd3d48236a874636bb22
|
122 140
|
1 Scope
|
........................................................................................................................................................5
|
2b997f793085bd3d48236a874636bb22
|
122 140
|
2 References
|
................................................................................................................................................5
|
2b997f793085bd3d48236a874636bb22
|
122 140
|
3 Definitions and abbreviations
|
..................................................................................................................6
|
2b997f793085bd3d48236a874636bb22
|
122 140
|
3.1 Definitions
|
......................................................................................................................................................... 6
|
2b997f793085bd3d48236a874636bb22
|
122 140
|
3.2 Abbreviations
|
..................................................................................................................................................... 6
|
2b997f793085bd3d48236a874636bb22
|
122 140
|
4 High level Requirements
|
.........................................................................................................................6
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.