hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
3e132ee54cef081bf4705ff3e4691de3 | 122 087 | 7.11 Barring of outgoing calls | ................................................................................................................................. 13 |
3e132ee54cef081bf4705ff3e4691de3 | 122 087 | 7.12 Barring of outgoing international calls | ............................................................................................................ 13 |
3e132ee54cef081bf4705ff3e4691de3 | 122 087 | 7.13 Barring of outgoing international calls except those directed to the home PLMN country | ............................. 13 |
3e132ee54cef081bf4705ff3e4691de3 | 122 087 | 7.14 Barring of incoming calls | ................................................................................................................................ 13 |
3e132ee54cef081bf4705ff3e4691de3 | 122 087 | 7.15 Barring of incoming calls when roaming outside the home PLMN country | ................................................... 13 |
3e132ee54cef081bf4705ff3e4691de3 | 122 087 | 7.16 Call Deflection | ................................................................................................................................................. 13 |
3e132ee54cef081bf4705ff3e4691de3 | 122 087 | 8 Interactions with other network features | ................................................................................................13 |
3e132ee54cef081bf4705ff3e4691de3 | 122 087 | 8.1 Support of Optimal Routeing | ........................................................................................................................... 13 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 4 3G TS 22.087 version 3.1.0 |
3e132ee54cef081bf4705ff3e4691de3 | 122 087 | 8.2 Multicall | ........................................................................................................................................................... 13 |
3e132ee54cef081bf4705ff3e4691de3 | 122 087 | 9 Interworking considerations | ..................................................................................................................13 Annex A (informative): Deviations of the 3GPP UUS supplementary service from the ISDN service.............................................................................................................15 Annex B: Change history ..............................................................................................................................16 History..............................................................................................................................................................17 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 5 3G TS 22.087 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.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 6 3G TS 22.087 version 3.1.0 1 Scope The User-to-User Signalling (UUS) supplementary service allows a mobile subscriber to send/receive a limited amount of information to/from another PLMN or ISDN subscriber over the signalling channel in association with a call to the other subscriber. 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. [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". [2] TS 22.004: General on supplementary services. [3] TS 22.030: Man-Machine Interface (MMI) of the Mobile Station (MS). [4] TS 21.905: "Vocabulary for 3GPP Specifications". [5] TS 22.135: "Multicall stage 1". 3 Definitions and Abbreviations 3.1 Definitions For the purposes of this TS, the following definitions apply: User-to-User Information (UUI): The information transferred by using the UUS supplementary service. UUS service: The UUS services (Service 1, 2 and 3) are components of the UUS supplementary service. If the UUS supplementary service is provided to a subscriber, she can handle the UUS services independently within a call. Served subscriber: The subscriber who has a provision of the UUS supplementary service and who activates the UUS supplementary service. For service 1 and 2 the served subscriber is always the calling subscriber, for service 3 either the calling or the called subscriber can be the served subscriber. Remote party: For service 1 and 2 the remote party is the called party of a call to which the UUS supplementary service is activated by the served subscriber. For service 3 the remote party can be either the called or the calling party of an established call to whom the use of the UUS supplementary service is requested by the served subscriber. 3.2 Abbreviations For the purposes of this TS the following abbreviations apply. UUS User-to-User Signalling UUI User-to-User Information Further GSM related abbreviations are listed in GSM 01.04 [1] and TS 21.905 [4]. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 7 3G TS 22.087 version 3.1.0 4 Description 4.1 Description The UUS supplementary service allows the served subscriber to send/receive a limited amount of subscriber generated information to/from another user in association with a call to the user. This information shall be passed transparently (i.e. without modification of contents) through the network. Normally, the network shall not interpret or act upon this information. The served subscriber can send and receive UUI in different phases of the call depending on the service(s) to which the subscriber subscribes. These services are: Service 1: UUI can be sent and received during the origination and termination of a call, with UUI embedded within call control messages. The service 1 can be activated implicit by inserting UUI when set-up a call or explicit with an appropriate procedure. Service 2: UUI can be sent and received after the served subscriber has received an indication that the remote party is being informed of the call and prior to the establishment of the connection. UUI sent by the served subscriber prior to receiving the acceptance of the call by the remote party, may as a network option be delivered to the remote party after the call has been established. The service 2 shall be activated explicitly. Service 3: User-to-user-information can be sent and received only while the connection is established. The service 3 shall be activated explicitly. Service 1, service 2 and service 3 shall allow the transmission of UUI with the maximum length of 128 octets per message. 4.2 Applicability to telecommunication services The applicability of this supplementary service is defined in TS 22.004 [2]. 5 Normal procedures with successful outcome 5.1 Provision The UUS supplementary service shall be provided to the served subscriber after pre-arrangement with the service provider. The remote party needs no subscription of the UUS supplementary service. NOTE: The remote party is able to send UUI without provision of the UUS supplementary service when the service is activated against her by the served subscriber. As a service provider option, one or any combination of the following shall be provided: - service 1 (implicitly requested andexplicitly requested); - service 2; - service 3. 5.2 Withdrawal The UUS supplementary service and several UUS services shall be withdrawn by the service provider upon the subscriber's request or for service providers reasons. The supplementary service UUS shall be withdrawn if all UUS services provided to the served subscriber are withdrawn. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 8 3G TS 22.087 version 3.1.0 5.3 Registration and Erasure not applicable. 5.4 Activation and Deactivation The UUS supplementary service shall be activated by the service provider as a result of provision and deactivated as a result of withdrawal. 5.5 Invocation The UUS supplementary service is invoked if at least one UUS service is activated by the served subscriber. 5.6 Interrogation not applicable. 5.7 Handling of UUS services 5.7.1 Activation UUS service is activated when: - activation is implicitly requested (for service 1); or - activation is explicitly requested (for service 1, service 2 and service 3) and is accepted by the remote party. Depending on the served subscriber subscription to the UUS supplementary service and the provision of the UUS services by the service provider, service 1 implicit, service 1 explicit, service 2 and service 3 can be activated individually or in combination. Service 1 implicit and service 1 explicit cannot be simultaneously active. Once an UUS service is activated the network shall accept UUI from either subscriber in the call, according to the service that has been activated. The network shall confirm the explicit activation of a UUS service (service 1, 2 and 3) to the served subscriber. This confirmation shall be preceded by an end-to-end check by the network for service availability. The network shall interrogate the remote party and check for the availability of the UUS service on the remote party's side. The mobile station shall confirm the requested services if it is able to handle the UUS service. The remote party shall not have the possibility to confirm or reject the request for the UUS service on a per call basis. No response from the remote party shall be taken by the network as a rejection of the request for the UUS service. NOTE: Nevertheless the remote party may restrict the use of a UUS service by pre-programming of the mobile station to reject incoming UUS activation requests. The network shall explicitly indicate to the calling mobile subscriber whether or not the requested service has been successfully activated. 5.7.1.1 Service 1 UUS service 1 shall be activated by the calling mobile subscriber when originating a call if UUI transfer is desired in either direction. Service 1 is automatically deactivated when the call is terminated. Service 1 can be activated by means of an implicit activation request or an explicit activation request. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 9 3G TS 22.087 version 3.1.0 Implicit activation: Service 1 is implicitly activated when UUI is included when originating a call. When service 1 is implicitly activated, service 1 is active for the call, i.e. the remote party is not required to send a response to the implicit activation request. However, the remote party can include UUI in the call response. Explicit activation: The UUS service 1 shall be activated explicitly by using of the procedure defined in TS 22.030 [3]. The served mobile subscriber shall be given an explicit response (acceptance or rejection) to an explicit activation request. An explicit activation request can include UUI. When service 1 is explicitly requested, the remote party can include UUI when accepting the activation request for the UUS supplementary service. 5.7.1.2 Service 2 The UUS service 2 shall be activated by using of the procedure defined in TS 22.030 [3]. Service 2 shall be activated by the served subscriber when originating a call, if UUI transfer is desired in either direction. Service 2 shall be explicitly requested. The served mobile subscriber shall be given an explicit response (acceptance or rejection) to an explicit activation request. Service 2 is automatically deactivated when the called subscriber is no longer being informed of the call, i.e. if the call is established or released. 5.7.1.3 Service 3 The served subscriber can explicit request the activation of service 3 when a call is originated or after the connection has been established by using the procedure defined in TS 22.030 [3]. The request for the UUS service 3 shall be accepted from the remote party in order to activate the UUS supplementary service. The served user shall be given an explicit response (acceptance or rejection) to the explicit activation request. Service 3 is automatically deactivated when the call is no longer established. 5.7.1.4 "UUS required" request When a call is originated, the calling subscriber can specify whether the requested UUS service(s) is (are) required for the call, i.e. if the call should be completed or not if UUI cannot be passed. If the "UUI-required" indication is given by the subscriber, the call shall not be completed if UUI cannot be passed to the called subscriber. If the "UUI-not- required" indication is given by the subscriber, the call will be completed even if UUI cannot be passed. If service 1 is implicitly requested or if service 3 is requested during the call, it cannot be requested as "UUI-required". 5.7.2 Invocation and operation If activated by the served subscriber a UUS service shall be invoked when UUI is sent by either subscriber to the network. When a subscriber sends UUI the network shall not confirm its delivery to the subscriber. For service 2 and 3, when sending a UUI message, the subscriber can indicate that the subscriber will send further UUI associated with this UUI message. This indication shall be given to the receiving subscriber. When sending a UUI message, the subscriber may indicate the use of particular user protocol associated with the UUI message. This indication shall be given to the receiving subscriber. The identification of, and the use of, user protocols is outside of this standard. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 10 3G TS 22.087 version 3.1.0 5.7.2.1 Service 1 A PLMN subscriber can transfer UUI when originating a call. When service 1 has been activated, either subscriber can include UUI when accepting, rejecting, or terminating a call. NOTE: It is possible for a calling subscriber to invoke the UUS service 1 with a call set-up and terminate the call before the connection is established. 5.7.2.2 Service 2 Any time between activation of service 2 and connection is established, either subscriber can transfer up to 2 UUI messages in each direction to the other subscriber involved in the call. 5.7.2.3 Service 3 After service 3 has been activated, either subscriber can transfer UUI to the other subscriber on the call after the connection has been established. NOTE: The amount of UUI messages that can be transferred with service 3 shall be defined. 5.7.2.4 Charging requirements The served subscriber shall be charged according to the number of UUI messages transferred in either direction. When charging for UUI the destination (e.g. international calls, diverted calls) of the related call shall not be considered. It shall be possible to charge for the invocation of the UUS supplementary service even if there are no other call charges. 6 Exceptional procedures or unsuccessful outcome 6.1 Provision and Withdrawal No exceptional procedures. 6.2 Registration and Erasure not applicable. 6.3 Handling of UUS services 6.3.1 Activation If the network cannot accept an implicit request for the activation of UUS service 1, no notification shall be given to the subscriber. In all other cases, if the network cannot accept a request for the activation of a UUS service, the network shall reject the activation. In addition, the network shall indicate which of service 1, service 2 and/or service 3 have been rejected. For the rejection of the activation request the following reasons may be possible: - service not subscribed to; - necessary signalling connectivity does not exist between sending and receiving subscribers; - conflicting situation with other supplementary service (e.g. CUG, incoming call barring); - service is already active; 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 11 3G TS 22.087 version 3.1.0 - network congestion. 6.3.2 Invocation The subscriber may not be able to interpret incoming UUI. In such situations, the user can discard this information without disrupting normal call handling. No specific signalling is provided by the network to accommodate this situation. Under circumstances of network congestion or failure, the network may discard services 2 and 3 UUI. 7 Interactions with other supplementary services 7.1 Call forwarding unconditional No impact NOTE: UUI or an activation request for a UUS service will be forwarded with the call even in the case the forwarding subscriber has no subscription of the relevant UUS service. 7.2 Call forwarding on mobile subscriber busy If call forwarding on mobile subscriber busy is invoked as a result of a network determined user busy condition (NDUB) of the called subscriber, any UUI and UUS request accompanies the call set-up request shall be forwarded with the call If call forwarding on mobile subscriber busy is invoked as a result of an user determined user busy condition (UDUB) the following cases shall be distinguished: - If the UDUB condition is met before alerting any UUI and UUS request accompanies the call set-up request shall be forwarded with the call. - If the UDUB condition is met after alerting the interactions as defined for call forwarding on no reply shall apply. UUI included in a UDUB request by the forwarding subscriber shall be ignored by the network. NOTE: UUI or an activation request for a UUS service will be forwarded with the call even in the case the forwarding subscriber has no subscription of the relevant UUS service. 7.3 Call forwarding on no reply Service 1: If UUS service 1 is implicitly requested to the forwarding subscriber the UUI shall be transferred to the forwarded-to party after the invocation of CFNRy. If UUS service 1 is explicitly requested with the option "UUS required“ to a called subscriber who has CFNRy active and operative and the no-reply condition timer expires, the call shall be released. If UUS service 1 is explicitly requested with the option "UUS not required“ to a called subscriber who has CFNRy active and operative, CFNRy shall be invoked. If the called subscriber has confirmed the UUS service 1 request prior to the invocation of CFNRy, the UUI and the UUS request shall be transferred to the forwarded-to party. Otherwise the UUI and the UUS request shall not be forwarded with the call. Service 2: If UUS service 2 is requested with the option "UUS not required“ to a called subscriber who has CFNRy active and operative, CFNRy shall be invoked but no UUS activation request will be given to the forwarded-to subscriber. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 12 3G TS 22.087 version 3.1.0 If UUS service 2 is requested with the option "UUS required“ to a called subscriber who has CFNRy active and operative, CFNRy shall not be invoked. Service 3: Any activation request for UUS service 3 that accompanies the call set-up request shall be forwarded with the call. NOTE: UUI or an activation request for a UUS service will be forwarded with the call even in the case the forwarding subscriber has no subscription of the relevant UUS service. 7.4 Call forwarding on mobile subscriber not reachable No impact NOTE: UUI or an activation request for a UUS service will be forwarded with the call even in the case the forwarding subscriber has no subscription of the relevant UUS service. 7.5 Call waiting UUI for the operation of UUS service 1 included in the call request shall be delivered with the call waiting indication to the called subscriber. There are no interactions with service 2 and service 3. 7.6 Call hold A subscriber who has invoked the Call Hold supplementary service may send or receive UUI to/from both the active and the held party. If the served subscriber has an active and a held call the mobile station shall indicate which party has sent a received UUI message. 7.7 Completion of calls to busy subscribers Requests for the activation of a UUS service contained in the original call request shall be stored with the request for the invocation of the CCBS supplementary service. The network shall also store any UUI containing in the original call request and use this stored UUI in the CCBS call. 7.8 Explicit call transfer When calls are transferred as a result of invocation of the explicit call transfer supplementary service, UUS services activated on either of the calls prior to the invocation of the explicit call transfer supplementary service shall be automatically deactivated by the network. No specific notification shall be sent to the involved subscribers when the UUS services are no longer activated. The subscribers involved in the transferred call may request the activation of service 3 again, if required. 7.9 Multi party service During a MPTY the MPTY-Manager can send and receive UUI to/from each remote party separately. The mobile station of the multi party manager shall indicate from which remote party a received UUI message was sent. UUI shall not be transferred between remote parties. 7.10 Advice of charge No impact. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 13 3G TS 22.087 version 3.1.0 NOTE: The Advice of Charge services may not provide any information concerning charges for the use of the UUS supplementary service. 7.11 Barring of outgoing calls no impact 7.12 Barring of outgoing international calls no impact 7.13 Barring of outgoing international calls except those directed to the home PLMN country no impact 7.14 Barring of incoming calls no impact. 7.15 Barring of incoming calls when roaming outside the home PLMN country no impact. 7.16 Call Deflection If Call Deflection is invoked before alerting the same interactions as for Call forwarding on mobile subscriber busy shall apply. If Call Deflection is invoked after alerting the same interactions as for Call forwarding on no reply shall apply. 8 Interactions with other network features 8.1 Support of Optimal Routeing The invocation of Optimal Routeing in case of late call forwarding shall have no impact on the interactions of UUS with the call forwarding supplementary services as defined in section 7. 8.2 Multicall See TS 22.135 [5]. The UUS supplementary service can be delivered only when both subscribers' networks provide a means of conveying the UUI. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 14 3G TS 22.087 version 3.1.0 Some networks may support the transmission of UUI with a maximum length of only 32 octets per message for service 1. In the interworking case only the first 32 octets of UUI with more than 32 octets per message shall be transferred. No notification about the limitation of the UUI shall be given to any subscriber. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 15 3G TS 22.087 version 3.1.0 Annex A (informative): Deviations of the 3GPP UUS supplementary service from the ISDN service The ISDN service UUS allows as a network option the transfer of UUI with a maximum length of 32 octets for service 1. This option shall not be supported in PLMNs. However there is the possibility that networks using the phase 1 or phase 2 standard can support the UUS service 1 implicitly requested with 32 octets. These networks shall apply the rules defined in the section 8, Interworking considerations. In the 3GPP specification some charging requirement are defined. These requirements shall allow network operators to charge their subscribers for the use of and to prevent misuse of the UUS supplementary service. Because of the different handling of busy states in ISDN the interactions with call forwarding on mobile subscriber busy are different. The network option to allow forwarding of UUS requests and UUI only if the forwarding subscriber has the subscription of the relevant UUS service is not supported. The general principle of CCBS to retain all information of the original call set-up and reusing this information for the CCBS call shall also be valid for the UUS supplementary service. Therefore the UUI contained in the original call set- up shall be stored in network and reused in the CCBS call. 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 16 3G TS 22.087 version 3.1.0 Annex B: Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.87 7.1.0 Transferred to 3GPP SA1 SA#04 22.087 3.0.0 SA#05 22.087 3.0.0 001 R99 3.0.1 Editorial update of references for GSM/3GPP use. SA#05 22.087 3.0.1 002 R99 3.1.0 Multicall (This CR was wrongly marked as 22.086 and should be to 22.087) 3G TS 22.087 version 3.1.0 Release 1999 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 17 3G TS 22.087 version 3.1.0 History Document history V3.0.0 July 1999 Transferred to TSG SA at ETSI SMG#29. Under TSG TSG SA Change Control. V3.0.1 October 1999 Inclusion of CR at SA#05 V3.1.0 December 1999 Inclusion of a subsequent CR from SA#05 3G TS 22.087 version 3.1.0 Release 1999 18 ETSI ETSI TS 122 087 V3.1.0 (2000-03) 3G TS 22.087 version 3.1.0 Release 1999 History Document history V3.1.0 March 2000 Publication |
2b7cc08a6cda16cef78883d84a691685 | 123 073 | 1 Scope | ........................................................................................................................................................5 |
2b7cc08a6cda16cef78883d84a691685 | 123 073 | 2 References | ................................................................................................................................................5 |
2b7cc08a6cda16cef78883d84a691685 | 123 073 | 2.1 Normative references | ......................................................................................................................................... 5 |
2b7cc08a6cda16cef78883d84a691685 | 123 073 | 2.2 Informative references | ....................................................................................................................................... 6 |
2b7cc08a6cda16cef78883d84a691685 | 123 073 | 3 Definitions and abbreviations | ..................................................................................................................6 |
2b7cc08a6cda16cef78883d84a691685 | 123 073 | 3.1 Definitions | ......................................................................................................................................................... 6 |
2b7cc08a6cda16cef78883d84a691685 | 123 073 | 3.2 Abbreviations | ..................................................................................................................................................... 6 |
2b7cc08a6cda16cef78883d84a691685 | 123 073 | 4 Main concepts | ..........................................................................................................................................7 |
2b7cc08a6cda16cef78883d84a691685 | 123 073 | 4.1 Localised Service Area definition | ...................................................................................................................... 7 |
2b7cc08a6cda16cef78883d84a691685 | 123 073 | 4.2 Subscriber information for Localised Service Area | ........................................................................................... 7 |
2b7cc08a6cda16cef78883d84a691685 | 123 073 | 4.3 Localised Service Area support in idle mode | .................................................................................................... 7 |
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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.