hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
da376d16eb2a7cd4aa93ea8ebb3b2ae8 | 101 580-2 | 4.4.2.3 Gate Related Procedures for PCRF Role | TP_PCRF_GRP_01 Standards Reference: 4.4.3 ¶ 6 PICS item: Test purpose: Ensure that the IUT in the Open state having received an AA-Request and having sent an AA-Answer, to indicate a resource allocation failure during the modification of PCC/QoS rules, sends an RA-Request containing a Specific-Action AVP indicating INDICATION_OF_FAILD_RESOURCES_ALLOCATION. Comments: It may be impossible to trigger the condition for sending of the RA-Request. ETSI ETSI TS 101 580-2 V1.1.1 (2012-04) 13 |
da376d16eb2a7cd4aa93ea8ebb3b2ae8 | 101 580-2 | 4.4.2.4 Session Termination for PCRF Role | TP_PCRF_ST_01 Standards Reference: 4.4.4 ¶ 2 PICS item: Test purpose: Ensure that the IUT in the Open state having established an AF session, on receipt of an ST-Request, sends an ST-Answer. Comments: TP_PCRF_ST_02 Standards Reference: 4.4.4 ¶ 4 PICS item: A.4/4 Test purpose: Ensure that the IUT in the Open state having established an AF session for sponsored connectivity, on receipt of an ST-Request, sends an ST-Answer containing a Sponsored-Connectivity-Data AVP containing an Used-Service-Unit AVP. Comments: |
da376d16eb2a7cd4aa93ea8ebb3b2ae8 | 101 580-2 | 4.4.2.5 Subscription to Notification of Signaling Path Status for PCRF Role | TP_PCRF_SN_01 Standards Reference: 4.4.5 ¶ 3 PICS item: Test purpose: Ensure that the IUT in the Open state, on receipt of an AA-Request subscribing to notifications of the status of the AF containing a Framed-IP-Address AVP containing a Specific-Action AVP indicating INDICATION_OF_RELEASE_OF_BEARER containing a Specific-Action AVP indicating INDICATION_OF_LOSS_OF_BEARER containing a Media-Component-Description AVP containing a Media-Sub-Component AVP containing a Flow-Usage AVP indicating AF_SIGNALLING containing a Flow-Number AVP indicating ‘0’ containing a Media-Component-Number AVP indicating ‘0’, sends a AA-Answer. Comments: In the case of IPv6 the Framed-IP-Address AVP is replaced by the Framed-IPv6-Prefix AVP. TP_PCRF_SN_02 Standards Reference: 4.4.5 ¶ 3 PICS item: Test purpose: Ensure that the IUT in the Open state, on receipt of an AA-Request subscribing to notifications of the status of the AF without the provision of AF signalling flow information, containing a Framed-IP-Address AVP indicating the full IP address of the UE containing a Specific-Action AVP indicating INDICATION_OF_RELEASE_OF_BEARER containing a Specific-Action AVP indicating INDICATION_OF_LOSS_OF_BEARER containing a Media-Component-Description AVP containing a Media-Sub-Component AVP containing a Flow-Number AVP indicating ‘0’ containing a Media-Component-Number AVP indicating ‘0’, sends an AA-Answer. Comments: In the case of IPv6 the Framed-IP-Address AVP is replaced by the Framed-IPv6-Prefix AVP. ETSI ETSI TS 101 580-2 V1.1.1 (2012-04) 14 TP_PCRF_SN_03 Standards Reference: 4.4.5 ¶ 5 PICS item: Test purpose: Ensure that the IUT in the Open state having established an Rx diameter session with subscription to notifications of the status of the AF signalling transmission path without the provision of AF signalling flow information, on receipt of an ST-Request, sends an ST-Answer. Comments: TP_PCRF_SN_04 Standards Reference: 4.4.5a ¶ 3 PICS item: Test purpose: Ensure that the IUT in the Open state, on receipt of an AA-Request subscribing to notifications of the status of the AF with the provision of AF signalling flow information, containing a Framed-IP-Address AVP indicating the full IP address of the UE containing a Media-Component-Description AVP containing a Media-Sub-Component AVP, containing a Flow-Number AVP containing two Flow-Description AVPs containing Flow-Usage AVP indicating AF_SIGNALLING containing Flow-Status AVP indicating ENABLED containing AF-Signalling-Protocol AVP indicating the signalling protocol between UE and AF containing Media-Component-Number AVP indicating ‘0’, sends an AA-Answer. Comments: In the case of IPv6 the Framed-IP-Address AVP is replaced by the Framed-IPv6-Prefix AVP. TP_PCRF_SN_05 Standards Reference: 4.4.5a ¶ 5 PICS item: Test purpose: Ensure that the IUT in the Open state having established an Rx diameter session with subscription to notifications of the status of the AF signalling transmission path with the provision of AF signalling flow information, on receipt of an ST-Request, sends an ST-Answer. Comments: |
da376d16eb2a7cd4aa93ea8ebb3b2ae8 | 101 580-2 | 4.4.2.6 Traffic Plane Events for PCRF Role | TP_PCRF_TPE_01 Standards Reference: 4.4.6.1 ¶ 1 PICS item: Test purpose: Ensure that when the IUT in the Open state having established an Rx diameter session, to indicate termination of an IP-CAN session, sends an AS- Request. Comments: It may be impossible to trigger the condition for sending of the AS-Request. TP_PCRF_TPE_01 Standards Reference: 4.4.6.1 ¶ 2 PICS item: Test purpose: Ensure that when the IUT in the Open state having established an Rx diameter session and having indicated termination of an IP-CAN session by sending an AS-Request, on receipt of an AS-Answer followed by an ST-Request, sends an ST-Answer. Comments: It may be impossible to trigger the condition for sending of the AS-Request. ETSI ETSI TS 101 580-2 V1.1.1 (2012-04) 15 History Document history V1.1.1 April 2012 Publication |
94385e3b1d95716ddca018b5efd763c0 | 101 580-1 | 1 Scope | The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the test specifications for the Diameter protocol on the Rx interface as specified in TS 129 214 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [3] and ETS 300 406 [4]. The supplier of a protocol implementation which is claimed to conform to TS 129 214 [1] is required to complete a copy of the PICS proforma provided in annex A of the present document and is required to provide the information necessary to identify both the supplier and the implementation. |
94385e3b1d95716ddca018b5efd763c0 | 101 580-1 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. |
94385e3b1d95716ddca018b5efd763c0 | 101 580-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 129 214: "Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Rx reference point (3GPP TS 29.214 version 10.5.0 Release 10)". [2] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [3] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [4] ETSI ETS 300 406: "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". [5] ETSI TS 129 212: "Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Gx/Sd reference point (3GPP TS 29.212 version 10.5.0 Release 10)". |
94385e3b1d95716ddca018b5efd763c0 | 101 580-1 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. ETSI ETSI TS 101 580-1 V1.1.1 (2012-04) 6 |
94385e3b1d95716ddca018b5efd763c0 | 101 580-1 | 3 Definitions and abbreviations | |
94385e3b1d95716ddca018b5efd763c0 | 101 580-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 129 214 [1] and the following apply: PICS proforma: document, in the form of a questionnaire, designed by the protocol specifier or conformance test suite specifier, which, when completed for an OSI implementation or system, becomes the PICS NOTE: See ISO/IEC 9646-1 [2]. Protocol Implementation Conformance Statement (PICS): statement made by the supplier of an Open Systems Interconnection (OSI) implementation or system, stating which capabilities have been implemented for a given OSI protocol NOTE: See ISO/IEC 9646-1 [2]. static conformance review: review of the extent to which the static conformance requirements are met by the IUT, accomplished by comparing the PICS with the static conformance requirements expressed in the relevant standard(s) NOTE: See ISO/IEC 9646-1 [2]. |
94385e3b1d95716ddca018b5efd763c0 | 101 580-1 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 129 214 [1] and the following apply: PICS Protocol Implementation Conformance Statement |
94385e3b1d95716ddca018b5efd763c0 | 101 580-1 | 4 Conformance | A PICS proforma which conforms to this PICS proforma specification shall be technically equivalent to annex A, and shall preserve the numbering and ordering of the items in annex A. A PICS which conforms to this PICS proforma specification shall: a) describe an implementation which claims to conform to TS 129 214 [1]; b) be a conforming ICS proforma which has been completed in accordance with the instructions for completion given in clause A.1; c) include the information necessary to uniquely identify both the supplier and the implementation. ETSI ETSI TS 101 580-1 V1.1.1 (2012-04) 7 Annex A (normative): PICS proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the PICS proforma in this annex so that it can be used for its intended purposes and may further publish the completed PICS proforma. A.1 Guidance for completing the ICS proforma A.1.1 Purposes and structure The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in relevant specifications may provide information about the implementation in a standardised manner. The PICS proforma is subdivided into clauses for the following categories of information: - instructions for completing the PICS proforma; - identification of the implementation; - identification of the protocol; - PICS proforma tables (for example: Major capabilities, etc). A.1.2 Abbreviations and conventions This annex does not reflect dynamic conformance requirements but static ones. In particular, a condition for support of a PDU parameter does not reflect requirements about the syntax of the PDU (i.e. the presence of a parameter) but the capability of the implementation to support the parameter. In the sending direction, the support of a parameter means that the implementation is able to send this parameter (but it does not mean that the implementation always sends it). In the receiving direction, it means that the implementation supports the whole semantic of the parameter that is described in the main part of the present document. As a consequence, PDU parameter tables in this annex are not the same as the tables describing the syntax of a PDU in the reference specification. The PICS proforma contained in this annex is comprised of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [3]. Item column The item column contains a number which identifies the item in the table. Item description column The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly means "is <item description> supported by the implementation?". Reference column The reference column gives reference to the relevant sections in core specifications. ETSI ETSI TS 101 580-1 V1.1.1 (2012-04) 8 Status column The various status used in this annex are in accordance with the rules in table A.1. Table A.1: Key to status codes Status code Status name Meaning m mandatory The capability shall be supported. It is a static view of the fact that the conformance requirements related to the capability in the reference specification are mandatory requirements. This does not mean that a given behaviour shall always be observed (this would be a dynamic view), but that it shall be observed when the implementation is placed in conditions where the conformance requirements from the reference specification compel it to do so. For instance, if the support for a parameter in a sent PDU is mandatory, it does not mean that it shall always be present, but that it shall be present according to the description of the behaviour in the reference specification (dynamic conformance requirement). o optional The capability may or may not be supported. It is an implementation choice. n/a not applicable It is impossible to use the capability. No answer in the support column is required. c.<integer> conditional The requirement on the capability ("m", "o", "n/a") depends on the support of other optional or conditional items. <integer> is the identifier of the conditional expression. o.<integer> qualified optional For mutually exclusive or selectable options from a set. <integer> is the identifier of the group of options, and the logic of selection of the options. Mnemonic column The Mnemonic column contains mnemonic identifiers for each item. Support column The support column shall be filled in by the supplier of the implementation. The following common notations, defined in ISO/IEC 9646-7 [3], are used for the support column: Y or y supported by the implementation N or n not supported by the implementation N/A, n/a or - no answer required (allowed only if the status is N/A, directly or after evaluation of a conditional status) References to items For each possible item answer (answer in the support column) within the PICS proforma there exists a unique reference, used, for example, in the conditional expressions. It is defined as the table identifier, followed by a solidus character "/", followed by the item number in the table. EXAMPLE: A.5/4 is the reference to the answer of item 4 in table A.5. A.1.3 Instructions for completing the PICS proforma The supplier of the implementation may complete the PICS proforma in each of the spaces provided. More detailed instructions are given at the beginning of the different clauses of the PICS proforma. A.2 Identification of the Network Equipment Identification of the Network Equipment should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if they are different. ETSI ETSI TS 101 580-1 V1.1.1 (2012-04) 9 A person who can answer queries regarding information supplied in the PICS should be named as the contact person. A.2.1 Date of the statement ......................................................................................................................................................................................... A.2.2 Network Equipment Under Test identification Name: ......................................................................................................................................................................................... ......................................................................................................................................................................................... Hardware configuration: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Software configuration: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... A.2.3 Product supplier Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... ETSI ETSI TS 101 580-1 V1.1.1 (2012-04) 10 A.2.4 Client Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... A.2.5 PICS contact person Name: ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... A.3 Identification of the protocol This PICS proforma applies to the following specification: • TS 129 214 [1]. ETSI ETSI TS 101 580-1 V1.1.1 (2012-04) 11 A.4 Global statement of conformance The implementation described in this PICS meets all the mandatory requirements of the referenced standard? [ ] Yes [ ] No NOTE: Answering "No" to this question indicates non-conformance to the protocol specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming. Explanations may be entered in the comments field at the bottom of each table or on attached pages. In the tabulations which follow, all references are to TS 129 214 [1] unless another numbered reference is explicitly indicated. A.5 PICS proforma tables A.5.1 Roles Table A.2: Roles Item Roles Reference clause Status Support 1 AF 4.3.1 o.1 2 PCRF 4.3.2 o.1 o.1: At least one of these roles shall be supported. A.5.2 System Capabilities for AF The tables provided in this clause need only to be completed for AF implementations, where item A.2/1 above is supported. Table A.3: System Capabilities for AF Item Does the IUT support ... Reference clause Status Support 1 Procedures for the initial provision of service information? 4.4.1 m 2 The sponsored data connectivity feature? 4.4.1, TS 129 212 [5], 4.5.20 o 3 Procedures for the modification of the session information? 4.4.2 o 4 Gate related procedures? 4.4.3 o 5 Procedures for the termination of AF sessions? 4.4.4 m 6 Procedures for the subscription to the notification of the status of the AF Signalling transmission path? 4.4.5 o 7 Procedures for the provision of information about AF Signalling IP flows? 4.4.5a o 8 Procedures for the handling of traffic plane events? 4.6 m ETSI ETSI TS 101 580-1 V1.1.1 (2012-04) 12 A.5.3 System Capabilities for PCRF The tables provided in this clause need only to be completed for PCRF implementations, where item A.2/2 above is supported. Table A.4: System Capabilities for PCRF Item Does the IUT support ... Reference clause Status Support 1 Checking of the service information provided by the AF? 4.3.2 o 2 Usage of the subscription information as basis for the policy and charging control decisions? 4.3.2 o 3 Procedures for the initial provision of service information? 4.4.1 m 4 The sponsored data connectivity feature? 4.4.1, TS 129 212 [5], 4.5.20 o 5 Procedures for the modification of the session information? 4.4.2 m 6 Gate related procedures? 4.4.3 m 7 Procedures for the termination of AF sessions? 4.4.4 m 8 Procedures for the subscription to the notification of the status of the AF Signalling transmission path? 4.4.5 m 9 Procedures for the provision of information about AF Signalling IP flows? 4.4.5a m 10 Procedures for the handling of traffic plane events? 4.6 m ETSI ETSI TS 101 580-1 V1.1.1 (2012-04) 13 History Document history V1.1.1 April 2012 Publication |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 1 Scope | The present 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. • For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y). |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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". [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". ETSI ETSI TS 101 416 V7.2.0 (2000-01) 7 (GSM 03.73 version 7.2.0 Release 1998) [12] GSM 11.14: "Digital cellular telecommunications system (Phase 2+); Specification of the SIM Application Toolkit for the Subscriber Identity Module –Mobile Equipment". |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 2.2 Informative references | [13] GSM 10.43: "Digital cellular telecommunications system; SoLSA, Work item status". |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 3 Definitions and abbreviations | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 3.1 Definitions | For the purposes of the present document, the following terms and 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. In the case of overlapping LSAs, the LSA with the highest priority shall be selected as current LSA. If there are more than one overlapping LSA with the highest priority any of those LSAs may be selected as current LSA. 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: LSA Localised Service Area LSA ID Localised Service Area Identity CSE Camel Service Environment |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 4 Main concepts | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. ETSI ETSI TS 101 416 V7.2.0 (2000-01) 8 (GSM 03.73 version 7.2.0 Release 1998) |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 4.3 Localised Service Area support in idle mode | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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). |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 4.4 Localised Service Area support in active mode | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. ETSI ETSI TS 101 416 V7.2.0 (2000-01) 9 (GSM 03.73 version 7.2.0 Release 1998) NOTE: For the handling of an established connection, it is out of scope of the present 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 |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 4.5 Localised Service Area support in access control | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 4.5.1 Emergency Call setup | The Emergency Call setup shall always be accepted by the MSC. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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 |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 4.5.3 (void) | 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. Service requests in exclusive access cells are accepted only for subscribers with subscription to the exclusive access cells. For subscribers with LSA only access call unrelated service requests are accepted even outside of the allowed LSAs. Active mode support may apply for call unrelated services. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 4.5.5 (void) | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 5 General architecture | No specific requirements are identified. The general architecture of GSM is maintained. ETSI ETSI TS 101 416 V7.2.0 (2000-01) 10 (GSM 03.73 version 7.2.0 Release 1998) 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 |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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: cell reselection in case of a LSA subscription; 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. 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: 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). For a user with a LSA service subscription, support is given for LSAs in active mode, with exception of the notification (LSA indication). |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 6.1 Handling of mobiles in exclusive access cells | The network shall broadcast information that the cell is used for exclusive access. This information is understood only by SoLSA compatible mobile stations. In order to prevent not allowed mobile stations to camp on exclusive access cells, the network may broadcast the escape PLMN code. The real PLMN code is still broadcast but only SoLSA compatible mobile stations can understand the information. If a location/routing area updating request is received in a cell broadcasting the escape PLMN code: • from a SoLSA compatible mobile station, the network shall not reject the request because of LSA subscription. ETSI ETSI TS 101 416 V7.2.0 (2000-01) 11 (GSM 03.73 version 7.2.0 Release 1998) • from a non-SoLSA compatible mobile station, the network shall reject the request with the cause 'PLMN not allowed'. • from a mobile station where the SoLSA compatibility is not known by the network (e.g. because classmark information was not received), the network shall neither accept nor reject the request. After a while, the mobile station may retry to perform the location/routing area updating. In order to know that the mobile station is SoLSA compatible, the network allows the mobile stations to perform 'early classmark sending procedure'. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 6.2 LSA support in network | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 6.2.1 VLR not supporting LSA | HLR shall reject roaming of a LSA only access subscriber to a VLR, which does not support LSA. A VLR supporting LSA shall indicate at location updating to the HLR that it supports LSA according to GSM 09.02. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 6.2.2 SGSN not supporting LSA | HLR shall reject roaming of a LSA only access subscriber to an SGSN, which does not support LSA. A SGSN supporting LSA shall indicate at location updating to the HLR that it supports LSA according to GSM 09.02. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 6.2.3 BSS not supporting LSA | This chapter handles networks where in the MSC/VLR service area only parts of the BSSs are supporting LSA. This configuration shall be seen as a network option. MSC/VLR shall reject MS originating/terminating call set-up for LSA only access subscribers when serving BSS does not support LSA. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 7 Transmission | No specific requirements are identified. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 8 Information storage | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 8.1 Information managed per subscriber | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 8.1.1 Stored in the HLR | The following mandatory information shall be stored in the HLR for each service subscriber: - a list of all the LSA Ids for the service subscriber; - the priority for each LSA; - the preferential access indicator for each LSA; - the LSA only access indicator. The following optional information may be stored in the HLR for each service subscriber: - LSA only access indication text (text to be displayed when out of LSA). ETSI ETSI TS 101 416 V7.2.0 (2000-01) 12 (GSM 03.73 version 7.2.0 Release 1998) The following optional information may also be stored for each subscribed LSA: - LSA name (A text string describing area and/or service. For example "ETSI BUILDING"); - LSA indication for idle mode (flag to activate/deactivate LSA indication in idle mode); - 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); - 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). |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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: a list of all the LSA Ids for the service subscriber; the priority for each LSA; the preferential access indicator for each LSA; the LSA only access indicator. The following optional information may also be stored for each subscribed LSA: 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 8.1.3 Stored in the SIM | The following mandatory information shall be stored in the SIM for each service subscriber: a list of all the LSA Ids for the service subscriber; the priority for each LSA; the LSA only access indicator. The following optional information may be stored in the SIM for each service subscriber: 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: a list of all the cell identities for the subscribed LSA; LSA name (A text string describing area and / or service. For example "ETSI BUILDING"); 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. ETSI ETSI TS 101 416 V7.2.0 (2000-01) 13 (GSM 03.73 version 7.2.0 Release 1998) |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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: a list of all the LSA Ids for the service subscriber; the priority for each LSA; the preferential access indicator for each LSA; the LSA only access indicator. The following optional information may also be stored for each subscribed LSA: 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 SGSN at the same time as other subscriber information is copied form HLR. SGSN entries shall be modified when corresponding HLR records are changed. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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 the present 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. ETSI ETSI TS 101 416 V7.2.0 (2000-01) 14 (GSM 03.73 version 7.2.0 Release 1998) |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 9 Identities | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 9.1 Identities for LSA | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 11 Function and information flows | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. ETSI ETSI TS 101 416 V7.2.0 (2000-01) 15 (GSM 03.73 version 7.2.0 Release 1998) 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: - 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. - 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. - 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 11.4 Functions related to MS in idle mode for support of LSA | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 11.4.1 Broadcast information | In cells belonging to a LSA, the LSA ID(s) and/or cell identity is broadcast. Further, in cells belonging to a LSA, which shall give exclusive access to a subscriber group, an exclusive access indication and/or the escape PLMN are broadcast. If the escape PLMN is broadcast then also the real PLMN code and a permission to the MS to perform 'early classmark sending' procedure are broadcast. To be able to favour the LSA cells at cell reselection new LSA reselection parameters are broadcast. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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 and indicate that escape PLMN is broadcast. This is done by adding the LSA ID(s) of current cell to the complete layer 3 information message for the exclusive access cell. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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 and indicate that escape PLMN is broadcast. This is done by adding the LSA ID(s) of current cell to the UL UNITDATA message for the exclusive access cell. ETSI ETSI TS 101 416 V7.2.0 (2000-01) 16 (GSM 03.73 version 7.2.0 Release 1998) |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 11.7 Functions related to active mode | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 11.7.1 MS connection establishment | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 11.7.1.1 Indication of list of LSAs 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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 LSA information sent to the BSS indicates the allowed LSA for the MS connection, their priorities, indication of preferential access per LSA, indication of active mode support per LSA and indication, whether or not, subscriber has only access to his allowed LSAs. 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) with active mode support and to prevent allocating resources in cells outside the allowed LSAs for the MS connection. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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 LSA information sent to the BSS indicates the allowed LSA 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) with active mode support and to prevent allocating resources in cells outside the allowed LSA for the MS connection. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 11.7.1.4 Indication of current LSA to the MSC | The BSS shall inform the MSC about the current LSA at successful assignment. In order to derive the current LSA, the BSS has to have received allowed LSAs before assignment (see subclause 11.7.1.2). If the MSC does not receive current LSA from the BSS at successful assignment, the MSC shall interpret that there is no current LSA. In case there is no assignment procedure between the MSC and the BSS (e.g. for short message transfer), the current LSA may be selected by the MSC on the basis of the allowed LSA(s) and the list of LSA ID(s) of the serving cell received from the BSS (see subclause 11.7.1). ETSI ETSI TS 101 416 V7.2.0 (2000-01) 17 (GSM 03.73 version 7.2.0 Release 1998) |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 11.7.2 Handover | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 11.7.2.1 Indication of allowed LSA to the target BSS | In case of BSS external handover, the MSC shall send the LSA information to the target BSS when requesting handover resource allocation. This information includes the allowed LSAs, their priorities, indication of preferential access per LSA, indication of active mode support per LSA and indication, whether or not, subscriber has only access to his allowed LSAs. The target BSS shall store the LSA information in order to use it at handovers and at possible assignments. In case of basic inter MSC handover, the MSC-A shall send the LSA information to the MSC-B when requesting handover resource allocation. The MSC-B shall deliver the LSA information to the target BSS and also store it for possible later use. In case of BSS external handover (after an inter MSC handover), the MSC-B shall send the stored LSA information to the target BSS when requesting handover resource allocation. This is the case for BSS external handover within the MSC-B but also for subsequent inter MSC handover to MSC-B' or back to MSC-A. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 11.7.2.2 Indication of current LSA to the MSC | In case of BSS external handover, the target BSS informs the MSC about the LSA ID of the potential new current LSA. This is done by adding the LSA ID of the current/new LSA to the handover request acknowledge message. In case of BSS internal handover, the BSS shall keep the MSC informed of the current LSA. This is done by adding the LSA ID of the current/new LSA to the handover performed message or assignment complete message (if handover performed during assignment). In case of basic inter MSC handover, the MSC-B shall inform the MSC-A about the potential new current LSA if a radio resource is available for handover. In case of BSS internal or BSS external handover within MSC-B (after an inter MSC handover), the MSC-B shall keep the MSC-A informed of the current LSA. In case of subsequent inter-MSC handover to third MSC (MSC-B'), the MSC-B' shall inform the MSC-A about the potential new current LSA if a radio resource is available for handover. NOTE: At handover, the potential new current LSA will become current LSA in case of successful handover completion. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 11.7.3 LSA active mode support | According to the LSA information received from the MSC (see subclause 11.7.1.2) or from the SGSN (see subclause 11.7.1.3), the BSS shall favour cells belonging to LSAs which have active mode support compared to other cells at resource allocation, network controlled cell reselection and handovers. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 11.7.4 LSA only access | If the subscriber is allowed to initiate/receive calls only in the allowed LSAs the BSS shall, if no current LSA can be selected, reject the assignment. Serving BSS shall not try to perform handover to cells that are outside of the allowed LSAs, if the subscriber only is allowed to access his allowed LSAs. Emergency calls shall be accepted even outside of allowed LSAs. ETSI ETSI TS 101 416 V7.2.0 (2000-01) 18 (GSM 03.73 version 7.2.0 Release 1998) |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 11.7.5 Exclusive Access | BSS shall try to allocate resources in exclusive access cells only if they are allowed for the subscriber. In the case no resources can be allocated in an allowed cell, the BSS shall reject the assignment request. Serving BSS shall not try to perform handover to exclusive access cells if they are not allowed for the subscriber. This is done so that exclusive access cells are not included into the handover required message. Emergency calls shall not be rejected because of exclusive access at assignment nor handover. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 11.7.6 Preferential Access | BSS shall favour subscribers who have preferential access to the LSA at resource allocation and in handovers compared to other subscribers. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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). ETSI ETSI TS 101 416 V7.2.0 (2000-01) 19 (GSM 03.73 version 7.2.0 Release 1998) 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, indication of active mode support per LSA and the LSA only access indicator of current PLMN. 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, indication of active mode support per LSA and the LSA only access indicator of current PLMN. ETSI ETSI TS 101 416 V7.2.0 (2000-01) 20 (GSM 03.73 version 7.2.0 Release 1998) 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 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. ETSI ETSI TS 101 416 V7.2.0 (2000-01) 21 (GSM 03.73 version 7.2.0 Release 1998) 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, indication of active mode support per 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. A_ASSIGNMENT_COMPLETE: Modified assignment complete including the LSA ID of current cell. ETSI ETSI TS 101 416 V7.2.0 (2000-01) 22 (GSM 03.73 version 7.2.0 Release 1998) 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, indication of active mode support per 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. ETSI ETSI TS 101 416 V7.2.0 (2000-01) 23 (GSM 03.73 version 7.2.0 Release 1998) 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 12 Charging | |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 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. |
2ff50194a724b72091ab07d6d4848112 | 101 416 | 12.2 Toll ticketing | Appropriate information concerning the change of charging due to the LSA change shall also be included in the charging record (toll ticket). ETSI ETSI TS 101 416 V7.2.0 (2000-01) 24 (GSM 03.73 version 7.2.0 Release 1998) 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 ETSI ETSI TS 101 416 V7.2.0 (2000-01) 25 (GSM 03.73 version 7.2.0 Release 1998) 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. ETSI ETSI TS 101 416 V7.2.0 (2000-01) 26 (GSM 03.73 version 7.2.0 Release 1998) CONTINUE: Modified CAP message indicating that the call continues without modifications. 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. ETSI ETSI TS 101 416 V7.2.0 (2000-01) 27 (GSM 03.73 version 7.2.0 Release 1998) Annex B (informative): Change History Document history 0.1.0 27.4.1998 First draft after SMG12 0.2.0 5.6.1998 Changes agreed in SoLSA workshop 5.6.1999 0.3.0 16.6.1998 Changes agreed in SMG12 16.6.1998 0.4.0 6.8.1998 Comments on version 0.3.0 0.5.0 19.8.1998 Changes agreed to 0.4.0 in SMG12 10.8.1998 0.6.0 8.9.1998 Comments on version 0.4.0 and 0.5.0 1.0.0 7/10/98 Edited for presentation to SMG for information 1.1.0 18/1/99 Comments on version 1.0.0 2.0.0 22/1/99 Approved by SMG12 7.0.0 5/7/99 Raised in v.7.0.0 after SMG#28 (technical content identical to v.2.0.0) 7.1.0 12/7/99 CRs agreed at SMG#29 implemented 7.2.0 6/1/00 CRs agreed at SMG#30 implemented ETSI ETSI TS 101 416 V7.2.0 (2000-01) 28 (GSM 03.73 version 7.2.0 Release 1998) History Document history V7.1.0 August 1999 Publication V7.2.0 January 2000 Publication |
0133c157924a68e4b323f84043ec6472 | 101 415 | 1 Scope | The present document, specifies a mechanism, which can be used as a platform for providing special tariffs and/or special set of service features for certain subscribers within a regionally restricted area or areas. The motivation for this concept is to create means for network operators to build new service and tariff packages, which take into account subscriber groups and their needs. The localised service area is both an optional network feature and an optional MS feature. Usage and implementation of the different SoLSA service features may vary according to operator's service packages. This feature is not intended to replace the existing method of cell selection, cell indication and handover. “Support of Localised service area (SoLSA)” is renamed Phase 2+ item “Support of Home Area Priority”. |
0133c157924a68e4b323f84043ec6472 | 101 415 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. • For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y). |
0133c157924a68e4b323f84043ec6472 | 101 415 | 2.1 Normative references | [1] GSM 02.06: "Digital cellular telecommunications system (Phase 2+); Types of Mobile Stations (MS)". [2] GSM 02.07: "Digital cellular telecommunications system (Phase 2+); Mobile Stations (MS) features". [3] GSM 02.11: "Digital cellular telecommunications system (Phase 2+); Service accessibility ". |
0133c157924a68e4b323f84043ec6472 | 101 415 | 2.2 Informative references | [4] GSM 10.43: "Digital cellular telecommunications system (Phase 2+); SoLSA, Work item status". [5] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". ETSI ETSI TS 101 415 V7.3.0 (2000-07) 6 (GSM 02.43 version 7.3.0 Release 1998) |
0133c157924a68e4b323f84043ec6472 | 101 415 | 3 Definitions and abbreviations | |
0133c157924a68e4b323f84043ec6472 | 101 415 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply. Localised Service Area (LSA): A localised service area consists of a cell or a number of cells within a PLMN. Cells being part of different localised service areas may have overlapping coverage areas. The cells constituting a localised service area may not necessarily provide continuous coverage. A LSA of four cells. An overlapping cell not part of LSA Figure 1: Localised Service Area Subscribed to LSA: Set of LSAs, which the user has subscribed to. Valid LSA: A LSA ,whichthe user has subscribed to and his MS can receive service. Current LSA: The LSA where a MS is receiving service. LSA Priority: Priority of subscriber's LSAs. When the user has several valid LSAs, the current LSA shall be selected by prioritising LSAs in case of overlapping LSAs. LSA "A" LSA "B" LSA "C" LSAs A, B and C are Subscribed to LSAs LSAs A and B are Valid LSAs LSA A is Current LSA = Subscriber Figure 2: Localised Service Areas LSA only access: LSA user is allowed to access PLMN within his allowed LSAs. LSA user is not allowed to receive and/or originate a call outside LSA area. ETSI ETSI TS 101 415 V7.3.0 (2000-07) 7 (GSM 02.43 version 7.3.0 Release 1998) LSA only access users are not allowed to receive and /or originate calls. LSA only access cells. All subscribed services available to user. Figure 3: LSA only access Exclusive Access: Access to exclusive access cells is restricted to defined LSA subscribers. Public cell, allowed for all users including exclusive access users. Private cell, only allowed for users with exclusive access. Figure 4: Exclusive Access Preferential Access: LSA user shall have preferential access to resources of LSA cells, compared to non-LSA users. Public cell, capacity allowed on equal basis for all users. Reserved resources for Preferential Access users. Limited capacity available to all other users. Figure 5: Preferential Access |
0133c157924a68e4b323f84043ec6472 | 101 415 | 3.2 Void | |
0133c157924a68e4b323f84043ec6472 | 101 415 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: LSA Localised Service Area ETSI ETSI TS 101 415 V7.3.0 (2000-07) 8 (GSM 02.43 version 7.3.0 Release 1998) Further GSM related abbreviations may be found in GSM 01.04. |
0133c157924a68e4b323f84043ec6472 | 101 415 | 4 Description | The localised service area concept shall give the operator the basis to offer subscribers different services (e.g. tariffs or access rights) depending on the location of the subscriber. |
0133c157924a68e4b323f84043ec6472 | 101 415 | 4.1 Defining subscriber information for localised service area | A subscriber can have up to 20 LSAs per PLMN. It shall be possible to assign localised service areas to subscribers. Subscriber may have service, which contains several LSAs potentially belonging to different PLMNs. There shall be means to allocate LSA priority to each subscriber independently by operator. Localised service areas for subscriber(s) may overlap, i.e. one cell may be part of several LSAs belonging to that subscriber. As an example, within a hierarchical cell structure, cells in different layers can constitute different localised service areas. A localised service area could be defined so that it is possible to establish flexible sized areas, which are applicable to - a very small localised service area ("home area" covering one or several cells dedicated e.g. to a residential subscriber or a company); or - a large area covering a part of the city (one or several location areas); or - a combination of these. Thus it is possible to use the various radio network configurations. The definition of location areas and the definition of localised service areas may be independent of each other. |
0133c157924a68e4b323f84043ec6472 | 101 415 | 4.2 Service Features | Following service features are building blocks for SoLSA based services. It is up to the operator to decide which service features are required for a specific service. - Localised service area indication. - Localised service area support in idle mode (camping). - Localised service area support in active mode (handover). - LSA only access. - Exclusive access. - Preferential access. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.