ETSI ETR 064 TECHNICAL December 1992 REPORT

Similar documents
ETSI ETR TECHNICAL December 1992 REPORT

EUROPEAN pr ETS TELECOMMUNICATION February 1996 STANDARD

EUROPEAN ETS TELECOMMUNICATION March 1996 STANDARD

EUROPEAN ETS TELECOMMUNICATION October 1991 STANDARD

ETSI ETR 286 TECHNICAL January 1996 REPORT

EUROPEAN ETS TELECOMMUNICATION March 1992 STANDARD

ETSI ETR 302 TECHNICAL September 1996 REPORT

GSM GSM TECHNICAL November 1996 SPECIFICATION Version 5.1.0

EUROPEAN ETS TELECOMMUNICATION February 1995 STANDARD

GSM GSM TECHNICAL July 1996 SPECIFICATION Version 5.0.0

EUROPEAN ETS TELECOMMUNICATION May 1997 STANDARD

EUROPEAN ETS TELECOMMUNICATION October 1991 STANDARD

ETSI ETR 144 TECHNICAL October 1994 REPORT

EUROPEAN ETS TELECOMMUNICATION December 1991 STANDARD

EUROPEAN ETS TELECOMMUNICATION May 1995 STANDARD

Draft EN V1.1.1 ( )

Draft EG V1.1.1 ( )

EUROPEAN ETS TELECOMMUNICATION October 1997 STANDARD

ETSI ETR 046 TECHNICAL July 1992 REPORT

This amendment A2 modifies the European Telecommunication Standard ETS (1990)

GSM GSM TECHNICAL July 1996 SPECIFICATION Version 5.0.2

ETSI ETR 109 TECHNICAL October 1993 REPORT

ETSI ETR 121 TECHNICAL February 1994 REPORT

Draft EN V1.2.1 ( )

EUROPEAN ETS TELECOMMUNICATION March 1994 STANDARD

EUROPEAN ETS TELECOMMUNICATION October 1993 STANDARD

ETSI ETR 123 TECHNICAL February 1994 REPORT

GSM GSM TECHNICAL December 1996 SPECIFICATION Version 5.0.0

ETSI ETR 174 TECHNICAL April 1995 REPORT

ETSI EN V1.2.1 ( )

This amendment A1 modifies the European Telecommunication Standard ETS (1991)

JP-3GA (R99) Line Identification Supplementary Services; Stage 1

GSM GSM TECHNICAL December 1995 SPECIFICATION Version 5.0.0

EUROPEAN ETS TELECOMMUNICATION November 1996 STANDARD

EUROPEAN ETS TELECOMMUNICATION July 1995 STANDARD

TR V1.1.1 ( )

TS V6.0.0 ( )

GSM GSM TECHNICAL December 1995 SPECIFICATION Version 5.0.0

ETSI ETR 346 TECHNICAL December 1996 REPORT

TS V6.0.0 ( )

GSM GSM TECHNICAL July 1996 SPECIFICATION Version 5.0.0

ETSI ETR 018 TECHNICAL November 1995 REPORT

EUROPEAN pr ETS TELECOMMUNICATION May 1996 STANDARD

JP-3GA (R99) Calling Name Presentation (CNAP); Stage 1 (T1P1)

EUROPEAN ETS TELECOMMUNICATION September 1994 STANDARD

ETSI ETR 325 TECHNICAL December 1996 REPORT

EUROPEAN ETS TELECOMMUNICATION January 1996 STANDARD

Draft EN V1.1.1 ( )

Final draft EN V1.2.1 ( )

Draft EN V1.2.3 ( )

TS-3GA (R99)v Operator Determined Call Barring

TR V1.1.1 ( )

EUROPEAN ETS TELECOMMUNICATION April 1997 STANDARD

GSM GSM TECHNICAL August 1998 SPECIFICATION Version 5.2.0

ETSI ETR 006 TECHNICAL December 1990 REPORT

EN V1.2.2 ( )

TS V6.0.0 ( )

GSM GSM TECHNICAL December 1995 SPECIFICATION Version 5.0.0

