hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
---|---|---|---|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4.3.1 Cell selection and reselection
|
....................................................................................................................... 7
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4.3.2 Localised service area indication
|
................................................................................................................. 7
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4.3.3 Exclusive access
|
........................................................................................................................................... 7
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4.3.4 LSA only access
|
........................................................................................................................................... 8
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4.4 Localised Service Area support in active mode
|
................................................................................................. 8
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4.4.1 Localised service area indication
|
................................................................................................................. 8
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4.4.2 Resource handling
|
........................................................................................................................................ 8
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4.5 Localised Service Area support in access control
|
.............................................................................................. 8
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4.5.1 Emergency Call setup
|
................................................................................................................................... 8
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4.5.2 Mobile Originating and Mobile Terminating Call setup
|
.............................................................................. 8
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4.5.3 Location Registration
|
................................................................................................................................... 9
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4.5.4 Call unrelated services (Short message transfer, USSD, Supplementary Service management)
|
................. 9
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
4.5.5 Routing Area Update
|
.................................................................................................................................... 9
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
5 General architecture
|
.................................................................................................................................9
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
6 Compatibility issues
|
.................................................................................................................................9
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
6.1 Handling of mobiles in exclusive access cells
|
................................................................................................. 10
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
7 Transmission
|
..........................................................................................................................................10
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
8 Information storage
|
................................................................................................................................10
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
8.1 Information managed per subscriber
|
............................................................................................................... 10
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
8.1.1 Stored in the HLR
|
...................................................................................................................................... 10
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
8.1.2 Stored in the VLR
|
...................................................................................................................................... 11
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
8.1.3 Stored in the SIM
|
....................................................................................................................................... 11
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
8.1.4 Stored in the SGSN
|
.................................................................................................................................... 11
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
8.2 Information managed per LSA
|
........................................................................................................................ 12
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
8.2.1 Stored in the MSC
|
...................................................................................................................................... 12
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
8.2.2 Stored in the BSS
|
....................................................................................................................................... 12
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
9 Identities
|
................................................................................................................................................12
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
9.1 Identities for LSA
|
............................................................................................................................................ 12
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
9.1.1 LSA ID
|
....................................................................................................................................................... 12
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
9.1.2 LSA name
|
.................................................................................................................................................. 12
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
10 Operation and maintenance aspects
|
.......................................................................................................13
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11 Function and information flows
|
.............................................................................................................13
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.1 LSA management
|
............................................................................................................................................ 13
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.2 Subscription management
|
................................................................................................................................ 13
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.3 Update of LSA data in SIM
|
............................................................................................................................. 13
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.4 Functions related to MS in idle mode for support of LSA
|
............................................................................... 13
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.4.1 Broadcast information
|
................................................................................................................................ 13
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.4.2 Cell selection and reselection.
|
.................................................................................................................... 14 (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 4 3G TS 23.073 version 3.0.0
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.4.3 Location Updating
|
...................................................................................................................................... 14
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.4.4 Routing Area Update
|
.................................................................................................................................. 14
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.5 Transfer of information from HLR to VLR
|
..................................................................................................... 14
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.6 Transfer of information from HLR to SGSN
|
................................................................................................... 14
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.7 Functions related to active mode support of LSA
|
............................................................................................ 14
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.7.1 MS connection establishment
|
..................................................................................................................... 14
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.7.1.1 Indication of current LSA to the MSC
|
.................................................................................................. 14
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.7.1.2 Indication of allowed LSA to the BSS
|
.................................................................................................. 15
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.7.1.3 Indication of allowed LSA to the BSS
|
.................................................................................................. 15
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.7.2 Handover
|
.................................................................................................................................................... 15
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.7.2.1 Indication of allowed LSA to the target BSS
|
....................................................................................... 15
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.7.2.2 Indication of current LSA to the MSC
|
.................................................................................................. 15
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.7.2.3 Indication of current LSA to the SGSN
|
................................................................................................ 15
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.8 LSA indication procedures
|
.............................................................................................................................. 15
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.8.1 Indication for mobile stations in idle mode
|
................................................................................................ 15
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.8.2 Indications for mobile stations in active mode
|
........................................................................................... 16
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
11.9 Overview of signalling
|
..................................................................................................................................... 16
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
12 Charging
|
.................................................................................................................................................20
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
12.1 General principles
|
............................................................................................................................................ 20
|
2b7cc08a6cda16cef78883d84a691685
|
123 073
|
12.2 Toll ticketing
|
.................................................................................................................................................... 20 Annex A (informative): SoLSA interworking with CAMEL.............................................................21 A.1 Subscriber information for Localised Service Area...............................................................................21 A.2 Network Architecture ............................................................................................................................21 A.3 Signalling Interworking .........................................................................................................................22 Annex B (informative): Change history...............................................................................................24 History..............................................................................................................................................................25 (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 5 3G TS 23.073 version 3.0.0 Foreword This Technical Specification has been produced by the 3GPP. This TS specifies the stage 2 description of the SoLSA service within the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; 1 Scope This document specifies the stage 2 description of the SoLSA service, which gives the network operator the basis to offer subscribers or group of subscribers different services, different tariffs and different access rights depending on the geographical location of the subscriber, according to GSM 02.43. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. 2.1 Normative references [1] GSM 02.43: “Digital cellular telecommunications system (Phase 2+); Support of Localised Service Area (SoLSA), Stage 1”. [2] GSM 03.03: “ Digital cellular telecommunications system (Phase 2+); Numbering, Addressing and Identification”. [3] GSM 03.22: “Digital cellular telecommunications system (Phase 2+); Functions Related to Mobile Station (MS) in Idle Mode”. [4] GSM 04.08: “Digital cellular telecommunications system (Phase 2+); Mobile Radio Interface – Layer 3 Specification”. (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 6 3G TS 23.073 version 3.0.0 [5] GSM 04.60: “Digital cellular telecommunications system (Phase 2+); Mobile Station (MS) – Base Station System (BSS) interface; Radio Link Control/ Medium Access Control (RLC/MAC) protocol (GPRS)”. [6] GSM 05.02: “ Digital cellular telecommunications system (Phase 2+); Multiplexing and Multiple Access on the Radio Path”. [7] GSM 05.08: “Digital cellular telecommunications system (Phase 2+); Radio subsystem link control”. [8] GSM 08.08: “Digital cellular telecommunications system (Phase 2+);Mobile Switching Centre – Base Station System (MSC – BSS) interface Layer 3 specification”. [9] GSM 08.18: “Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Base Station System (BSS) – Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)”. [10] GSM 08.58: “Digital cellular telecommunications system (Phase 2+); BSC-BTS Interface – Layer 3 Specification”. [11] GSM 11.11: “Digital cellular telecommunications system (Phase 2+); Specification of the Subscriber Identity Module – Mobile Equipment (SIM-ME) Interface”. [12] GSM 11.14: “Digital cellular telecommunications system (Phase 2+); Specification of the SIM Application Toolkit for the Subscriber Identity Module –Mobile Equipment”. 2.2 Informative references [13] GSM 10.43: “Digital cellular telecommunications system; SoLSA, Work item status”. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following definitions apply: Allowed localised service area: A Localised Service Area where the subscriber has allowed service. Current localised service area: The Localised Service Area of the serving cell to which the mobile station has subscription. Escape PLMN: A specific PLMN code that may be broadcast for non SoLSA compatible mobile stations that do not understand the exclusive access indicator. Localised Service Area: A Localised Service Area consists of a cell or a number of cells. The cells constituting a LSA may not necessarily provide continuous coverage. Network operator: Entity that provides the network operating elements and resources for the execution of the LSA service. Service provider: Entity that offers the LSA services for subscription. The network operator may be the service provider. Service subscriber: Mobile subscriber, which subscribes to the LSA service. In principle, if a network provides LSA service, all users are able to subscribe to this service. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 7 3G TS 23.073 version 3.0.0 LSA Localised Service Area LSA ID Localised Service Area Identity CSE Camel Service Environment 4 Main concepts 4.1 Localised Service Area definition The network operator can define a Localised Service Area, LSA, consisting of a cell or a number of cells. It is possible for the network operator to set certain characteristics/attributes per LSA. Some LSA related attributes may be managed as part of cell management, e.g. exclusive access. The LSA is identified by a LSA ID. It shall be possible for the service subscriber to define a name on each of her allowed LSAs. 4.2 Subscriber information for Localised Service Area For a subscriber, the network operator or the service provider can define one or more LSA(s) as allowed LSA(s). It shall be possible to establish an order of priority between the allowed LSAs for a given subscriber and if the subscriber shall have preferential access within these LSAs. It shall also be possible to define whether access outside the allowed LSA(s) is allowed for a subscriber. Subscriber specific LSA information is stored and managed in the HLR. Application related LSA information is stored in appropriate service platform, e.g. in the CAMEL Service Environment (see annex A). In addition to subscriber details in the HLR server, it is also necessary for subscriber specific LSA information to be stored and managed in the SIM. Subscribers may receive SIM cards with the initial LSA data stored. The management of LSA data on SIM may be performed manually (in which case SIM has to be returned to the network operator or service provider for updating), or over the air interface as described in subclause 11.3. 4.3 Localised Service Area support in idle mode 4.3.1 Cell selection and reselection A cell reselection mechanism as defined in subclause 11.4.2 shall be used so that when camping on a cell in idle mode, the subscriber’s mobile station favours the cells belonging to her LSA(s). The mobile station shall always attempt to reselect a cell in a higher priority LSA. Cells outside the allowed LSA(s) shall have the lowest priority. 4.3.2 Localised service area indication The service subscriber can define a name (alphanumeric name, icon, etc) for each of her allowed LSAs. The MS will, in idle mode and if required by the user, indicate to the user the current LSA. The indication may be the name of the current LSA, as set by the user. The form of display and indication are left to manufacturer’s choice. 4.3.3 Exclusive access An exclusive access cell is a cell belonging to one or more LSAs and with allowed access only for users having this exclusive access cell included in his/her allowed LSAs. Other user’s mobile stations must be prevented from using the cell to obtain any service, other than TS12 (Emergency Calls). (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 8 3G TS 23.073 version 3.0.0 4.3.4 LSA only access It shall be BSS-controlled functionality to prevent terminated and/or originated calls outside the subscriber’s allowed LSA(s). Emergency calls are however always allowed. 4.4 Localised Service Area support in active mode 4.4.1 Localised service area indication As a network option, service subscribers may be notified at change of current LSA. This notification shall be performed as described in subclause 11.7. The form of display and indication are left to manufacturer’s choice. 4.4.2 Resource handling As a network operator option it shall be possible to allow or prohibit connection set-up and handover depending on the subscriber’s LSA information. Information to be made available to the radio resource allocation function and the handover function are as depicted in subclause 8.2.2. NOTE: For the handling of an established connection, it is out of scope of this document to describe how the network shall perform the resource allocation, handover, etc. depending on the subscriber’s LSA information. The following shall only be seen as examples. Assignment of traffic resources in preferential access LSA’s may (network option) be favoured for subscribers having this cell as part of their allowed LSAs. When the subscriber sets up a call in one of her LSAs, the cells belonging to that LSA can (network option) be favoured when handovers are carried out. Handovers to exclusive access cells can (network option) be prevented for users not having the cell as part of their allowed LSA. For a user with LSA only access, handovers as well as new originating and terminating calls may (network option) be allowed outside the allowed LSAs. Emergency calls are however always allowed 4.5 Localised Service Area support in access control 4.5.1 Emergency Call setup The Emergency Call setup shall always be accepted by the MSC. 4.5.2 Mobile Originating and Mobile Terminating Call setup The MSC receives the LSA ID(s) of the current cell from the BSC before the call setup. The current LSA can be selected on the basis of the allowed LSA(s) in the subscriber data. Depending on the current LSA, the network may continue as follows: • The MSC accepts the setup without Active mode support, if the active mode indicator flag for selected LSA is not set. • The MSC accepts the setup with Active mode support, if the active mode indicator flag for selected LSA is set. • The MSC starts charging activities for the current LSA (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 9 3G TS 23.073 version 3.0.0 4.5.3 Location Registration The MSC/VLR shall reject a location registration if the cell is used for exclusive access and none of the LSA Ids of current cell corresponds to the LSA ID(s) stored in the subscriber record. 4.5.4 Call unrelated services (Short message transfer, USSD, Supplementary Service management) The MSC receives the LSA ID(s) of the current cell from the BSC in the COMPLETE_L3_INFO. The current LSA can be selected on the basis of the allowed LSA(s) in the subscriber data and it can be used e.g. for the charging purposes. However, the service request is always accepted. Also, no active mode support is applied for the call unrelated services. 4.5.5 Routing Area Update SGSN shall reject a routing area update if the cell is used for exclusive access and none of the LSA Ids of current cell corresponds to the LSA ID(s) stored in the subscriber record. 5 General architecture No specific requirements are identified. The general architecture of GSM is maintained. Active mode support - Handover support (CS) - Network controlled cell reselection support (PS) MAP Subscriber’s LSA Data (relevant in the VPLMN) Create and download LSA information LSA Subscription Information BTS MS BCCH : - LSA cell reselection parameters - LSA id list (optional) - Cell id (optional) SIM ATK SIM data download (optional) LSA Subscription Information Subscriber’s LSA Data LSA data stored in SIM SGSN MSC VLR SSP HLR Idle mode support and indication LSA definition LSA ID – cell id mapping Set exclusive access cells Set cell reselection parameters MAP Subscriber’s LSA Data (relevant in the SGSN) LSA ID(s) of current cell BSC LSA ID(s) of current cell Service Mgmt Subscriber’s LSA Data Figure 1: General architecture 6 Compatibility issues LSA can not be used with standard phase 1 or phase 2 mobile stations (or with non-compatible phase 2+ mobile stations) with all service aspects. A dedicated mobile station with LSA capability is required. A compatible mobile station shall provide the following specific functions: 3.´ cell reselection in case of a LSA subscription; 3.´ notification of the current LSA. A mobile station with LSA capability shall also provide the complete functionality in order to allow the use of phase 2 services. (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 10 3G TS 23.073 version 3.0.0 Standard phase 1 and phase 2 mobile stations in a network shall not be impacted by the presence of LSA services in that network due to LSA signalling, also if the mobile station is operated with a SIM that contains SoLSA fields. However, if LSA is provided in a network, it can be applied to non-compatible mobile stations in the following way: 3.´ For a user with a LSA service subscription and with LSA only access, support is given for LSA only access, with exception of the notification (LSA indication). 3.´ For a user with a LSA service subscription, support is given for LSAs in active mode, with exception of the notification (LSA indication). 6.1 Handling of mobiles in exclusive access cells An escape PLMN may be included for old MSs that do not understand the exclusive access indicator. Such an MS will consider the cell as belonging to another PLMN. If the escape PLMN is broadcast and the subscriber is not allowed within the cell, the receiving MSC/VLR/SGSN shall reject the location update with the cause PLMN not allowed. The escape PLMN will be added to the list of forbidden PLMNs and not accessed again. SoLSA compatible mobile stations will however read the correct PLMN in the system information and treat the cell as normal. 7 Transmission No specific requirements are identified. 8 Information storage 8.1 Information managed per subscriber 8.1.1 Stored in the HLR The following mandatory information shall be stored in the HLR for each service subscriber: 3.´ a list of all the LSA Ids for the service subscriber; 3.´ the priority for each LSA; 3.´ the preferential access indicator for each LSA; 3.´ the LSA only access indicator. The following optional information may be stored in the HLR for each service subscriber: 3.´ LSA only access indication text (text to be displayed when out of LSA). The following optional information may also be stored for each subscribed LSA: 3.´ LSA name (A text string describing area and/or service. For example “ETSI BUILDING”); 3.´ LSA indication for idle mode (flag to activate/deactivate LSA indication in idle mode); 3.´ LSA indication for active mode (flag to activate/deactivate LSA indication in active mode); - - idle mode support (flag to activate/deactivate idle mode support in LSA); 3.´ active mode support (flag to activate/deactivate active mode support in LSA). The LSA Ids are defined in subclause 9.1.1. A service subscriber shall not be provided with more than 20 LSAs per PLMN (including universal LSA’s). (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 11 3G TS 23.073 version 3.0.0 8.1.2 Stored in the VLR The following mandatory information, which is relevant in the VPLMN, shall be stored in the VLR for each service subscriber: 3.´ a list of all the LSA Ids for the service subscriber; 3.´ the priority for each LSA; 3.´ the preferential access indicator for each LSA; 3.´ the LSA only access indicator. The following optional information may also be stored for each subscribed LSA: 3.´ LSA indication for active mode (flag to activate/deactivate LSA indication in active mode); active mode support (flag to activate/deactivate active mode support in LSA). This information shall be brought forward to the VLR at the same time as other subscriber information is copied form HLR. VLR entries shall be modified when corresponding HLR records are changed. 8.1.3 Stored in the SIM The following mandatory information shall be stored in the SIM for each service subscriber: 3.´ a list of all the LSA Ids for the service subscriber; 3.´ the priority for each LSA; 3.´ the LSA only access indicator. The following optional information may be stored in the SIM for each service subscriber: 3.´ LSA only access indication text (text to be displayed when out of LSA). The following optional information may also be stored for each subscribed LSA: 3.´ a list of all the cell identities for the subscribed LSA; 3.´ LSA name (A text string describing area and / or service. For example “ETSI BUILDING”); 3.´ LSA indication for idle mode (flag to activate/deactivate LSA indication in idle mode); - - idle mode support (flag to activate/deactivate idle mode support in LSA); The information shall be modified when corresponding HLR and BSS records are changed. 8.1.4 Stored in the SGSN The following mandatory information, which is relevant in the VPLMN, shall be stored in the SGSN for each service subscriber: 3.´ a list of all the LSA Ids for the service subscriber; 3.´ the priority for each LSA; 3.´ the preferential access indicator for each LSA; 3.´ the LSA only access indicator. The following optional information may also be stored for each subscribed LSA: 3.´ LSA indication for active mode (flag to activate/deactivate LSA indication in active mode); 3.´ active mode support (flag to activate/deactivate active mode support in LSA). (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 12 3G TS 23.073 version 3.0.0 This information shall be brought forward to the SGSN at the same time as other subscriber information is copied form HLR. SGSN entries shall be modified when corresponding HLR records are changed. 8.2 Information managed per LSA The LSA is defined as a list of cells inside the network. The cells shall be defined by their cell identification consisting of the Location Area Code and the Cell Identity as defined in GSM 08.08 and are therefore uniquely identified in the network. 8.2.1 Stored in the MSC The information stored in the MSC (network option) is the network specific service configuration of each LSA defined by the network operator and relevant for the MSC. The network specific configuration of each LSA may also include specific rules for e.g. the priority handling and the mapping between LSA information for the subscriber (VLR data) and the LSA information sent to BSS and when to notify MS about a service area change. NOTE: For the handling of call establishment, it is out of scope of this document to describe how the network shall perform e.g. mapping between LSA information for the subscriber (VLR data) and the LSA information sent to BSS. The network specific service configuration information shall only be seen as an example. 8.2.2 Stored in the BSS The information stored in the BSS is the network specific service configuration of each LSA defined by the network operator and relevant for the BSS. For each LSA relevant for the BSS in case of internal and external handover support, the LSA ID and the cells belonging to the LSA shall be stored. The BSS must also have knowledge about in which LSA cells that the exclusive access shall be indicated. The network specific configuration of each LSA may also include rules for e.g. handover and resource allocation. 9 Identities 9.1 Identities for LSA 9.1.1 LSA ID The LSA ID shall either be a PLMN significant number or a universal identity, indicated by one bit in the LSA ID. PLMN significant number: The LSA ID shall be a binary number uniquely assigned to an area in one network. The identity consists of 3 octets. Universal identity: The LSA ID shall be a globally unique identity assigned to a specific company or organization. A suitable Assigning and Registration Authority is required. 9.1.2 LSA name It shall be possible to assign a subscriber-defined identifier to each LSA. The LSA name can e.g. be an icon or an alphanumeric text up to 10 characters. (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 13 3G TS 23.073 version 3.0.0 10 Operation and maintenance aspects The operators have the possibility to: - Define LSAs consisting of a cell or a number of cells. - Set parameters for prioritised LSA cell reselection. - Set the parameter for exclusive access. 11 Function and information flows 11.1 LSA management The LSA attributes, as given in subclause 8.2 shall be entered and modified by the network operator or the service provider. 11.2 Subscription management When the subscriber record is created in the HLR, the list of allowed LSAs, priority of each LSA, the preferential access indicator of each LSA and information about access rights outside these LSAs shall be included. The network operator can change the LSA information for a subscription at any time. A change of subscription shall not affect any on-going calls at the moment of change. The update of SIM with user LSA information is done as depicted in subclause 11.3. 11.3 Update of LSA data in SIM SIM Application Toolkit (SAT) SIM Data Download procedure, as specified in GSM 11.14, can be used to download LSA data to SIM over the air interface. SAT class 1 supports SMS as the bearer for LSA data. When using over the air interface for updating LSA information on the SIM card the GSM 03.48 specifies Standardised SIM toolkit commands for Remote File Management: 3.´ GSM 03.48 contains a standard format for remote file handling based on the instruction set from GSM 11.11. Operators have possibility to use and update SIMs from different vendors. 3.´ The parameter(s) in the SIM Data Download Message is either a single command, or a list of commands, and each command is coded according to the generalised structure defined in GSM 03.48. 3.´ Data field to be used in commands will be specified in GSM 11.11 for SoLSA GSM Rec. 03.48 also specifies various security mechanisms (e.g. various derivatives of DES) that can used to protect the remote file management commands. New SIMs for SoLSA are needed to cater for SIM related security issues. Unauthorised modification of SoLSA data in SIM, either by users or by any other entity, is to be prohibited. . 11.4 Functions related to MS in idle mode for support of LSA 11.4.1 Broadcast information In cells belonging to a LSA, the LSA ID(s) and/or cell identity is broadcast. (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 14 3G TS 23.073 version 3.0.0 Further, in cells belonging to a LSA, which shall give exclusive access to a subscriber group, an exclusive access indication is broadcast. To be able to favour the LSA cells at cell reselection new LSA reselection parameters are broadcast. 11.4.2 Cell selection and reselection. The definition of a “suitable cell”, as defined in GSM 03.22, is modified with the following criterion: A SoLSA exclusive access cell is “suitable” only if the LSA of the cell is one of the allowed LSA according to the SIM. Emergency calls are always allowed if no cells are found suitable. An MS with SIM indicating LSA subscription shall always try to reselect the cell with the highest LSA priority according to the information stored on the SIM. The LSA reselection parameters broadcast on the BCCH shall be used to calculate the reselection criteria. The broadcasting mechanism is as described in GSM 04.08 and GSM 04.60. The MS shall follow the reselection procedures defined in GSM 05.08. NOTE: The text above covers also the case when the MS is using GPRS together with SoLSA. 11.4.3 Location Updating If the escape PLMN is broadcast the BSS shall, at location updating, inform the MSC/VLR about the LSA ID(s) of the cell where the location updating request message was received. This is done by adding the LSA ID(s) of current cell to the complete layer 3 information message for the exclusive access cell. 11.4.4 Routing Area Update If the escape PLMN is broadcast the BSS shall, at routing area update, inform the SGSN about the LSA ID(s) of the cell where the routing area update request message was received. This is done by adding the LSA ID(s) of current cell to the UL UNITDATA message for the exclusive access cell. 11.5 Transfer of information from HLR to VLR If the subscription contain LSA information then, when the subscriber registers on a VLR, the HLR shall send the LSA subscription data to that VLR, which is relevant in the VPLMN. This is done by adding the LSA information to the MAP_INSERT_SUBSCRIBER_DATA and for deletion in MAP_DELETE_SUBSCRIBER_DATA. When there is a change in the LSA information the HLR shall include at least the new and/or modified LSA data. When there is a change in the access right outside the LSA(s) the HLR shall include the LSA only access indicator. 11.6 Transfer of information from HLR to SGSN If the subscription contain LSA information then, when the subscriber registers on a SGSN, the HLR shall send the LSA subscription data to that SGSN, which is relevant in the VPLMN. This is done by adding the LSA information to the MAP_INSERT_SUBSCRIBER_DATA and for deletion in MAP_DELETE_SUBSCRIBER_DATA. When there is a change in the LSA information the HLR shall include at least the new and/or modified LSA data. When there is a change in the access right outside the LSA(s) the HLR shall include the LSA only access indicator. 11.7 Functions related to active mode support of LSA 11.7.1 MS connection establishment 11.7.1.1 Indication of current LSA to the MSC At initial connection establishment the BSS shall inform the MSC about the LSA ID(s) of the cell where the initial layer 3 message was received. This is done by adding the LSA ID(s) of current cell to the complete layer 3 message. (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 15 3G TS 23.073 version 3.0.0 11.7.1.2 Indication of allowed LSA to the BSS The MSC sends the LSA information message to the BSS including the A-interface LSA information of the connection as defined in GSM 08.08. The MSC maps the subscription LSA information on to the A-interface LSA information for LSAs requiring ‘active mode support’. The LSA information sent to the BSS indicates the allowed area for the MS connection. The BSS shall store the LSA information in order to use it on later actions, e.g. at handover. The LSA information for the MS connection shall be used in the BSS at assignment of radio resources in order to e.g. prioritise cells in the allowed LSA(s) and to prevent allocating resources in cells outside the allowed area for the MS connection. 11.7.1.3 Indication of allowed LSA to the BSS The SGSN may send the LSA information message to the BSS for a mobile station in ready mode as defined in GSM 08.18. The SGSN sends the subscription LSA information for LSAs requiring ‘active mode support’. The LSA information sent to the BSS indicates the allowed area for the MS connection. The BSS shall store the LSA information in order to use it on later actions, e.g. when determine specific cell selection parameters. The LSA information for the MS connection shall be used in the BSS to e.g. prioritise cells in the allowed LSA(s) and to prevent allocating resources in cells outside the allowed area for the MS connection. 11.7.2 Handover 11.7.2.1 Indication of allowed LSA to the target BSS In case of BSS external handover, the LSA information for the connection shall be included in the handover request message. 11.7.2.2 Indication of current LSA to the MSC In case of BSS external handover, the BSS informs the MSC about the LSA ID of current cell. This is done by adding the LSA ID of the current/new cell to the handover request acknowledge message. In case of BSS internal handover, the BSS informs the MSC when a change of LSA has occurred for a connection. This is done by adding the LSA ID of the current/new cell to the handover performed message or assignment complete message (if handover performed during assignment). 11.7.2.3 Indication of current LSA to the SGSN In case of cell change, the BSS may inform the SGSN about the LSA ID(s) of current cell. This is done by adding the LSA ID(s) of the current/new cell to the UL UNITDATA message. 11.8 LSA indication procedures Different indication procedures shall be applied in relation to the mode of the mobile station as presented in clause 4 and defined in the following sections. 11.8.1 Indication for mobile stations in idle mode In addition to indicate the registered PLMN, an MS with subscription for a LSA in the registered PLMN shall indicate this LSA when it is available. The indication towards the user is optional and may be done by displaying the stored LSA name that corresponds to the ID of the current LSA. An MS with LSA only access subscription may also give an indication towards the user, when the no subscribed LSAs are available to the user. The indication is optional and may be done by displaying the LSA only access text stored in the SIM. (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 16 3G TS 23.073 version 3.0.0 11.8.2 Indications for mobile stations in active mode The network decides when to send a notification to the MS about a change of current LSA. The information will be sent from the MSC to the MS and will contain the LSA ID. This is done by adding the LSA ID of the current cell to the MM Information message. If no LSA ID is included in the MM Information message the MS shall assume that the current cell does not belong to any of the allowed LSAs for the subscriber. The indication towards the user is optional and can be heard as e.g. a beep in the receiver or by displaying the stored LSA name that corresponds to the received LSA ID. 11.9 Overview of signalling In this overview, the messages required to implement the specified concept are identified and brief details are given of each message. These signalling flows are not normative, but provided as an illustration on possible signalling interworking (note that only those parts of the procedures that are relevant for the LSA service are included). MS MSC VLR LOCATION_ UPDATING_ REQUEST MAP_UPDATE_ LOCATION_ AREA HLR BSS MAP_INSERT_ SUBSCRIBER_ DATA MAP_UPDATE_ LOCATION_ AREA COMPLETE_ LAYER3_ INFORMATION Figure 2: Signalling information required at location registration LOCATION_UPDATING_REQUEST: Standard message. COMPLETE_LAYER3_INFORMATION: If the escape PLMN is broadcast, the MSC is provided with location updating information together with the LSA ID(s) of current cell. MAP_UPDATE_LOCATION_AREA: Standard message. MAP_INSERT_SUBSCRIBER_DATA: The VLR is provided with the subscriber information including the allowed LSA ID(s), priority of each LSA, the preferential access indicator for each LSA and the LSA only access indicator of current PLMN. (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 17 3G TS 23.073 version 3.0.0 MS SGSN UPLINK_ UNITDATA HLR BSS MAP_INSERT_ SUBSCRIBER_ DATA MAP_UPDATE_ LOCATION_ AREA ROUTING_ AREA_UPDATE Figure 3: Signalling information required at routing area update ROUTING_AREA_UPDATE_REQUEST: Standard message. UPLINK_UNITDATA: If the escape PLMN is broadcast, the SGSN is provided with routing area update information together with the LSA ID(s) of current cell. MAP_UPDATE_LOCATION_AREA: Standard message. MAP_INSERT_SUBSCRIBER_DATA: The SGSN is provided with the subscriber information including the allowed LSA ID(s), priority of each LSA and the LSA only access indicator of current PLMN. SM TL SMS-DELIVER SM TL SMS-DELIVER acknowledgement To SMSC From SMSC MAP-MT-FORWARD- SHORT-MESSAGE request MSC MS GMSC/ IWMSC LSA mgmt MT-SHORT- MESSAGE MAP-MT-FORWARD- SHORT-MESSAGE response Routing query to HLR Answer from HLR etc. Figure 4: Signalling information required at updating of the subscriber’s LSA information by using SMS (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 18 3G TS 23.073 version 3.0.0 MT-SHORT-MESSAGE, MAP-MT-FORWARD-SHORT-MESSAGE request, SM TP SMS-DELIVER: Standard messages containing subscriber’s LSA information and are parts of SIM data download. SM TP SMS-DELIVER acknowledgement, MAP-MT-FORWARD-SHORT-MESSAGE response: Standard messages containing result of the operation. RACH (CHAN_REQ) MS BSS MSC/VLR IMMEDIATE_ASSIGNMENT SABM (SERV_REQ) COMPLETE_LAYER3_ INFORMATION UA (SERV_REQ) CM_SERVICE _ACCEPTED SETUP ASSIGNMENT_REQUEST ASSIGNMENT_COMMAND SABM UA ASSIGNMENT_COMPLETE A-ASSIGNMENT_COMPLETE CALL_PROCEEDING SYSTEM_INFO LSA_INFORMATION Figure 5: Signalling information required for mobile originating call establishment SYSTEM_INFO: The network provides the cell identity and/or LSA ID(s) of the cell, LSA cell reselection parameters and the exclusive access indication. Initial RACH CHANNEL_REQUEST: Standard message. IMMEDIATE_ASSIGNMENT: Standard message. SABM (SERV_REQ): Standard message. UA (SERV_REQ): Standard message. COMPLETE_LAYER3_INFORMATION: The MSC is provided with initial information about the requested service together with the LSA ID(s) of current cell. CM_SERVICE_ACCEPT: Standard message. The service request is acknowledged. Acknowledgement of the service can also be performed by invocation of ciphering mode setting. SETUP: Standard message. CALL_PROCEEDING: Standard message. LSA INFO: New message including the allowed LSA ID(s), priority of each LSA, the preferential access indicator for each LSA and an indication about the access rights outside these LSA(s) for the service subscriber. This message needs to be sent before Assignment request. Additional messages may be sent anytime during the lifetime of a call. ASSIGNMENT_REQUEST: Standard message. ASSIGNMENT_COMMAND: Standard message. SABM: Standard message. UA: Standard message. ASSIGNMENT_COMPLETE: Standard message. (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 19 3G TS 23.073 version 3.0.0 A_ASSIGNMENT_COMPLETE: Modified assignment complete including the LSA ID of current cell. BSS-A MSC-A MSC-B HANDOVER REQUIRED MAP_PREPAR HANDOVER HANDOVER REQUEST BSS-B Figure 6: Signalling information required at BSS external handover initiation HANDOVER REQUIRED: Standard message. MAP_PREPARE_HANDOVER: Standard message. Including the modified handover request. HANDOVER_REQUEST: Modified handover request including the allowed LSA ID(s), priority of each LSA, the preferential access indicator of each LSA and an indication about the access rights outside these LSA(s). MSC-A MSC-B MAP_PROCESS_ ACCESS_SIGNAL. HANDOVER_ REQUEST_ ACKNOWLEDGE BSS-B Figure 7: Signalling information required at BSS external handover acknowledgement HANDOVER_REQUEST_ACKNOWLEDGE: Modified handover request acknowledge including the LSA ID of current cell. MAP_PROCESS_ACCESS_SIGNALLING request: Standard message. Including the modified handover request acknowledge. (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 20 3G TS 23.073 version 3.0.0 MS BSS-B MSC-B HANDOVER PERFORMED MAP_PROCESS ACCESS_SIGNAL HANDOVER COMPLETE MSC-A Figure 8: Signalling information required at BSS internal handover HANDOVER_COMPLETE: Standard message. HANDOVER _PERFORMED: Modified handover performed including the LSA ID of current cell. MAP_PROCESS_ACCESS_SIGNALLING request: Standard message. Including the modified handover performed. BSS MS MSC MM_INFORMATION Figure 9: Signalling information required at notification of LSA change in active mode MM_INFORMATION: Modified MM-INFORMATION message including the LSA ID of current cell. 12 Charging 12.1 General principles Using LSA as a location based charging can be realised. Different charging can be applied with respect to different LSAs, which shall also include the possibility to change charging when moving between LSAs with different tariffs associated. LSAs with higher priority may be associated with different tariffs. Appropriate information concerning the change of charging due to the LSA change shall also be included in the charging record (toll ticket). (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 21 3G TS 23.073 version 3.0.0 Annex A (informative): SoLSA interworking with CAMEL This Annex is informative. Regarding the SoLSA network architecture SMG12 has decided that: • the HLR solution is chosen for SoLSA • CAMEL phase 3 will be improved in the 99 release so that it fully utilises the SoLSA benefits. This annex collects the optional functional enhancements for CAMEL required to enable CAMEL interworking with SoLSA. These enhancements are expected to be included in CAMEL phase3 in Release 99. A.1 Subscriber information for Localised Service Area Subscriber specific information LSA information is stored and managed in the HLR. Application related LSA information is stored in appropriate service platform, e.g. in the CAMEL Service Environment. A.2 Network Architecture MAP Subscribers LSA Data (relevant in the VPLMN) Create and download LSA information BTS MS BCCH : - LSA cell reselection parameters - LSA id list (optional) - Cell id (optional) SIM ATK SIM data download (optional) LSA Subscription Information Subscribers LSA Data LSA data stored in SIM SGSN MSC VLR SSP HLR Active mode support Idle mode support and indication LSA definition LSA ID – cell id mapping Set exclusive access cells Set cell reselection parameters MAP Subscribers LSA Data (relevant in the SGSN) LSA ID(s) of current cell BSC LSA ID(s) of current cell Service Mgmt CSE LSA Subscription Information CAMEL based applications that use SoLSA CAP Subscribers LSA Data Figure A1: NW architecture including SoLSA related enhancements on CAMEL Service Environment (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 22 3G TS 23.073 version 3.0.0 A.3 Signalling Interworking RACH MS BSS MSC/VLR IIMM_ASS SABM (SERV_REQ) COM_L3_INFO UA (SERV_REQ) CM_SERV_ACC SETUP ASS_REQ ASS_CMD SABM UA Air_ASS_COM A-ASS_COM CALL PROCEEDING SYSTEM_INFO INITIAL DP CONTINUE/ CONNECT gsmSCF LSA_INFO Figure A2: Signalling interworking at Mobile Originating Call Establishment with applications on CAMEL Service Environment SYSTEM_INFO: The network provides the cell identity and/or LSA ID(s) of the cell, LSA cell reselection parameters and the exclusive access indication. Initial RACH CHAN_REQ: Standard message. IMM_ASS: Standard message. SABM (SERV_REQ): Standard message. UA (SERV_REQ): Standard message. COM_L3_INFO: The MSC is provided with initial information about the requested service together with the LSA ID(s) of current cell. CM_SERV_ACC: Standard message. The service request is acknowledged. Acknowledgement of the service can also be performed by invocation of ciphering mode setting. SETUP: Standard message. INITIALDP: Modified CAP message indicating that the CAMEL TDP has been met. Additionally the LSA ID(s) of the current cell are sent to the gsmSCF. CONTINUE: Modified CAP message indicating that the call continues without modifications. (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 23 3G TS 23.073 version 3.0.0 CONNECT: Modified CAP message indicating that the gsmSCF has modified e.g. the destination number. CALL_PROCEEDING: Standard message. LSA INFO: New message including the LSA ID(s), priority of each LSA, the preferential access indicator of each LSA and an indication about the access rights outside these LSA(s) for the service subscriber. This message need to be sent before Assignment Request message. Additional messages may be sent at anytime during the lifetime of a call. ASS_REQ: Standard message. ASS_CMD: Standard message. SABM: Standard message. UA: Standard message. Air_ASS_COM: Standard message. A_ASS_COM: Modified assignment complete including the LSA ID of current cell. (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 3GPP 3G TS 23.073 V3.0.0 (1999-08) 24 3G TS 23.073 version 3.0.0 Annex B (informative): Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 03.73 7.1.0 Transferred to 3GPP CN CN#04 23.073 3.0.0 (3G TS 23.073 version 3.0.0 Release 1999) ETSI TS 123 073 V3.0.0 (2000-01) ETSI TS 123 073 V3.0.0 (2000-01) ETSI 25 ETSI ETSI TS 123 073 V3.0.0 (2000-01) (3G TS 23.073 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
0.1 References
|
.......................................................................................................................................................... 5
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
0.2 Abbreviations
|
..................................................................................................................................................... 5
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1 Closed User Group (CUG)
|
......................................................................................................................5
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.1 Definition
|
........................................................................................................................................................... 5
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.2 Description
|
......................................................................................................................................................... 6
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.2.1 Service description
|
....................................................................................................................................... 6
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.2.2 Applicability to telecommunication services
|
............................................................................................... 6
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.2.3 Definitions
|
.................................................................................................................................................... 6
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3 Normal procedures with successful outcome
|
..................................................................................................... 6
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3.1 Provision
|
...................................................................................................................................................... 6
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3.2 Withdrawal
|
................................................................................................................................................... 7
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3.5 Activation
|
..................................................................................................................................................... 7
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3.6 Deactivation
|
................................................................................................................................................. 7
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3.7 Invocation
|
..................................................................................................................................................... 7
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3.8 Normal operation with successful outcome
|
................................................................................................. 7
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3.8.1 Mobile originating calls
|
.......................................................................................................................... 8
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3.8.1.1 A user with no preferential CUG and no OA capability
|
................................................................... 8
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3.8.1.2 A user with a preferential CUG but no OA capability
|
...................................................................... 8
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3.8.1.3 A user with the OA capability but no preferential CUG
|
................................................................... 8
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3.8.1.4 A user with a preferential CUG and the OA capability
|
.................................................................... 8
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3.8.1.5 A user not subscribing to the CUG Supplementary Service
|
............................................................. 9
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3.8.2 Mobile terminating calls
|
......................................................................................................................... 9
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3.8.2.1 CUG call with no OA indication
|
....................................................................................................... 9
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3.8.2.2 CUG call with OA indication
|
............................................................................................................ 9
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.3.8.2.3 Normal call
|
....................................................................................................................................... 9
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.4 Exceptional procedures or unsuccessful outcome
|
.............................................................................................. 9
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.4.1 Exceptional operation or unsuccessful outcome
|
.......................................................................................... 9
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.4.10 Roaming into networks not supporting CUG
|
............................................................................................. 10
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.5 Alternate procedures
|
........................................................................................................................................ 10
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.6 Interactions with other Supplementary Services
|
.............................................................................................. 10
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.6.82.1 Call forwarding unconditional
|
.............................................................................................................. 10
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.6.82.2 Call forwarding on mobile subscriber busy
|
.......................................................................................... 11
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.6.82.3 Call forwarding on no reply
|
.................................................................................................................. 11
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.6.82.4 Call forwarding on mobile subscriber not reachable
|
............................................................................ 11
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.6.83.1 Call waiting
|
.......................................................................................................................................... 11
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.6.84.1 Multi-party service
|
............................................................................................................................... 11
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.6.88 Call restriction Supplementary Services
|
.................................................................................................... 11
|
dec4c8c5cf1e3925fd0827d92a8d928b
|
122 085
|
1.7 Interworking considerations
|
............................................................................................................................. 11 Annex 1 (normative): General subscription options (Per Subscriber)......................................................13 Annex 2 (normative): Originating PLMN actions on call requests on the calling user's side.................14 Annex 3 (normative): Terminating PLMN actions.....................................................................................15 Annex 4 (normative): CUG interaction with the call forwarding Supplementary Services ...................16 Annex 5 (informative): Change history........................................................................................................17 History..............................................................................................................................................................18 (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 4 3G TS 22.085 version 3.1.0 Foreword This Technical Specification has been produced by the 3GPP. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 5 3G TS 22.085 version 3.1.0 0 Scope The present document describes the Supplementary Services belonging to the group Community Of Interest Supplementary Services. The general aspects, including definitions and recommended provision, of the description of the Supplementary Services are given in TS 22.004. The group of Community Of Interest Supplementary Services includes one Supplementary Service: - Closed user group (clause 1). 0.1 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • 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 23.003: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification". [4] ITU-T Recommendation X.121: "International numbering plan for public data networks". [5] ITU-T Recommendation X.180: "Administrative arrangements for closed user groups (CUGs)". [6] TS 21.905: "Vocabulary for 3GPP Specifications". 0.2 Abbreviations Abbreviations used in the present document are listed in GSM 01.04 and TS 21.905. 1 Closed User Group (CUG) 1.1 Definition The Closed User Group (CUG) Supplementary Service enables subscribers, connected to a PLMN and possibly also other networks, to form closed user groups (CUGs) to and from which access is restricted. A specific user may be a member of one or more CUGs. Members of a specific CUG can communicate among each other but not, in general, with users outside the group. The ability to set up emergency calls remains unaffected. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 6 3G TS 22.085 version 3.1.0 1.2 Description 1.2.1 Service description An ISDN/MSISDN number shall identify each member of a CUG. A CUG shall be defined for one or more basic service groups. CUG members can have additional capabilities that allow them to originate calls outside the group, and/or to receive calls from outside the group. CUG members can have additional restrictions that prevent them from originating calls to other members of the CUG, or from receiving calls from other members of the CUG. CUG shall remain unaffected when members roam to PLMNs supporting CUG. Roaming subscribers must have the same CUG facilities on the roamed-to PLMN as on the Home PLMN. When roaming to networks not supporting CUG, the CUG restrictions must be enforced. (However, where possible, the CUG facilities should be supported, see subclause 1.4.10.) Each individual subscriber may be a member of a maximum of 10 CUGs. 1.2.2 Applicability to telecommunication services The applicability of this Supplementary Service is defined in GSM 22.004 [2]. 1.2.3 Definitions MSISDN: A number conforming to the numbering plan and structure specified in TS 23.003. CUG member: A user who has subscribed to the CUG Supplementary Service and is one of the users in the group formed by a particular CUG. CUG index: A value assigned by the network to identify a CUG. CUG Interlock Code (IC): Is used by the network (not by the MS) to identify CUG membership. preferential CUG: A preferential CUG, which can be specified for each basic service group, is the nominated default CUG to be used when no explicit CUG index is received by the network. suppress preferential CUG: A user action to prohibit the use of the preferential CUG, on a per call basis. Incoming Access (IA): An arrangement which allows a member of a CUG to receive calls from outside the CUG. Outgoing Access (OA): An arrangement which allows a member of a CUG to place calls outside the CUG. suppress OA: A user action to prohibit the use of the OA subscription option, on a per call basis. Incoming Calls Barred Within A CUG (ICB): An access restriction that prevents a CUG member from receiving calls from other members of that group. Outgoing Calls Barred Within A CUG (OCB): An access restriction that prevents a CUG member from placing calls to other members of that group. CUG calls: A CUG call is a call which is restricted to a pre-defined group of users. 1.3 Normal procedures with successful outcome 1.3.1 Provision The CUG Supplementary Service shall be provided after prior arrangement with the service provider. At provision subscription options should be selected by the served mobile subscriber. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 7 3G TS 22.085 version 3.1.0 A user may be a member of several CUGs. The service provider defines the number of CUGs, up to the maximum stated in subclause 1.2.1, which can be allocated to an individual subscriber. The user shall choose one of the following subscription options for each basic service group applied to the CUG Supplementary Service. This subscription option may be provisioned on a per basic service group basis or for all basic services: - CUG calls only; - CUG with incoming access, i.e. can also receive calls, which are not subject to CUG restrictions; - CUG with outgoing access, i.e. can also make calls, which are not subject to CUG restrictions; - CUG with incoming and outgoing access, i.e. can also make and receive calls, which are not subject to CUG restrictions. A user may subscribe to one of two additional restrictions applying for each particular CUG: - incoming calls barred within a CUG; - outgoing calls barred within a CUG. The network shall provide a subscription option in order to enable the user to specify a preferential CUG, for each basic service group included in at least one of the CUG(s). The user can request that no preferential CUG exists, or that a particular one of her CUGs (or the only one if a single CUG applies) is used as a preferential CUG for the particular basic service group. If a user has the subscription option outgoing calls barred within a CUG, it is not allowed to specify that particular CUG as a preferential CUG. The subscription options are shown in Annex 1. The CUG indices shall be allocated by prior arrangement with the service provider. The choice of preferential CUG(s) shall be alterable only by service provider action upon request by the served user. 1.3.2 Withdrawal Withdrawal of the CUG Supplementary Service, membership of one or more CUGs, will be by the action of the service provider, at the request of the subscriber or CUG management, or for administrative reasons. 1.3.5 Activation The CUG Supplementary Service will be activated by the service provider as a result of provision. 1.3.6 Deactivation The CUG Supplementary Service will be deactivated by the service provider as a result of withdrawal. 1.3.7 Invocation Normal call setup procedures shall apply to calls with the CUG Supplementary Service. 1.3.8 Normal operation with successful outcome A user having neither the restriction of incoming calls barred within a CUG, nor the restriction of outgoing calls barred within a CUG can make calls to, and receive calls from, members of those CUGs of which the user is a member. Upon receipt of a call setup attempt to or from a CUG subscriber the network shall check its validity in conjunction with the access capabilities subscribed to. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 8 3G TS 22.085 version 3.1.0 On successful validation of a CUG call setup attempt the network shall attempt to establish the call to the required destination. 1.3.8.1 Mobile originating calls When originating a call, the calling user may specify a CUG index to indicate that service to a particular CUG is required. If no CUG index is given then the preferential CUG (if specified) is used by the network. The Outgoing Access (OA) capability allows CUG subscribers to make outgoing calls, which are not subject to CUG restrictions. If a user, subscribing to the CUG Supplementary Service, originates a call and enters a request for suppression of both a preferential CUG and of the OA capability but does not enter a CUG index, the call shall be rejected. If a user, subscribing to the CUG Supplementary Service and having the OA capability, originates a call and enters a CUG index (without suppressing the OA capability), while having the restriction of outgoing calls barred within that CUG, the call shall be established without any CUG information i.e. as a normal call. The originating PLMN actions are illustrated in annex 2. As a network option, the network may signal towards the calling user the CUG index in use for the current call, if this can be determined by the network. 1.3.8.1.1 A user with no preferential CUG and no OA capability If a user, subscribing to the CUG Supplementary Service, who has no preferential CUG and no OA capability, originates a call and enters a CUG index (and possibly requests suppression of a preferential CUG and/or the OA capability) the call shall be established using the CUG index provided. If no CUG index is entered the call shall be rejected. 1.3.8.1.2 A user with a preferential CUG but no OA capability If a user, subscribing to the CUG Supplementary Service, who has a preferential CUG but no OA capability, originates a call and enters no CUG information (or if she only requests suppression of the OA capability),the call shall be established using the preferential CUG. If she enters a CUG index (and possibly a request for suppression of the preferential CUG and/or the OA capability), the call shall be established using the CUG index provided. If she enters only a request for suppression of the preferential CUG, i.e. no CUG index, the call shall be rejected. 1.3.8.1.3 A user with the OA capability but no preferential CUG If a user, subscribing to the CUG Supplementary Service, who has the OA capability but no preferential CUG, originates a call and enters no CUG information (or if she only requests suppression of a preferential CUG), the call shall be established without any CUG information being sent, i.e. this is set up as a normal call. If she enters a CUG index (and possibly a request for suppression of a preferential CUG), the call shall be established using the CUG index provided and with an indication of OA allowed. If she enters both a CUG index and a request for suppression of the OA capability (and possibly a request for suppression of a preferential CUG), the call shall be established using the CUG index provided. If she enters only a request for suppression of the OA capability, i.e. no CUG index, the call shall be rejected. 1.3.8.1.4 A user with a preferential CUG and the OA capability If a user, subscribing to the CUG Supplementary Service, who has a preferential CUG and the OA capability, originates a call without any CUG information, the call shall be established using the preferential CUG and with an indication of OA allowed. If she enters a CUG index (and possibly a request for suppression of the preferential CUG), the call shall be established using the CUG index provided and with an indication of OA allowed. If she enters only a request for suppression of the OA capability, the call shall be established using the preferential CUG. If she enters only a request for suppression of the preferential CUG, i.e. no CUG index, the call shall be established without any CUG information i.e. this is set up as a normal call. If she enters both a CUG index and a request for suppression of the OA capability (and possibly a request for suppression of the preferential CUG), the call shall be established using the CUG index provided. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 9 3G TS 22.085 version 3.1.0 1.3.8.1.5 A user not subscribing to the CUG Supplementary Service If a user, not subscribing to the CUG Supplementary Service, originates a call and enters CUG information the call shall be set up as a normal call. 1.3.8.2 Mobile terminating calls If a user, with or without the IA capability, receives a CUG call and the calling user is a member of the same CUG, the incoming CUG call shall be indicated as such, towards the called Mobile Station, with the appropriate CUG index. If a user with the IA capability receives a call from a user who has not subscribed to the CUG Supplementary service, or from a user who is a member from another CUG and who is using the OA capability, the call is offered to the user as a normal incoming call. The terminating PLMN actions are illustrated in annex 3. 1.3.8.2.1 CUG call with no OA indication For a call where an interlock code is received, but not an indication of OA allowed, the following applies: If there is a match with any of the called user's CUGs, and if she does not have incoming calls barred within this CUG, the call shall be offered as a CUG call. In all other cases the call shall be rejected. 1.3.8.2.2 CUG call with OA indication For a call where both an interlock code and an indication of OA allowed is received, the following applies: If there is a match with any of the called user's CUGs, and if she does not have incoming calls barred within this CUG, the call shall be offered as a CUG call. If the above condition does not apply, and if she has incoming access allowed, the call shall be offered as a normal call. If the called subscriber does not subscribe to the CUG Supplementary Service, the call shall be offered as a normal call. In all other cases, the call shall be rejected. 1.3.8.2.3 Normal call When a normal call is received, i.e. a call without any CUG information, the following shall apply: If the called subscriber subscribes to the CUG Supplementary Service and has incoming access allowed, or if she is a normal non-CUG subscriber, the call shall be offered as a normal call. In all other cases, the call shall be rejected. 1.4 Exceptional procedures or unsuccessful outcome 1.4.1 Exceptional operation or unsuccessful outcome Upon receipt of a call setup attempt to or from a CUG subscriber, the network shall check its validity in conjunction with the access capabilities subscribed to. If an invalid request is received or the checks cannot be performed, then the network shall reject the call and return an appropriate indication to the calling user. The network shall prohibit a user with incoming calls barred within a CUG from receiving CUG calls from members of the same CUG. The network shall prohibit a user with outgoing calls barred within a CUG from making CUG calls within that CUG. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 10 3G TS 22.085 version 3.1.0 1.4.10 Roaming into networks not supporting CUG The HPLMN shall control handling of roaming, when a CUG subscriber is roaming into a network not supporting CUG, without relying on extra functionality in network entities not supporting CUG. For subscribers roaming in a PLMN not supporting CUG the following apply: 1) In the case of basic service groups not subject to CUG restrictions, incoming and outgoing calls shall be allowed as normal. 2) In the case of basic service groups subject to CUG restrictions and without incoming access, incoming calls shall not be allowed. 3) In the case of basic service groups subject to CUG restrictions and without outgoing access, outgoing calls shall not be allowed. 4) Normal incoming calls are allowed for basic service groups subject to CUG restrictions and for which the called user has incoming access allowed. 5) Outgoing calls are allowed for basic service groups subject to CUG restrictions and for which the user has outgoing access allowed. 1.5 Alternate procedures None identified 1.6 Interactions with other Supplementary Services 1.6.82.1 Call forwarding unconditional CUG restrictions shall be met between the calling user and the forwarding user. In addition, the call must not be forwarded if the CUG restrictions of the forwarding mobile subscriber forbid her to make a call attempt of the same type to the forwarded-to user. The parameters of the CUG requested by the calling user shall be used for the forwarding call, and by this means CUG restrictions shall be met between the calling user and the forwarded-to user, except for the cases stated in section b) below. Annex 4 shows under what circumstances a call shall be allowed to be forwarded. a) CUG call with no OA indication. For calls received with an IC, but no indication of OA allowed, the following is valid: If the forwarding subscriber subscribes to the CUG Supplementary Service, and if she does not have outgoing calls barred within the CUG, the call shall be forwarded with the same IC as received from the A-party. In all other cases, the call shall be rejected. b) CUG call with an indication of OA allowed. For calls received with an IC and an indication of OA allowed, the following is valid: If the forwarding subscriber subscribes to the CUG Supplementary Service, and if there is a match with any of her CUGs, and if she does not have OA allowed, and if she does not have outgoing calls barred within the CUG, then the call shall be forwarded with the same IC as received from the A-party (the indication of OA allowed shall in this case NOT be forwarded). If the forwarding subscriber subscribes to the CUG Supplementary Service, and if there is a match with any of her CUGs, and if she does have OA allowed, and if she does not have outgoing calls barred within the CUG, then the call shall be forwarded with the same IC as received from the A-party and with the indication of OA allowed. If this forwarding subscriber has outgoing calls barred within the CUG, then the call shall be forwarded as a normal call (the CUG information shall in this case NOT be forwarded). (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 11 3G TS 22.085 version 3.1.0 If the forwarding subscriber subscribes to the CUG Supplementary Service, and if there is no match with any of her CUGs, but if she has IA allowed and OA allowed, then the call shall be forwarded with the same IC as received from the A-party and with the indication of OA allowed (in this case the subscription option "Intra-CUG restrictions" is not relevant). If the forwarding subscriber does not subscribe to the CUG Supplementary Service, then the call shall be forwarded with the same IC as received from the A-party and with the indication of OA allowed. In all other cases, the call shall be rejected. c) Normal call. For normal calls received the following is valid: If the forwarding subscriber subscribes to the CUG Supplementary Service, and if she does have OA allowed, then the call shall be forwarded without any CUG data. (In this case the subscription option "Intra-CUG restrictions" is not relevant.) If the forwarding subscriber does not subscribe to the CUG Supplementary Service, then the call shall be forwarded (without any CUG data). In all other cases, the call shall be rejected. 1.6.82.2 Call forwarding on mobile subscriber busy Same as the interaction with call forwarding unconditional. 1.6.82.3 Call forwarding on no reply Same as the interaction with call forwarding unconditional. 1.6.82.4 Call forwarding on mobile subscriber not reachable Same as the interaction with call forwarding unconditional. 1.6.83.1 Call waiting No interaction. If the incoming (waiting) call is a CUG call it shall be indicated as such. 1.6.84.1 Multi-party service No interaction. Multi-party calls shall be set up taking into account the CUG relationships between the controlling party and each of the remote parties. The CUG restrictions need not to be checked between remote parties. 1.6.88 Call restriction Supplementary Services The call restriction Supplementary Services, when active and operative, takes precedence over the CUG restrictions. The activation of a call restriction Supplementary Service does not affect any current CUG call. If, due to an interworking situation, signalling in the network is not able to carry the information required to provide the service, the network shall terminate the attempt and return an appropriate indication to the calling user. However, a CUG call with an OA indication shall in this case continue to be established as a normal call. The rejection of CUG calls cannot be technically guarantied in all network interconnection cases, and can only be ensured by inter-connect agreement. Management of CUG spanning over multiple networks: (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 12 3G TS 22.085 version 3.1.0 A CUG may span over several networks. In this case the responsibility for the management of this CUG is in one of these networks. NOTE: One mechanism exists for CUGs spanning over data networks only, having X.121 as the numbering plan (see ITU-T Recommendation X.180 (1988)), "Administrative arrangements for international closed user groups". (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 13 3G TS 22.085 version 3.1.0 Annex 1 (normative): General subscription options (Per Subscriber) Subscription Option Values Available Subscription to CUGs List of one or more CUG indices to the maximum stated in subclause 1.2.1. Intra CUG restrictions (for each CUG) - None designated - Incoming calls barred within a CUG - Outgoing calls barred within a CUG Applicability to Basic Services (for each CUG) - List of one or more Basic Service groups - All Basic Services Per basic service group subscription options Subscription Option Values Available Preferential CUG - None designated (NOTE) - CUG index Type of inter CUG accessibility - None designated - Outgoing access - Incoming access - Outgoing and Incoming access (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 14 3G TS 22.085 version 3.1.0 Annex 2 (normative): Originating PLMN actions on call requests on the calling user's side Information from the calling user Calling user's subscription - - - No CUG info CUG index or CUG index and suppress pref. CUG Suppress OA Suppress pref. CUG CUG index and suppress OA or CUG index and suppress OA and suppress pref CUG User without preferential CUG and without OA Reject call Establish call using CUG index provided Reject call Reject call Establish call using CUG index provided User with preferential CUG but without OA Establish call using pref CUG Establish call using CUG index provided Establish call using pref CUG Reject call Establish call using CUG index provided User without preferential CUG but with OA Establish call without any CUG info i.e. a normal call Establish call using CUG index provided and OA indicator Reject call Establish call without any CUG info i.e. a normal call Establish call using CUG index provided User with preferential CUG and with OA Establish call using pref CUG and OA indicator Establish call using CUG index provided and OA indicator Establish call using pref CUG Establish call without any CUG info i.e. a normal call Establish call using CUG index provided User without the CUG SS Normal call Normal call Normal call Normal call Normal call NOTE 1: If a CUG user enters a non-allocated CUG index the call shall be rejected. NOTE 2: If a user, subscribing to the CUG Supplementary Service and having the OA capability, originates a call and enters a CUG index (without suppressing the OA capability), while having the restriction of outgoing calls barred within that CUG, the call shall be established without any CUG information i.e. as a normal call. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 15 3G TS 22.085 version 3.1.0 Annex 3 (normative): Terminating PLMN actions This table shows the type of call request sent to the destination user or that a rejection indication is returned to the calling user, as a result of the CUG checks on the destination network side. Network actions on call requests on the called user's side Type of CUG indication M or CUG attributes of the forwarding user for requested basic service group forwarding user is a non from the NM IA not allowed IA allowed CUG user network not icb icb not icb icb CUG call with no OA M CUG call rejected CUG call rejected rejected indication NM rejected rejected CUG call with OA indication M CUG call rejected CUG call normal call normal call NM rejected normal call Normal call -- rejected normal call normal call M: match with any of the called subscriber's CUGs for the requested basic service group. NM: no match with any of the called subscriber's CUGs for the requested basic service group. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 16 3G TS 22.085 version 3.1.0 Annex 4 (normative): CUG interaction with the call forwarding Supplementary Services This table shows under what circumstances a call shall be allowed to be forwarded. Type of CUG indication M or CUG attributes of the forwarding user for requested basic service group forwarding user is a non from the NM OA not allowed OA allowed CUG user network 1) not ocb ocb not ocb ocb CUG call with no OA M CF rejected CF rejected rejected indication NM rejected rejected CUG call with OA indication M CFm 2) rejected CF CFn CF NM rejected CF 3) Normal call -- rejected CF 3) CF Abbreviations: CF: Forward call using the calling subscriber's parameters CFm: Forward call using modified calling subscriber's parameters CFn: The call is forwarded as a normal call. NOTE 1: M: match with any of the called subscriber's CUGs for the requested basic service group. NM: no match with any of the called subscriber's CUGs for the requested basic service group. NOTE 2: Only the interlock code is sent from the forwarding subscriber towards the forwarded to subscriber. NOTE 3: The subscription option outgoing calls barred within a CUG (ocb), is not relevant in this case. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 3GPP 3G TS 22.085 V3.1.0 (1999-12) 17 3G TS 22.085 version 3.1.0 Annex 5 (informative): Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.85 7.0.0 Transferred to 3GPP SA1 SA#04 22.085 3.0.0 SA#05 22.085 3.0.0 001 R99 3.0.1 Editorial update of references for GSM/3GPP use. SA#06 22.085 3.0.1 001 R99 3.1.0 Editorial update for GSM/3GPP use. (3G TS 22.085 version 3.1.0 Release 1999) ETSI TS 122 085 V3.1.0 (2000-01) ETSI 18 ETSI ETSI TS 122 085 V3.1.0 (2000-01) (3G TS 22.085 version 3.1.0 Release 1999) History Document history V3.1.0 January 2000 Publication
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
0.1 References
|
.......................................................................................................................................................... 5
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
0.2 Abbreviations
|
..................................................................................................................................................... 5
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1 MultiParty Service (MPTY)
|
....................................................................................................................5
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.1 Definition
|
........................................................................................................................................................... 5
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.