C.2 Cell identifiers for GAN A/Gb mode
3GPP43.318Generic Access Network (GAN)Release 17Stage 2TS
C.2.1 GAN Cell Id for Location Services & Billing
Cell Global Identities (CGI) may be used to perform location-basing routeing of a call for services such as: emergency services; operators; announcements and freephone numbers. Cell identities can be also used by the core network to identify the location of where a call was originated/terminated for charging purposes. The GANC provides a CGI to the core network indicating the GAN cell.
C.2.1.1 Assigning GAN Cell Id based on GSM location
In the GAN architecture, the MS has a direct IP-based connection to the GANC. The GAN coverage area may overlay the GERAN coverage area. Logical mapping of GAN Cells to a CGI can be completed at various resolutions, for example (but not limited to):
– a GAN cell for each GSM cell;
– a GAN cell for each GSM routeing area; or
– a GAN cell for each GSM location area.
A single GANC could represent one or more cells (CGI) in one or more location areas (LAI).
C.2.2 GAN Cell Id for handover-to-GAN
The GAN cell id used for location and charging can be independent from the GAN cell id used for handover.
A single GANC represents a single cell, and referred to as GAN cell, for the purpose of handover from GERAN to GAN. This "handover-GANC-CGI" is not visible to the MS. It is only used in the GERAN and CN for identifying a target cell (i.e. target GANC) for handover from GERAN to GAN, and ignored by the GANC, when received during the handover via the A-interface.
The "handover-GANC-CGI" assigned to the GANC is configured as the target handover cell in all neighbouring GERAN cells (in the ARFCN/BSIC-to-CGI mapping table). Neighbouring GERAN cells are those whose service area "overlaps" the GANC service area, for the purpose of handover.
For example, neighbour cells are:
– All GERAN cells attached to the same MSC as the GANC.
– All GERAN cells attached to a different MSC but that can handover to the MSC to which the GANC is attached.
When the MS reports measurements to the GERAN BSS on the GAN cell identified by its ARFCN/BSIC, then the GERAN BSS maps the ARFCN/BSIC to the "handover-GANC-CGI" through its mapping table, and is thus able to identify the target cell (GANC) for handover-to-GAN.
C.2.3 GAN ARFCN/BSIC for handover-to-GAN
The GERAN-to-GAN handover method makes use of an RF channel number (ARFCN) and base station identity code (BSIC) parameters to identify the GAN target cell. All GANCs in a given operator domain can share the same ARFCN/BSIC values, if there is a single GANC neighbour per GSM cell. This ARFCN/BSIC is indicated to the MS by the GANC during GAN registration.
The selection of the RF channel number (ARFCN) used for the UTRAN to GAN handover procedure should not correspond to a channel from any frequency band defined in 3GPP TS 45.005, to avoid UEs not requiring compressed mode for GSM measurements from unnecessarily powering up their GSM receivers.
C.3 (void)
Annex D (informative):
Change history
|
Change history |
|||||||
|
Date |
TSG GERAN# |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
2005-01 |
23 |
GP-050544 |
– |
– |
Version for Release 6 approved at TSG GERAN#23 |
2.0.0 |
6.0.0 |
|
2005-04 |
24 |
GP-050934 |
001 |
Introduction of the support for Cell Broadcast in GAN |
6.0.0 |
6.1.0 |
|
|
2005-06 |
25 |
GP-051594 |
003 |
Editorial correction PCCO to GAN |
6.1.0 |
6.2.0 |
|
|
2005-06 |
25 |
GP-051595 |
004 |
GERAN preferred mode MS behaviour |
6.1.0 |
6.2.0 |
|
|
2005-06 |
25 |
GP-051763 |
005 |
1 |
GAN only mode MS behaviour |
6.1.0 |
6.2.0 |
|
2005-06 |
25 |
GP-051704 |
007 |
Clarification to the CS charging description for GAN |
6.1.0 |
6.2.0 |
|
|
2005-09 |
26 |
GP-052142 |
0009 |
Removal of addressing for the Generic Access Network |
6.2.0 |
6.3.0 |
|
|
2005-11 |
27 |
GP-052796 |
0010 |
1 |
Clarifications to GAN Stage 2 |
6.3.0 |
6.4.0 |
|
2006-01 |
28 |
GP-060460 |
0008 |
6 |
Introduction of the Inter RAT Handover to GAN definition |
6.4.0 |
6.5.0 |
|
2006-01 |
28 |
GP-060391 |
0012 |
1 |
Clarifications to GAN Stage 2 |
6.4.0 |
6.5.0 |
|
2006-04 |
29 |
GP-060929 |
0013 |
1 |
Clarification on GANC Selection |
6.5.0 |
6.6.0 |
|
2006-04 |
29 |
GP-060924 |
0014 |
1 |
Rove-in description alignment with ‘Call re-establishment’ |
6.5.0 |
6.6.0 |
|
2006-05 |
30 |
GP-061188 |
0016 |
Clarification of GAN selection when MS in GERAN/UTRAN preferred mode |
6.6.0 |
6.7.0 |
|
|
2006-11 |
32 |
GP-062357 |
0018 |
1 |
GAN cell selection : Alignment with stage 3 |
6.7.0 |
6.8.0 |
|
2006-11 |
32 |
GP-062272 |
0019 |
Cryptographic algorithm update |
6.7.0 |
6.8.0 |
|
|
2006-11 |
32 |
GP-062119 |
0017 |
2 |
PS Handover Support for GAN |
6.8.0 |
7.0.0 |
|
2007-02 |
33 |
GP-070499 |
0021 |
3 |
Correction of BSSMAP messages in the Mobile Terminated Call Flow |
7.0.0 |
7.1.0 |
|
2007-05 |
34 |
GP-071010 |
0022 |
1 |
GERAN/UTRAN cells scan for rove-out in GAN mode |
7.1.0 |
7.2.0 |
|
2007-08 |
35 |
GP-071522 |
0024 |
3 |
Editorial corrections to GERAN and GSM references for GAN emergency procedures |
7.2.0 |
7.3.0 |
|
2007-11 |
36 |
GP-071945 |
0028 |
1 |
Change of specification title |
7.3.0 |
7.4.0 |
|
2007-11 |
36 |
GP-071977 |
0025 |
3 |
Addition of GAN Iu Mode functionality to GAN Stage 2 |
7.4.0 |
8.0.0 |
|
2007-11 |
36 |
GP-072013 |
0026 |
2 |
Maintaining PLMN Continuity in GAN Mode |
7.4.0 |
8.0.0 |
|
2008-02 |
37 |
GP-080397 |
0029 |
2 |
Supplementing GAN Registration Update with UARFCN |
8.0.0 |
8.1.0 |
|
2008-05 |
38 |
GP-080844 |
0030 |
1 |
Stage 2 changes to align with GAN Stage 3 |
8.1.0 |
8.2.0 |
|
2008-05 |
38 |
GP-080845 |
0033 |
1 |
Stage 2 clarification of MS deregistration after handover from GAN to GERAN/UTRAN |
8.1.0 |
8.2.0 |
|
2008-08 |
39 |
GP-081390 |
0034 |
2 |
Supporting Multiple GAN Modes per PLMN |
8.2.0 |
8.3.0 |
|
2009-02 |
41 |
GP-090164 |
0036 |
Clarification on the GANC Selection Process for PLMN Continuity |
8.3.0 |
8.4.0 |
|
|
2009-02 |
41 |
GP-090165 |
0037 |
Clarification on Maintaining PLMN Continuity in GAN Mode |
8.3.0 |
8.4.0 |
|
|
2009-12 |
44 |
Version for Release 9 |
8.4.0 |
9.0.0 |
|||
|
2010-11 |
48 |
GP-101977 |
0039 |
1 |
Changes to support rove in from LTE and rove out to LTE |
9.0.0 |
10.0.0 |
|
2010-11 |
48 |
GP-101970 |
0040 |
1 |
Changes to support RFC 4867 bandwidth-efficient mode |
9.0.0 |
10.0.0 |
|
2011-03 |
49 |
GP-110199 |
0041 |
GAN IPsec alignment |
10.0.0 |
10.1.0 |
|
|
2012-09 |
55 |
Version for Release 11 |
10.1.0 |
11.0.0 |
|||
|
2014-09 |
63 |
Version for Release 12 (frozen at SP-65) |
11.0.0 |
12.0.0 |
|||
|
2015-05 |
66 |
GP-150441 |
0042 |
Correction of reference to TS 29.234 |
12.0.0 |
12.1.0 |
|
|
2015-12 |
68 |
Version for Release 13 (frozen at SP-70) |
12.1.0 |
13.0.0 |
|||
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2016-12 |
RP-74 |
RP-162068 |
0043 |
– |
C |
Alignment according to withdrawal of I-WLAN feature |
13.1.0 |
|
2016-12 |
RP-74 |
RP-162067 |
0044 |
– |
C |
3GPP security profile update |
14.0.0 |
|
2017-03 |
RP-75 |
RP-170062 |
0045 |
– |
C |
3GPP security profile update |
14.1.0 |
|
2018-06 |
RP-80 |
– |
– |
– |
– |
Version for Release 15 (frozen at SP-80) |
15.0.0 |
|
2020-07 |
RP-88e |
– |
– |
– |
– |
Upgrade to Rel-16 version without technical change |
16.0.0 |
|
2022-03 |
RP-95e |
– |
– |
– |
– |
Upgrade to Rel-17 version without technical change |
17.0.0 |