TR V1.1.1 ( )

EUROPEAN ETS TELECOMMUNICATION July 1994 STANDARD

EN V1.1.1 ( )

3GPP TS V7.0.0 ( )

ETSI TCR-TR 008 TECHNICAL COMMITTEE August 1993 REFERENCE TECHNICAL REPORT

EN V1.2.4 ( )

EUROPEAN ETS TELECOMMUNICATION September 1994 STANDARD

Draft EN V1.2.3 ( )

EUROPEAN ETS TELECOMMUNICATION September 1994 STANDARD

EUROPEAN ETS TELECOMMUNICATION February 1995 STANDARD

ETSI TS V3.3.1 ( )

EUROPEAN ETS TELECOMMUNICATION November 1995 STANDARD

EUROPEAN ETS TELECOMMUNICATION September 1996 STANDARD

EUROPEAN ETS TELECOMMUNICATION January 1994 STANDARD

EUROPEAN ETS TELECOMMUNICATION May 1995 STANDARD

Final draft EN V1.2.2 ( )

GSM GSM TECHNICAL March 1996 SPECIFICATION Version 5.1.0

EUROPEAN pr ETS TELECOMMUNICATION March 1996 STANDARD

EUROPEAN prets TELECOMMUNICATION November 1998 STANDARD

This amendment A1 modifies the European Telecommunication Standard ETS (1992) Terminal Equipment (TE); Group 3 facsimile equipment ETSI

EUROPEAN ETS TELECOMMUNICATION April 1993 STANDARD

ES V1.1.1 ( )

3GPP TS V ( )

EN V1.2.4 ( )

EN V1.2.4 ( )

EN V3.1.3 ( )

ETSI TS V7.0.0 ( )

ETSI TS V3.1.0 ( )

ETSI TS V4.1.0 ( )

EUROPEAN ETS TELECOMMUNICATION August 1997 STANDARD

Tdoc SMG P ETSI SMG#28 Milan 8-12 February Source: SMG3 Subject: Update of GSM 09.14

EUROPEAN pr ETS TELECOMMUNICATION August 1996 STANDARD

EG V1.2.1 ( )

EN V1.1.1 ( )

GSM GSM TECHNICAL May 1996 SPECIFICATION Version 5.0.0

ETSI TCR-TR 006 TECHNICAL COMMITTEE October 1992 REFERENCE TECHNICAL REPORT

ETSI TS V5.0.0 ( )

EN V1.2.4 ( )

EUROPEAN ETS TELECOMMUNICATION September 1994 STANDARD

EN V1.2.4 ( )

EN V1.2.2 ( )

Draft ETSI EG V3.1.1 ( )

Transcription:

ETSI ETR 064 TECHNICAL December 1992 REPORT Source: ETSI TC-NA Reference: DTR/NA-70304 ICS: 33.080 Key words: UPT, Interaction Universal Personal Telecommunication (UPT); Requirements on feature interaction and network functionalities ETSI European Telecommunications Standards Institute ETSI Secretariat * Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16 Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 1992. All rights reserved.

Page 2 Whilst every care has been taken in the preparation and publication of this document, errors in content, typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to "ETSI Editing and Committee Support Dept." at the address shown on the title page.

Page 3 Contents Foreword...5 1 Scope...7 2 References...7 3 Abbreviations...7 4 The feature interaction model...7 5 Service subscription interactions...8 5.1 A UPT user makes an outgoing call from a fixed or mobile terminal without prior registration...8 5.2 A UPT user registers to make multiple outgoing calls from a fixed terminal...8 5.3 A UPT user registers to make multiple outgoing calls from a mobile terminal...8 5.4 Incoming call to a UPT user registered at a fixed or mobile terminal...9 6 Methodology for identifying network functionalities for feature interaction...9 7 UPT features...9 8 Serving networks...10 9 Feature interaction issues and solutions...10 History...12

Page 4 Blank page

Page 5 Foreword ETSI Technical Reports (ETRs) are informative documents resulting from ETSI studies which are not appropriate for European Telecommunication Standard (ETS) or Interim-European Telecommunication Standard (I-ETS) status. An ETR may be used to publish material which is either of an informative nature, relating to the use or application of ETSs or I-ETSs, or which is immature and not yet suitable for formal adoption as an ETS or I-ETS. This ETSI Technical Report (ETR) provides a general discussion on the interaction between Universal Personal Telecommunication (UPT) features and the features and supplementary services of the serving network. It also provides some guidelines on how to analyse the issues and required functionalities.

Page 6 Blank page

Page 7 1 Scope This ETSI Technical Report (ETR) provides a general discussion on the interaction between Universal Personal Telecommunication (UPT) features and the features and supplementary services of the serving network. It also provides some guidelines on how to analyse the issues and required functionalities. Specific issues and functionalities for the different UPT phases are discussed in the appropriate documents, for UPT phase 1 this is DTR/NA-71304 [1], an ETR is also planned for UPT phase 2. 2 References The following reference is used within this ETR. [1] DTR/NA-71304: "Universal Personal Telecommunication (UPT) Phase 1: Network functionalities for feature interaction". 3 Abbreviations For the purposes of this ETR, the following abbreviations are used. CFU CLIP CLIR COLP COLR FPLMTS GSM ISDN MCID PLMN PSTN UMTS UPT Call Forwarding Unconditional Calling Line Identification Presentation Calling Line Identification Restriction Connected Line identification Presentation Connected Line identification Restriction Future Public Land Mobile Telecommunication Service Global System for Mobile communications Integrated Services Digital Network Malicious Call Identification Public Land Mobile Network Public Switched Telephone Network Universal Mobile Telecommunication System Universal Personal Telecommunication 4 The feature interaction model UPT, being a package of services, will have interactions with other services or service features. These interactions can occur at the time of: 1) service/feature introduction in the network; 2) service/feature subscription; 3) service/feature invocation by the user; 4) service/feature operation.

Page 8 It is also noted that interactions may occur, at least: a) among different features associated to the same UPT related service; b) between features associated to the UPT service for a given UPT subscriber and features associated with other services that the same subscriber may have invoked or subscribed to; c) between features associated to the UPT service for a given UPT subscriber and features associated with possible services related to the terminal/calling line onto which that subscriber is currently registered. As a principle, in UPT, supplementary services should be independent of those offered by the serving network. Thus activation of a UPT supplementary service from a specific terminal should not affect, and should not be affected by, the supplementary services offered to, or activated by, the terminal by virtue of its association with its serving network. 5 Service subscription interactions There are four scenarios that can be considered which illustrate terminal and UPT service subscription interactions. In each of these scenarios the replying of terminating exchanges, identified supports UPT. 5.1 A UPT user makes an outgoing call from a fixed or mobile terminal without prior registration In accordance with current network operation, a call set-up request would be checked against the terminal-related services subscription. However, the UPT user will expect his/her service subscription ("service profile") to apply. Therefore, the serving exchange must be able to distinguish an outgoing call made by a UPT user, from an outgoing call made by a non-upt user. Furthermore, the exchange must be able to identify which UPT user is making the call, so that the user's specific services can be provided. Therefore, a UPT user identification/authentication process is also required. The UPT user should be able to make user of any service which is subscribed in the user's service profile with the exception of services which the serving 1) exchange of the terminal is unable to support. In addition, the services to which the terminal itself is subscribed should have no impact on the user's request. For example, the terminal may not be subscribed to abbreviated dialling but the UPT user may be subscribed. The exchange should accept an abbreviated number in a UPT call set-up request and use information in the UPT user's service profile to determine the full called number. 5.2 A UPT user registers to make multiple outgoing calls from a fixed terminal The UPT user may want to make multiple outgoing calls without going through an identification/authentication process before each call. Therefore, UPT user registers so that the serving exchange will treat all subsequent outgoing calls as UPT calls from that user. Unlike the case given in subclause 5.1, the serving exchange must now "remember" who the user is in order to properly handle subsequent calls as UPT calls rather than as traditional terminal calls. 5.3 A UPT user registers to make multiple outgoing calls from a mobile terminal This case is similar to the case given in subclause 5.2, as long as the mobile terminal is served by the same exchange (network) through which the user registered. However, if the mobile terminal moves to another area, existing mobile network procedures only provide the new serving exchange (network) with information about the terminal; the information associated with the UPT user registration is not provided. 1) The serving exchange serves the terminal.

Page 9 Therefore, the new serving exchange will treat subsequent outgoing calls as terminal calls but the user will expect them to continue to be treated as UPT calls. This situation requires that either the user re-register or the previous serving exchange must be able to provide UPT user registration information to the new serving exchange. The latter alternative is preferable. However, the transfer of such information should ideally be done without changing existing mobile network procedures. 5.4 Incoming call to a UPT user registered at a fixed or mobile terminal UPT users will expect their subscribed services to apply for both outgoing and incoming calls. Incoming calls to UPT users are made by the caller (UPT user or non-upt user) dialling the user's UPT number. Information in the UPT user's service profile is used to determine the routing for the call. However, if the call is routed in the traditional manner, the terminating exchange will not be able to distinguish a call made to the terminal from a call made to a UPT user at that terminal. Therefore, only the terminal-related services would be provided. For example, if the UPT user subscribes to call waiting but the terminal is not subscribed to call waiting, then call waiting would not be provided, but this is not what the UPT user would expect. Therefore, it must be possible for the terminating exchange to distinguish incoming UPT calls from non-upt calls. Furthermore, if more than one UPT user is associated with the same terminal, the terminating exchange must be able to distinguish the specific UPT user for which the call is intended, so that user's specific services are provided. 6 Methodology for identifying network functionalities for feature interaction In order to define the UPT requirements for feature interaction for the given UPT implementation phases, the following procedure is recommended: - identification of the UPT features that apply for the UPT phase considered; - identification of the features and supplementary services of the serving network; - analysis and mapping of the above features; - identification of the feature interaction issues; - identification of possible solutions; - formulation of required (additional) functionalities. 7 UPT features Two categories of UPT features have been identified: - core UPT features, i.e. those features which are fundamental for the UPT service concept, and are considered essential for UPT provision; - additional UPT features, i.e. those features which are additional to the fundamental UPT service concept. Additional UPT features may be considered essential or optional for UPT provision. The core and additional UPT features that apply for the UPT implementation phase considered must be taken from the relevant ETRs.

Page 10 8 Serving networks The features and supplementary services of the serving networks that apply for the phase considered must be analysed. Examples of serving networks are: a) Public Switched Telephone Network (PSTN), the public telephony network; b) Integrated Services Digital Network (ISDN), with some restrictions in the initial UPT implementation phases; c) Public Land Mobile Networks (PLMNs): - mobile GSM; - UMTS; and - FPLMTS; will be considered; - analogue mobile networks do not need to be considered. 9 Feature interaction issues and solutions A mapping is performed between the UPT features and the features and supplementary services of each serving network. Interactions are defined based on the analysis described in the preceding Clauses, and solutions proposed. A sample of the mapping in case of ISDN is given in table 1. Table 1: Interaction issues - ISDN (sample) Features/supplementary services of serving network UPT features CLIP CLIR COLP COLR MCID CFU... InCall registration Outgoing UPT call set-up OutCall registration AllCall registration Linked registration CLIP: Calling Line Identification Presentation CLIR: Calling Line Identification Restriction COLP: Connected Line identification Presentation COLR: Connected Line identification Restriction (1) CFU: Call Forwarding Unconditional MCID:Malicious Call Identification

Page 11 As an example, the table indicates an interaction issue between the call forwarding unconditional supplementary service and InCall registration ((1) in table 1). A conflict exists if a UPT subscriber registers for incoming calls on a terminal on which the call forwarding unconditional supplementary service has been invoked ((1) in table 1). The following solutions have been identified to avoid counteraction of these features: - InCall registration is not possible in this case; - InCall registration overrides the call forwarding unconditional supplementary service. This solution requires the capability of distinguishing UPT calls from non-upt calls and resulting additional actions.

Page 12 History Document history December 1992 First Edition