hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
41f4dd01af106b6509f05176f478e52b | 36.813 | 4.2.4 Overload Characteristics of GPS Receivers in Proximity to LTE Band 24 eNBs | In response to 3GPP RAN4 request for LightSquared to perform a study on the overload impact of LTE Band 24 on GPS receivers involved in cellular applications [21, 22], LightSquared has performed Field and Lab Tests for six (6) CellPhones/SmartPhones, as well as fixed GPS timing unites, used in network infrastructure, to determine the impact of LTE Band 24 eNB transmission to their overload Characteristics. The details of field and lab test configuration and test results are captured in [23], and [24]. A summary of the contents of [23] and [24] are provided in Section 4.2.4.1
Although results were provided for a limited number of devices (6), the study was concluded at this point considering that, in the meantime, a more comprehensive study, covering a wider variety of GPS receivers than those involved in cellular applications, was initiated under the auspices of the FCC [2]. The latter study will be conducted by a cross-industry group led by LightSquared and USGPSIC, the reports of the study having complete public visibility.
4.2.4.1 Summary of Study Results
In [23], a field trial was undertaken to test the operational behaviour of cell-phones equipped with GPS receivers in an open parking lot with some tree shadowing. The criterion of GPS service failure was defined to be the point where either the number of satellites tracked simultaneously fell below 4, or a positioning application on the device declared that it was switching from using GPS to cellular triangulation. The test results are summarized in Table 4.2.4-1.
Table 4.2.4-1 Per Carrier LTE Power Thresholds for GPS Receivers
Cell Phone GPS Test Results (Interferer Threshold Level at which device switches to AGPS)
One 5MHz carrier @ 1552.5MHz
One 10MHz carrier @ 1550.5MHz
Two 10MHz carriers @ 1550.5MHz & 1531MHz
Device 1
-15dBm
-16dBm
-17dBm
Device 2
-29dBm
-32dBm
-34dBm
Device 3
>-10dBm
>-10dBm
>-10dBm
Under the assumption and test set up described in [23], and LightSquared’s deployment plans regarding spectrum occupancy and base station EIRP, it was concluded (based on the particular analytical/geometric link calculation methods used and described in [23]) that, for one (1) out of the three (3) phones tested, the maximum exclusion zone (where GPS service would be affected as defined above) would be approximately 20m around the base of the tower. For two (2) phones, there were no exclusion zones at all. Interpreting the outdoor test results with a cellular planning tool, incorporating market specific morphologies, suggested that (for the one affected phone) the exclusion zone would be 1.1 – 2.5 % of the coverage area.
In addition to the work on mobile GPS receivers, [23] includes the work done by LightSquared over the past several years to analyze the overload effect of L-band base stations antennas on proximate timing unit GPS antennas. A GPS antenna pre-selector, sufficient to allow deployments as close as 3m, was specified by Lightsquared and developed by more than one GPS timing unit vendor. This antenna utilizes receive filters which produce a signal attenuation of 65 dB at 1575.42 MHz ±50 MHz.
In [24], lab results are provided for three additional smartPhone GPS receivers. The key performance indicators (KPI’s) used in this experiment were Position Error and SNR (as reported by the GPS processor). The results show that the Position Error was found to have a very sharp threshold, which often occurred at relatively high values of SNR degradation (in some cases around 10 dB) relative to the case of zero OOB LTE power. The GPS Rx Signal level used in the experiment was assumed to between -125dBm and -130dBm. The lab test setup is depicted in [24].
Eight (8) satellites were emulated for desired signal levels of -125 dBm and -130 dBm. In a given test, all emulated satellites had the same desired signal level. It is noteworthy, that these devices were tested in standalone GPS mode with no A-GPS assistance. In the real world, the mobile device may benefit from increased sensitivity offered by the mobile assistance data.
The results are captured in Table 4.2.4-24.2.4-2, 4.2.4-3, 4.2.4-4, 4.2.4-5, 4.2.4-6, and 4.2.4-7 for 3 devices under test. The average values were taken over 75 samples.
Table 4.2.4-2: Device 4 Measurements at -125 dBm GPS Rx Level
GPS/Sat
LTE
Avg
Avg
Sat
Sat
Sat
Sat
Sat
Sat
Sat
Sat
dBm
dBm
Error (2D) in meters
SNR
11
14
17
20
23
24
31
32
-125
OFF
5.80
35.07
35.06
35.05
35.15
35.04
35.05
35.15
35.05
35.03
-125
-50
6.53
34.60
34.41
34.63
34.76
34.51
34.67
34.77
34.71
34.34
-125
-40
5.21
34.40
34.47
34.43
34.42
34.51
34.49
34.03
34.51
34.32
-125
-30
6.61
34.76
34.75
34.73
34.84
34.75
34.77
34.74
34.78
34.68
-125
-25
5.39
33.63
33.79
34.06
34.09
33.56
33.09
33.70
33.51
33.26
-125
-20
6.19
32.21
32.30
32.17
32.17
32.28
32.30
31.92
32.37
32.17
-125
-15
4.66
31.68
31.78
32.45
31.96
31.51
31.52
31.42
31.49
31.28
-125
-10
6.17
28.30
25.76
31.35
28.25
29.52
26.1
29
25.2
31.17
Table 4.2.4-3: Device 5 Measurements at -125 dBm GPS Rx Level
GPS/Sat
LTE
Avg
Avg
Sat
Sat
Sat
Sat
Sat
Sat
Sat
Sat
dBm
dBm
Error (2D) in Meters
SNR
11
14
17
20
23
24
31
32
-125
OFF
7.57
36.11
36.11
36.11
36.14
36.11
36.08
36.11
36.14
36.08
-125
-50
7.41
36.05
36.04
36.04
36.06
36.06
36.02
36.04
36.04
36.06
-125
-40
7.11
35.33
35.34
35.36
35.36
35.34
35.32
35.27
35.39
35.29
-125
-30
7.12
33.05
33.04
33.11
33.26
32.96
32.94
33.06
33.06
32.94
-125
-25
5.45
32.38
32.19
32.51
32.39
32.38
32.48
32.18
32.47
32.45
-125
-20
7.00
27.84
27.81
27.94
27.77
27.90
27.75
27.79
27.92
27.87
-125
-15
38.22
27.09
27.83
26.75
26.70
27.19
26.55
27.72
26.80
27.16
-125
-10
35,960.34
22.44
25.79
23.81
19.29
20.00
20.41
26.27
19.76
24.18
Table 4.2.4-4: Device 6 Measurements at -125 dBm GPS Rx Level
GPS/Sat
LTE
Avg
Avg
Sat
Sat
Sat
Sat
Sat
Sat
Sat
Sat
dBm
dBm
Error (2D) in Meters
SNR
11
14
17
20
23
24
31
32
-125
OFF
2.49
34.21
34.21
34.20
34.23
34.18
34.20
34.23
34.24
34.20
-125
-50
3.01
34.73
34.74
34.74
34.75
34.71
34.72
34.76
34.71
34.73
-125
-40
6.03
34.77
34.77
34.78
34.80
34.72
34.74
34.83
34.74
34.75
-125
-30
4.28
34.69
34.67
34.70
34.70
34.67
34.69
34.73
34.66
34.68
-125
-25
4.74
34.62
34.63
34.62
34.63
34.60
34.61
34.66
34.59
34.61
-125
-20
4.36
34.45
34.45
34.46
34.48
34.45
34.42
34.49
34.40
34.44
-125
-15
4.87
33.44
33.44
33.42
33.46
33.46
33.41
33.49
33.41
33.42
-125
-10
4.44
31.44
31.55
31.53
31.58
31.57
31.51
31.02
31.56
31.21
Table 4.2.4-5: Device 4 Measurements at -130 dBm GPS Rx Level
GPS/Sat
LTE
Avg
Avg
Sat
Sat
Sat
Sat
Sat
Sat
Sat
Sat
dBm
dBm
Error (2D) in meters
SNR
11
14
17
20
23
24
31
32
-130
OFF
10.60
29.69
30.03
30.09
29.39
29.19
28.35
30.03
30.31
30.09
-130
-50
8.81
30.09
30.25
30.11
29.88
30.02
30.15
30.29
30.35
29.68
-130
-40
4.10
30.57
30.66
30.47
30.70
30.75
30.61
30.62
30.69
30.10
-130
-30
5.64
30.18
30.17
30.17
30.19
N/A
30.17
30.20
30.17
30.17
-130
-25
2.31
28.05
29.80
27.22
26.45
29.65
29.83
29.40
22.06
29.97
-130
-20
10.23
23.14
29.00
N/A
N/A
20.08
18.24
19.36
29.00
N/A
-130
-15
4.05
25.18
26.83
26.85
26.45
N/A
19.50
26.63
23.14
26.83
-130
-10
9.53
23.81
24.88
25.00
18.00
25.00
23.79
26.00
N/A
24.00
Table 4.2.4-6: Device 5 Measurements at -130 dBm GPS Rx Level
GPS/Sat
LTE
Avg
Avg
Sat
Sat
Sat
Sat
Sat
Sat
Sat
Sat
dBm
dBm
Error (2D) in meters
SNR
11
14
17
20
23
24
31
32
-130
OFF
10.16
30.91
30.91
30.89
30.95
30.89
30.87
31.12
30.81
30.83
-130
-50
6.99
30.57
30.60
30.54
30.61
30.48
30.54
30.67
30.59
30.53
-130
-40
7.01
29.19
29.16
29.19
29.18
29.21
29.18
29.18
29.23
29.21
-130
-30
6.80
28.11
28.15
28.14
28.27
28.12
28.05
28.14
28.29
27.73
-130
-25
6.57
26.60
27.01
25.06
26.11
26.88
26.67
27.07
27.01
26.97
-130
-20
28587.34
25.46
27.66
24.49
23.46
25.57
23.17
27.92
23.54
27.85
-130
-15
54597.55
25.38
26.60
21.78
27.30
24.52
20.46
27.47
26.61
28.32
-130
-10
46038.95
22.56
27.14
17.57
20.26
20.97
19.00
27.58
21.04
26.93
Table 4.2.4-7: Device 6 Measurements at -130 dBm GPS Rx Level
GPS/Sat
LTE
Avg
Avg
Sat
Sat
Sat
Sat
Sat
Sat
Sat
Sat
dBm
dBm
Error (2D) in meters
SNR
11
14
17
20
23
24
31
32
-130
OFF
4.78
30.56
30.56
30.58
30.58
30.55
30.53
30.61
30.53
30.56
-130
-50
4.11
30.17
30.20
30.21
30.18
30.13
30.17
30.21
30.13
30.14
-130
-40
14.00
30.62
30.61
N/A
30.64
30.62
30.63
30.64
N/A
30.59
-130
-30
6.27
29.74
29.75
29.76
29.75
29.72
29.73
29.77
29.70
29.76
-130
-25
5.51
29.93
29.95
29.92
29.96
29.91
29.91
29.95
29.92
29.92
-130
-20
4.82
29.71
29.73
29.72
29.73
29.71
29.76
29.75
29.63
29.67
-130
-15
5.16
28.53
28.62
28.60
28.58
28.46
28.49
28.47
28.52
28.53
-130
-10
37964.43
27.31
26.94
27.08
27.37
27.59
26.77
27.61
27.06
28.06
Also included in [24], is a description of a field trial to gather data about GPS received signal levels from different satellites in suburban and urban morphologies, validating the GPS receive signal strength used in the lab experiment (-125dBm and -130dBm) for outdoor use case. The field trial was performed using a widely used commercial GPS receiver, with a calibrated antenna mounted on the roof of a vehicle, allowing the C/N of signals received from individual satellites to be monitored, referenced to a 0 dBi antenna. Measurements were made in the open sky, suburban, and urban environments. |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5 Study of E-UTRA requirements | |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.1 Operating band and channel arrangement | |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.1.1 Operating bands | The L-Band LTE for ATC of MSS in North America is designed to operate in the operating band defined in Table 5.1.1-1:
Table 5.1.1-1: E-UTRA frequency bands
E‑UTRA Operating Band
Uplink (UL) operating band
BS receive
UE transmit
Downlink (DL) operating band
BS transmit
UE receive
Duplex Mode
FUL_low – FUL_high
FDL_low – FDL_high
24
1626.5 MHz
–
1660.5 MHz
1525 MHz
–
1559 MHz
FDD |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.1.2 Channel bandwidths per operating band | The transmission bandwidth configuration in Table 5.1.2-1 shall be supported for each of the specified channel bandwidths.
Table 5.1.2-1: E-UTRA channel bandwidth
E-UTRA band / channel bandwidth
E-UTRA Band
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
24
Yes
Yes |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.1.3 Carrier frequency and EARFCN | The relation between EARFCN and the carrier frequency in MHz for the downlink is given by the following equation, where FDL_low and NOffs-DL are given in Table 5.1.3-1 and NDL is the downlink EARFCN.
FDL = FDL_low + 0.1(NDL – NOffs-DL)
The relation between EARFCN and the carrier frequency in MHz for the uplink is given by the following equation where FUL_low and NOffs-UL are given in Table 5.1.3-1 and NUL is the uplink EARFCN.
FUL = FUL_low + 0.1(NUL – NOffs-UL)
Table 5.1.3-1: E-UTRA channel numbers
E-UTRA Operating
Band
Downlink
Uplink
FDL_low (MHz)
NOffs-DL
Range of NDL
FUL_low (MHz)
NOffs-UL
Range of NUL
24
1525
7700
7700 – 8039
1626.5
25700
25700 – 26039 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.1.4 TX–RX frequency separation | The default E-UTRA TX channel (carrier centre frequency) to RX channel (carrier centre frequency) separation is specified in Table 5.1.4-1 for the TX and RX channel bandwidths defined in Table 5.1.2-1.
Table 5.1.4-1: Default UE TX-RX frequency separation
E-UTRA Operating Band
TX - RX
carrier centre frequency
separation
24
-101.5 MHz |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.1.5 Band Release Independence | Band 24 is specified in Release 10, but is defined as a release-independent frequency band. This approach aligns the Band 24 band with other frequency bands when considering features that have to be supported in different releases.
UEs that conform to Release 8 and support Band 24 shall support the following requirements in Release 10.
Release 8 UEs shall comply with the Release 10 RF requirements for Band 24 specified in 3GPP TS 36.101 [7] as indicated in Table 5.1.5-1. These new requirements should be added as a new section of 3GPP TS 36.307 [13].
Table 5.1.5-1: RF Requirements for Band 24 UE
Section / Clause
Description
5.5
Operating bands
5.6
Channel bandwidth
5.7
Channel arrangement
6.2
Transmit power
6.3
Output power dynamics
6.6
Output RF spectrum emissions
6.7
Transmit intermodulation
7.3
Reference sensitivity power level
7.4
Maximum input level
7.5
Adjacent Channel Selectivity (ACS)
7.6
Blocking characteristics
7.7
Spurious response
7.8
Intermodulation characteristics
The UE shall comply with the Release 10 RF requirements for the following RRM requirements for Band 24 specified in 3GPP TS 36.133 [11] as indicated in Table 5.1.5-2:
Table 5.1.5-2: RRM Requirements for Band 24 UE
Section / Clause
Description
4
E-UTRAN RRC_IDLE state mobility
8
UE Measurements Procedures in RRC_CONNECTED State
9
Measurement Performances for UE.
A.9
Measurement Performances for UE Test Cases
Similar requirements for Release 9 UEs that conform to Release 10 support of Band 24 will be provided as well. |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.2 Specific UE RF requirements | |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.2.1 Maximum Output Power | Band 24 will operate at the same maximum output power level as bands listed in Table 5.2.1-1 (Table 6.2.2-1 from 3GPP TS 36.101 [7]). The following UE Power Classes define the maximum output power for any transmission bandwidth within the channel bandwidth.
Table 5.2.1-1: UE Power Class
EUTRA band
Class 1 (dBm)
Tolerance (dB)
Class 2 (dBm)
Tolerance (dB)
Class 3 (dBm)
Tolerance (dB)
Class 4 (dBm)
Tolerance (dB)
…
24
23
±2
… |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.2.2 Maximum Output Power with additional Requirements | Band 24 will use the default value for Additional Maximum Power Reduction (A-MPR) of 0 dB. |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.2.3 Spurious Emissions | Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emissions, inter-modulation products and frequency conversion products, but exclude out of band emissions.
In section 4.2.3 of the TR [2], LightSquared previously noted that the FCC requirements for L-Band to protect the GPS band were measured in terms of EIRP. However, owing to the proximity of Band 24 to the GPS band, RAN-4 requested that some assurance be provided in 3GPP TS 36.101 [7] that it would be feasible to meet the spurious emission requirements mandated by the FCC to protect GPS receivers. Therefore, 3GPP TS 36.101 [7] has been modified for Band 24 to meet the FCC requirements as conducted power requirements, assuming a UE 0 dBi antenna gain.
In terms of bands with harmonic issues relative to Band 24, it is known that 3GPP Band 13 has second order harmonics that fall into the downlink (1525 to 1559 MHz) of Band 24. Along with the addition of Band 24, an exception for Band 13 has been added to Table 5.2.3-1 (Table 6.6.3.2-1 in 3GPP TS 36.101 [7]) for the UE-to-UE requirements below.
Table 5.2.3-1: Requirements
E-UTRA Band
Spurious emission
Protected band
Frequency range
(MHz)
Maximum Level (dBm)
MBW (MHz)
Comment
1
E-UTRA Band 1, 3, 7, 8, 9, 11, 20, 21, 34, 38, 40
FDL_low
-
FDL_high
-50
1
E-UTRA band 33
FDL_low
-
FDL_high
-50
1
Note3
E-UTRA band 39
FDL_low
-
FDL_high
-50
1
Note3
Frequency range
860
-
895
-50
1
Frequency range
1884.5
-
1919.6
-41
0.3
Note6,Note7
1884.5
-
1915.7
Note 6, Note8
2
E-UTRA Band 2, 4, 5, 10, 12, 13, 14, 17, 24
FDL_low
-
FDL_high
-50
1
3
E-UTRA Band 1, 3, 7, 8, 20, 33, 34, 38
FDL_low
-
FDL_high
-50
1
4
E-UTRA Band 2, 4, 5, 10, 12, 13, 14, 17, 24
FDL_low
-
FDL_high
-50
1
5
E-UTRA Band 2, 4, 5, 10, 12, 13, 14, 17, 24
FDL_low
-
FDL_high
-50
1
6
E-UTRA Band 1, 9, 11, 34
FDL_low
-
FDL_high
-50
1
Frequency range
860
-
875
-37
1
Frequency range
875
-
895
-50
1
Frequency range
1884.5
-
1919.6
-41
0.3
Note7
1884.5
-
1915.7
Note8
7
E-UTRA Band 1, 3, 7, 8, 20, 33, 34
FDL_low
-
FDL_high
-50
1
E-UTRA Band 38
FDL_low
-
FDL_high
-50
1
Note 3
8
E-UTRA Band 1, 8, 20, 33, 34, 38, 39, 40
FDL_low
-
FDL_high
-50
1
E-UTRA band 3
FDL_low
-
FDL_high
-50
1
Note 2
E-UTRA band 7
FDL_low
-
FDL_high
-50
1
Note 2
9
E-UTRA Band 1, 9, 11, 21, 34
FDL_low
-
FDL_high
-50
1
Frequency range
860
-
895
-50
1
Frequency range
1884.5
-
1919.6
-41
0.3
Note7
1884.5
-
1915.7
Note8
10
E-UTRA Band 2, 4, 5, 10, 12, 13, 14, 17, 24
FDL_low
-
FDL_high
-50
1
11
E-UTRA Band 1, 9, 11, 21, 34
FDL_low
-
FDL_high
-50
1
Frequency range
860
-
895
-50
1
Frequency range
1884.5
1919.6
-41
0.3
Note7
1884.5
-
1915.7
Note8
12
E-UTRA Band 2, 5, 12, 13, 14, 17, 24
FDL_low
-
FDL_high
-50
1
E-UTRA Band 4, 10
FDL_low
-
FDL_high
-50
1
Note2
13
E-UTRA Band 2, 4, 5, 10, 12, 13, 14, 17
FDL_low
-
FDL_high
-50
1
E-UTRA Band 24
FDL_low
-
FDL_high
-50
1
Note2
Frequency range
763
-
775
-35
0.00625
14
E-UTRA Band 2, 4, 5, 10, 12, 13, 14, 17, 24
FDL_low
-
FDL_high
-50
1
Frequency range
763
-
775
-35
0.00625
17
E-UTRA Band 2, 5, 12, 13, 14, 17, 24
FDL_low
-
FDL_high
-50
1
E-UTRA Band 4, 10
FDL_low
-
FDL_high
-50
1
Note2
18
E-UTRA Band 1, 9, 11, 21, 34
FDL_low
-
FDL_high
-50
1
Frequency range
860
-
895
-40
1
Frequency range
1884.5
-
1919.6
-41
0.3
Note7
1884.5
-
1915.7
Note8
19
E-UTRA Band 1, 9, 11, 21, 34
FDL_low
-
FDL_high
-50
1
Frequency range
860
-
895
-40
1
Note9
Frequency range
1884.5
-
1919.6
-41
0.3
Note7
1884.5
-
1915.7
Note8
20
E-UTRA Band 1, 3, 7, 8, 33, 34, 38, 39, 40
FDL_low
-
FDL_high
-50
1
E-UTRA Band 38
FDL_low
-
FDL_high
-50
1
Note 2
21
E-UTRA Band 11, 21
FDL_low
-
FDL_high
-35
1
Note10
E-UTRA Band 1, 9, 34
FDL_low
-
FDL_high
-50
1
Frequency range
860
-
895
-50
1
Frequency range
1884.5
-
1919.6
-41
0.3
Note7
1884.5
-
1915.7
Note8
…
24
E-UTRA Band 2, 4, 5, 10, 12, 13, 14, 17, 24
FDL_low
-
FDL_high
-50
1
…
33
E-UTRA Band 1, 3, 7, 8, 20, 34, 38, 39, 40
FDL_low
-
FDL_high
-50
1
Note5
34
E-UTRA Band 1, 3, 7, 8, 9, 11, 20, 21, 33, 38,39, 40
FDL_low
-
FDL_high
-50
1
Note5
Frequency range
860
-
895
-50
1
Frequency range
1884.5
-
1919.6
-41
0.3
Note7
1884.5
-
1915.7
Note8
35
36
37
-
38
E-UTRA Band 1,3, 8, 20, 33, 34
FDL_low
-
FDL_high
-50
1
E-UTRA Band 7
FDL_low
-
FDL_high
-50
1
Note3
39
E-UTRA Band 34, 40
FDL_low
-
FDL_high
-50
1
40
E-UTRA Band 1, 3, 20, 33, 34, 39
FDL_low
-
FDL_high
-50
1
Note 1: FDL_low and FDL_high refer to each E-UTRA frequency band specified in 3GPP TS 36.101 [7] Table 5.5-1
Note 2: As exceptions, measurements with a level up to the applicable requirements defined in 3GPP TS 36.101 [7] Table 6.6.3.1-2 are permitted for each assigned E-UTRA carrier used in the measurement due to 2nd or 3rd harmonic spurious emissions. An exception is allowed if there is at least one individual RE within the transmission bandwidth (see Figure 5.6-1) for which the 2nd or 3rd harmonic, i.e. the frequency equal to two or three times the frequency of that RE, is within the measurement bandwidth (MBW).
Note 3: To meet these requirements some restriction will be needed for either the operating band or protected band
Note 4: N/A
Note 5: For non synchronised TDD operation to meet these requirements some restriction will be needed for either the operating band or protected band
Note 6: Applicable when NS_05 in section 6.6.3.3.1 is signalled by the network.
Note 7: Applicable when co-existence with PHS system operating in 1884.5-1919.6 MHz.
Note 8: Applicable when co-existence with PHS system operating in 1884.5 -1915.7 MHz.
Note 9: Applicable when NS_08 in section 6.6.3.3.3 is signalled by the network
Note 10: Applicable when NS_09 in section 6.6.3.3.4 is signalled by the network |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.2.4 Reference Sensitivity Power Level | The reference sensitivity power level REFSENS is the minimum mean power applied to both the UE antenna ports at which the throughput shall meet or exceed the requirements for the specified reference measurement channel.
For the PREFSENS parameters provided in Table 5.2.4-1 below (from 3GPP TS 36.101 [7], Table 7.3.1-1) for Band 24, the following link budgets for the 5 and 10 MHz bandwidth cases have been calculated as follows:
● For 5 MHz: -174 + 10*log(4.5 MHz) + NF + SNR + CL – DG + IM = -100 dBm
● For 10 MHz: -174 + 10*log(9.0 MHz) + NF + SNR + CL – DG + IM = -97 dBm
Where:
- NF (noise figure) = 9 dB
- SNR (for QPSK @ rate 1/3)= - 1 dB
- CL (Rx combiner loss) = 0.5 dB
- DG (Rx diversity gain) = 3 dB
- IM (implementation margin) = 2 dB
Table 5.2.4-1: Reference sensitivity QPSK PREFSENS
Channel bandwidth
E-UTRA Band
1.4 MHz
(dBm)
3 MHz
(dBm)
5 MHz
(dBm)
10 MHz
(dBm)
15 MHz
(dBm)
20 MHz
(dBm)
Duplex Mode
…
24
-100
-97
FDD
…
Table 5.2.4-2 (3GPP TS36.101, Table 7.3.1-2) specifies the minimum number of allocated uplink resource blocks for which the reference receive sensitivity requirement must be met. Band 24 is capable of transmitting all available RB’s on the uplink.
Table 5.2.4-2: Minimum uplink configuration for reference sensitivity
E-UTRA Band / Channel bandwidth / NRB / Duplex mode
E-UTRA Band
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
Duplex Mode
…
24
25
50
FDD
…
The combination of channel bandwidths and operating bands for E-UTRA is shown in Table Table 5.2.4-3 (3GPP TS 36.101 [7], Table 5.6.1-1). The transmission bandwidth configuration in Table 5.2.4-3 is supported by Band 24 for each of the specified channel bandwidths.
Table 5.2.4-3: E-UTRA channel bandwidth
E-UTRA band / channel bandwidth
E-UTRA Band
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
...
24
Yes
Yes
... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3 Specific BS RF requirements | |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3.1 Operating band unwanted emissions | The operating band unwanted emission limits, specified in EIRP metrics, are defined from 10 MHz below the lowest frequency of the downlink operating band up to 10 MHz above the highest frequency of the downlink operating band. The requirements shall apply to whatever the type of transmitter considered (single carrier or multi-carrier) and for all transmission modes foreseen by the manufacturer's specification.
As discussed in Section 4, the BS out-of-band-emission limits mandated by the FCC on this band, in general, are specified as required attenuation below the mean output power of the transmitter in accordance with Table 5.3.1-1 below. These should be viewed as the minimum, default requirements, and may be superseded by additional requirements where so specified.
Table 5.3.1-1: FCC emission limits for the L-Band
Frequency offset (f_offset) from the FCC authorized bandwidth (B)
Attenuation (dB) below the mean output power in watts (P) of the transmitter
Measurement bandwidth
B/2 f_offset < B
25
4 kHz
B f_offset < 5B/2
35
4 kHz
5B/2 f_offset
43 + 10log(P)
4 kHz
The quantity B in Table 5.3.1-1 is the FCC authorized BW which corresponds to the LTE channel bandwidth in 3GPP. Requirements in Table 5.3.1-1 are measured from the carrier centre frequency. As requirements should be measured from the channel edge as is usual in 3GPP, the requirements are converted as shown in Table 5.3.1-2 for the 5 and 10 MHz channel bandwidth.
Table 5.3.1-2: FCC emission limits related to channel edge for the L-Band
Channel bandwidth
Frequency offset of measurement filter ‑3dB point, f
Frequency offset of measurement filter centre frequency, f_offset
Minimum requirement attenuation (dB) below maximum output power in watts (P) of the transmitter
Measurement bandwidth
5 MHz
0 MHz f < 2.5 MHz
0.002 MHz f_offset < 2.502 MHz
25
4 kHz
2.5 MHz f < 10 MHz
2.502 MHz f_offset < 10.002 MHz
35
4 kHz
10 MHz f < fmax
10.002 MHz MHz f_offset < f_offsetmax
43 + 10log(P)
4 kHz
10 MHz
0 MHz f < 5 MHz
0.002 MHz f_offset < 5.002 MHz
25
4 kHz
5 MHz f < 20 MHz
5.002 MHz f_offset < 20.002 MHz
35
4 kHz
20 MHz f < fmax
20.002 MHz MHz f_offset < f_offsetmax
43 + 10log(P)
4 kHz
The operating band unwanted emission limits for Category A for E‑UTRA bands >1GHz (as specified in Clause 6.6.3 of 3GPP TS 36.104 [8] and 3GPP TS 36.141 [12]) and the FCC emission limits for this band are shown in Figure 5.3.1-1 below for the 5MHz channel bandwidth option, for the cases of Wide Area, Local Area, and Home BS with 46 dBm, 24 dBm, and 20 dBm output power, respectively. It can be seen that the operating band unwanted emission (Category A) limits are always tighter. Therefore, the operating band unwanted emission limits for Category A for E‑UTRA bands >1GHz shall be applied to this band. Note that the operating band unwanted emission limits for Category B are not applicable in North America, and thus need not be specified for this band.
(1a) Wide Area BS with 46 dBm output power
(1b) Local Area BS with 24 dBm output power
(1c) Home BS with 20 dBm output power
Figure 5.3.1-1: The operating band unwanted emission (Category A) limits for E‑UTRA bands >1GHz and the additional (FCC) limits |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3.2 Additional spurious emissions requirements | These requirements may be applied for the protection of systems operating in frequency ranges other than the E-UTRA BS downlink operating band. The limits may apply as an optional protection of such systems that are deployed in the same geographical area as the E-UTRA BS, or they may be set by local or regional regulation as a mandatory requirement for an E-UTRA operating band.
The E-UTRA BS spurious emissions limits currently specified for co-existence with systems operating in other frequency bands are more stringent than the out-of-band emissions limits by the FCC. To ensure sufficient protection to the co-existing systems, the same limits as the other E-UTRA bands BS apply for this band in Clause 6.6.4.3 of 3GPP TS 36.104 [8] (Tables 6.6.4.3.1-1 and 6.6.4.3.1-1x) and Clause 6.6.4.5.4 of 3GPP TS 36.141 [12] (Tables 6.6.4.5.4-1 and 6.6.4.5.4-1x). And to ensure sufficient protection from the co-existing systems, the same limits as the other E-UTRA bands BS shall be specified for coexistence with the BS in this band in Clause 6.6.4.3 of 3GPP TS 36.104 [8] (Tables 6.6.4.3.1-1 and 6.6.4.3.1-1x) and Clause 6.6.4.5.4 of 3GPP TS 36.141 [12] (Tables 6.6.4.5.4-1 and 6.6.4.5.4-1x).
Moreover, as discussed in Section 4, the BS in this band shall meet the following limits on emissions into the 1559-1610 MHz band as requested in [6] and shown in Table 5.3.2-1 below:
Table 5.3.2-1: FCC emission limits into the 1559-1610 MHz band
Frequency
dBW/MHz EIRP
(Measurement bandwidth = 1 MHz)
dBW EIRP of discrete emissions
of less than 700 Hz bandwidth
(Measurement bandwidth = 1 kHz)
Wide Area and Local Area Base Stations
1559-1610 MHz
-100
-110
Home Base Stations
1559-1605 MHz
-114.7
-110
This emission limit is expressed as EIRP, not as a conducted emission requirement suitable for BS equipment. EIRP (effective isotropic radiated power), is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). In this form, the EIRP requirement is not testable at the BS antenna connector. An alternative is to define maximum unwanted emission levels based on declared values by the manufacturer, similarly to the requirements for Band 20 for DTT band protection in 3GPP TS 36.104 [8] Table 6.6.3.3-4. To provide assurance that the FCC mandated emission levels for the protection of GPS can be achieved by practical base stations, Appendix A provides an example of an actual base station mask for a particular antenna gain and cable loss.
Even though the victim band 1559 – 1610 MHz band is still within 10 MHz of Band 24 DL operating band, it is proposed that this FCC requirement shall be specified as additional spurious emissions requirements in Clause 6.6.4.3 of TS 36 104.
Maximum emission levels shall be specified as PE_1MHz and PE_1kHz which are declared values by the manufacturer. The requirement then provides the characteristics of the base station needed to verify compliance with the regional EIRP requirement.
The following Table 5.3.2-2 and note shall be added to 3GPP TS 36.104 [8] and 3GPP TS36.141 [12] (as Table 5.3-4):
Table 5.3.2-2: Declared emissions levels for protection of the 1559-1610 MHz band
Operating Band
Frequency range
Declared emission level [dBW]
(Measurement bandwidth = 1 MHz)
Declared emission level [dBW] of discrete emissions of less than 700 Hz bandwidth
(Measurement bandwidth = 1 kHz)
24
1559 - 1610 MHz
PE_1MHz
PE_1kHz
Note: The regional requirement is defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The EIRP level is calculated using: PEIRP = PE + Gant where PE denotes the BS unwanted emission level at the antenna connector, Gant equals the BS antenna gain minus feeder loss. The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3.3 Co-location with other base stations | These requirements may be applied for the protection of other BS receivers when GSM900, DCS1800, PCS1900, GSM850, UTRA FDD, UTRA TDD and/or E-UTRA BS are co-located with an E-UTRA BS. The requirements assume a 30 dB coupling loss between transmitter and receiver and are based on co-location with base stations of the same class.
The E-UTRA BS spurious emissions limits currently specified for co-location with another BS are more stringent than the out-of-band emissions limits by the FCC. To ensure sufficient protection to the co-located BS, the same BS limits as the other E-UTRA bands use shall be specified for this band in Clause 6.6.4.4 of 3GPP TS 36.104 [8] and Clause 6.6.4.5.5 of 3GPP TS 36.141 [12]. To ensure sufficient protection from the co-located BS, the same BS limits as the other E-UTRA bands use shall be specified for co-location with the BS in this band in Clause 6.6.4.3 of 3GPP TS 36.104 [8] and Clause 6.6.4.5.4 of 3GPP TS 36.141 [12]. |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3.4 General blocking requirement | The blocking characteristics are a measure of the receiver’s ability to receive a wanted signal at its assigned channel in the presence of an unwanted interferer, which is a 1.4MHz, 3MHz or 5MHz E-UTRA signal for in-band blocking or a CW signal for out-of-band blocking.
The general blocking requirements currently specified for E-UTRA BS apply the in-band blocking signal within the +/-20 MHz of the UL frequency range of a band, except when the DL frequency range of the same band falls within such range. Since the duplex distance of this band is larger than 20 MHz and thus no exception is needed, the same general blocking requirements as specified for E-UTRA Bands 2 and 5 BS shall be specified for this band in Clause 7.6.1 of 3GPP TS 36.104 [8] and Clause 7.6.5.1 of 3GPP TS 36.141 [12] to ensure sufficient BS receiver blocking ability. |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3.5 Blocking requirement for co-location with other base stations | This additional blocking requirement may be applied for the protection of E-UTRA BS receivers when GSM, UTRA or E-UTRA BS operating in a different frequency band are co-located with an E-UTRA BS. The requirements assume a 30 dB coupling loss between interfering transmitter and E-UTRA BS receiver and are based on co-location with base stations of the same class.
The blocking requirements currently specified for E-UTRA BS when co-located with BS in other frequency bands do not apply when the interfering signal falls within the +/-10 MHz of the UL frequency range of a band, except for Band 13 in order to allow co-location with Band 14 BS. Since no UTRA/E-UTRA DL is operating within the +/-10 MHz of the UL frequency range of this band, the blocking requirements shall be specified for this band in Clause 7.6.2 of 3GPP TS 36.104 [8] and Clause 7.6.5.2 of 3GPP TS 36.141 [12] using the same interfering signal as the other E-UTRA bands BS, and do not apply when the interfering signal falls within +/-10 MHz of the UL frequency range of this band (i.e. 1616.5 – 1670.5 MHz). |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3.6 UTRAN requirements | |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3.6.1 Required changes to 3GPP TS 25.461 | In 3GPP TS 25.461 [14], section 4.3.7 “Operating bands” and the corresponding Table 4.3.7.1 (Table 5.3.6.1-1 below) “Frequency bands” of 3GPP TS 25.461 [14] require alteration to accommodate the new L_Band_LTE_ATC_MSS frequency band parameters, as follows. (Section 6.8 of the TR for the work item summarizes these changes.)
Table 5.3.6.1-1: Frequency bands
UTRA Operating Band
E-UTRA Operating Band
UL operating band
UE transmit, BS receive
DL operating band
UE receive, BS transmit
–
24
1626.5 – 1660.5 MHz
1525 – 1559 MHz |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3.6.2 Required changes to 3GPP TS 25.466 | In 3GPP TS 25.466 [15], Annex B “Assigned fields for additional data” and the corresponding Table B.2-1 (Table 5.3.6.2-1 in 3GPP TS 25.466 [15]) “Coding for operating bands in field 0x08” of 3GPP TS 25.466 [15] require alteration to accommodate the new L_Band_LTE_ATC_MSS frequency band parameters, as follows. (Section 6.9 of the TR for the work item summarizes these changes.)
Table 5.3.6.2-1: Coding for operating bands in field 0x08
Bit no
15
14…10
9
8
7
6
5
4
3
2
1
0
Operating band
Res.
Spare
XXIV
Res.
Res.-
XXI
XX
XIX
XVIII
XVII
Res.
Res. |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6 Summary of required changes to E-UTRA specifications | |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.1 Required changes to 3GPP TS 36.101 | Required changes in 3GPP TS 36.101 [7] are shown in Table 6.1-1.
Table 6.1-1: Required Changes for 3GPP TS 36.101 [7]
Clause
Description
Description of change
Proposed changes
5.5
Operating bands
Add a new row for the band into Table 5.5-1.
R4-102509
5.6.1
Channel bandwidths per operating band
Add channel bandwidths 5 and 10 MHz for the band into Table 5.6.1-1.
R4-103452
5.7.3
Carrier frequency and EARFCN
Add a new channel numbering for the band into Table 5.7.3-1.
R4-102509
5.7.4
TX–RX frequency separation
Add a new row for the band into Table 5.7.4-1.
R4-102509
6.2.2
UE Maximum Output Power
Add a new row for the band into Table 6.2.2-1.
R4-103452
6.2.4
UE Maximum Output Power with additional requirements
(FFS) Add a new row for the band into Table 6.2.4-1.
R4-103452
6.6.2.2
Additional Spectrum Emission Mask
(FFS) Add new requirements for the band.
R4-103452
6.6.3.2
Spurious emission band UE co-existence
Add the band into Table 6.6.3.2-1 for mutual protection with E-UTRA Band 2, 4, 5, 10, 12, 13, 14 and 17.
R4-103452
6.6.3.3
Additional spurious emissions
(FFS) Add new requirements for the band.
R4-103452
7.3
Reference sensitivity power level
Add a new row for the band into Tables 7.3.1-1, 7.3.1-2, 7.3.2-1 and, when deems necessary, 7.3.1-3.
R4-103452
7.6.1
In-band blocking
Add the band into Table 7.6.1.1-2.
R4-103452
7.6.2
Out-of-band blocking
Add the band into Table 7.6.2.1-2.
R4-103452 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.2 Required changes to 3GPP TS 36.104 | Required changes in 3GPP TS 36.104 [8] are shown in Table 6.2-1.
Table 6.2-1: Required Changes for 3GPP TS 36.104 [8]
Clause
Description
Description of change
Proposed changes
5.5
Operating bands
Add a new row for the band into Table 5.5-1.
R4-102509
5.7.3
Carrier frequency and EARFCN
Add new channel numbers for the band into Table 5.7.3-1.
R4-102509
6.6.3
Operating band unwanted emissions
Add the band to Category A.
R4-103353
6.6.4.3
Additional spurious emissions requirements
Add a new row for the band into Tables 6.6.4.3.1-1 and 6.6.4.3-1x.
R4-103353
6.6.4.4
Co-location with other base stations
Add a new row for the band into Tables 6.6.4.4.1-1 and 6.6.4.4.1-2.
R4-102508
7.6.1
General blocking requirement
Add the band into Tables 7.6.1.1-1, 7.6.1.1-1a, and 7.6.1.1-1b.
R4-102508
7.6.2
Co-location with other base stations
Add a new row for the band into Tables 7.6.2.1-1 and 7.6.2.1-2.
R4-102508 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.3 Required changes to 3GPP TS 36.113 | Required changes in 3GPP TS 36.113 [9] are shown in Table 6.3-1.
Table 6.3-1: Required changes for 3GPP TS 36.113 [9]
Clause
Description
Description of change
Proposed changes
4.5.2
Receiver exclusion band
Add a new row for the band.
R4-102509 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.4 Required changes to 3GPP TS 36.124 | Required changes in 3GPP TS 36.124 [10] are shown in Table 6.4-1.
Table 6.4-1: Required changes for 3GPP TS 36.124 [10]
Clause
Description
Description of change
Proposed changes
4.4
Receiver exclusion band
Add a new row for the band.
R4-102509 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.5 Required changes to 3GPP TS 36.133 | Required changes in 3GPP TS 36.133 [11]are shown in Table 6.5-1.
Table 6.5-1: Required changes for 3GPP TS 36.133 [11]
Clause
Description
Description of change
Proposed changes
4.2.2.3
Measurements of intra-frequency E-UTRAN cells
Add the band to the band list for RSRP and SCH_RP.
R4-103619
4.2.2.4
Measurements of inter-frequency E-UTRAN cells
Add the band to the band list for RSRP and SCH_RP.
R4-103619
8.1.2.2
E-UTRAN intra frequency measurements
Add the band to the band list for SCH_RP.
R4-103619
8.1.2.3
E-UTRAN inter frequency measurements
Add the band to the band list for RSRP and SCH_RP.
R4-103619
8.1.2.5
E-UTRAN OTDOA Intra-Frequency RSTD Measurements
Add the band to the band list for PRP.
R4-103619
8.1.2.6
E-UTRAN Inter-Frequency OTDOA Measurements
Add the band to the band list for PRP.
R4-103619
9.1.2
Intra-frequency RSRP Accuracy Requirements
Add the band to the band list for RSRP.
R4-103619
9.1.3
Inter-frequency RSRP Accuracy Requirements
Add the band to the band list for RSRP.
R4-103619
9.1.5
Intra-frequency RSRQ Accuracy Requirements
Add the band to the band list for RSRP.
R4-103619
9.1.6
Inter-frequency RSRQ Accuracy Requirements
Add the band to the band list for RSRP.
R4-103619
9.1.9
UE Rx – Tx time difference
Add the band to the band list for RSRP.
R4-103619
9.1.10
Reference Signal Time Difference (RSTD)
Add the band to the band list for PRP.
R4-103619
A.9.1.1
(RSRP) FDD Intra frequency case
Add the band to the band list for Noc, RSRP, and Io.
R4-103619
A.9.1.3
(RSRP) FDD—FDD Inter frequency case
Add the band to the band list for Noc, RSRP, and Io.
R4-103619
A.9.2.1
(RSRQ) FDD Intra frequency case
Add the band to the band list for Noc, RSRP, RSRQ, and Io.
R4-103619
A.9.2.3
(RSRQ) FDD—FDD Inter frequency case
Add the band to the band list for Noc, RSRP, RSRQ, and Io.
R4-103619 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.6 Required changes to 3GPP TS 36.141 | Required changes in 3GPP TS 36.141 [12] are shown in Table 6.6-1.
Table 6.6-1: Required Changes for 3GPP TS 36.141 [12]
Clause
Description
Description of change
Proposed changes
5.5
Operating bands
Add a new row for the band into Table 5.5-1.
R4-102509
5.7.3
Carrier frequency and EARFCN
Add new channel numbers for the band into Table 5.7.3-1.
R4-102509
6.6.3
Operating band unwanted emissions
Add the band to Category A.
R4-102508
6.6.4.5.4
Co-existence with other systems in the same geographical area
Add a new row for the band into Tables 6.6.4.5.4.1-1 and 6.6.4.5.4-1x.
R4-102508
6.6.4.5.5
Co-location with other base stations
Add a new row for the band into Tables 6.6.4.5.5-1 and 6.6.4.5.5-2.
R4-102508
7.6.5.1
(Blocking) General requirement
Add the band into Tables 7.6-1, 7.6-1a and 7.6-1x.
R4-102508
7.6.5.2
Co-location with other base stations
Add a new row for the band into Table 7.6-3 and 7.6-4.
R4-102508 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.7 Required changes to 3GPP TS 36.307 | Required changes in 3GPP TS 36.307 [13] are shown in Table 6.7-1.
Table 6.7-1: Required Changes for 3GPP TS 36.307 [13]
Clause
Description
Description of change
Proposed Changes
New clause
Band 24 Independent of Release
Add a new clause to specify the extra requirements for UE conforming to earlier releases to support this band.
R4-103241 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.8 Required changes to 3GPP TS 25.461 | Required changes in 3GPP TS 25.461 [14] are shown in Table 6.8-1.
Table 6.8-1: Required changes for 3GPP TS 25.461 [14]
Clause
Description
Description of change
Proposed Changes
4.3.7
Operating bands
Add a new row for the band in Table 4.3.7.1.
R4-103240 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.9 Required changes to 3GPP TS 25.466 | Required changes in 3GPP TS 25.466 [15] are shown in Table 6.9-1.
Table 6.9-1: Required changes for 3GPP TS 25.466 [15]
Clause
Description
Description of change
Proposed Changes
Annex B
Assigned fields for additional data
Add an entry for the band in Table B.2-1.
R4-103240 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.10 Required changes to 3GPP TS 25.101 | Required changes in 3GPP TS 25.101 [16] are shown in Table 6.10-1.
Table 6.10-1: Required Changes for 3GPP TS 25.101 [16]
Clause
Description
Description of change
Proposed Changes
6.6.3
Spurious emissions
Add the band DL frequency range into Tables 6.13 and 6.13A for UTRA Band II, IV, V, X, XII, XIII and XIV.
R4-104674 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.11 Required changes to 3GPP TS 25.104 | Required changes in 3GPP TS 25.104 [17] are shown in Table 6.11-1.
Table 6.11-1: Required Changes for 3GPP TS 25.104 [17]
Clause
Description
Description of change
Proposed Changes
6.6.3.3
Co-existence with other systems in the same geographical area
Add a new row for the band into Table 6.11.
R4-104052
6.6.3.4
Co-existence with co-located and co-sited base stations
Add a new row for the band into Tables 6.12 and 6.14.
R4-104052
6.6.3.9
Co-existence with Home BS operating in other bands
Add a new row for the band into Tables 6.20.
R4-104052
7.5.2
Minimum Requirement - Co-location with GSM900, DCS 1800, PCS1900, GSM850, UTRA FDD and/or E-UTRA FDD
Add a new row for the band into Tables 7.5C and 7.5E.
R4-104052 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.12 Required changes to 3GPP TS 25.141 | Required changes in 3GPP TS 25.141 [18] are shown in Table 6.12-1.
Table 6.12-1: Required Changes for 3GPP TS 25.141 [18]
Clause
Description
Description of change
Proposed Changes
6.5.3.7.4
Co-existence with other systems in the same geographical area
Add a new row for the band into Table 6.38.
R4-104053
6.5.3.7.5
Co-existence with co-located and co-sited base stations
Add a new row for the band into Tables 6.39 and 6.41.
R4-104053
6.5.3.7.10
Co-existence with Home BS operating in other bands
Add a new row for the band into Tables 6.47.
R4-104053
7.5.5
Blocking characteristics - Test Requirements
Add a new row for the band into Tables 7.4N and 7.4Q.
R4-104053 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.13 Required changes to 3GPP TS 37.104 | Required changes in 3GPP TS 37.104 [19] are shown in Table 6.13-1.
Table 6.13-1: Required Changes for 3GPP TS 37.104 [19]
Clause
Description
Description of change
Proposed Changes
6.6.1.3
Additional spurious emissions requirements
Add a new row for the band into Table 6.6.1.3.1-1.
R4-104054
6.6.1.4
Co-existence with co-located and co-sited base stations
Add a new row for the band into Table 6.6.1.4.1-1.
R4-104054
7.5.2
Co-location minimum requirement
Add a new row for the band into Table 7.5.2-1.
R4-104054 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.14 Required changes to 3GPP TS 37.141 | Required changes in 3GPP TS 37.141 [20] are shown in Table 6.14-1.
Table 6.14-1: Required Changes for 3GPP TS 37.141 [20]
Clause
Description
Description of change
Proposed Changes
6.6.1.5.5
Additional spurious emission requirements
Add a new row for the band into Table 6.6.1.5.5-1.
R4-104055
6.6.1.5.6
Co-location with other Base Stations
Add a new row for the band into Table 6.6.1.5.6-1.
R4-104055
7.5.5.2
Co-location test requirements
Add a new row for the band into Table 7.5.5.2-1.
R4-104055 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 7 Project plan | |
41f4dd01af106b6509f05176f478e52b | 36.813 | 7.1 Schedule and Work Task Status | The schedule and work task status for this work item are summarized in Table 7.1-1 below.
Table 7.1-1 Schedule and Work Task Status
RAN4 Meeting and Date
Work Tasks
Status
RAN4#55 (April 2010)
TR Skeleton
Approved
Summary of required changes to E-UTRA specifications
Approved
Band and channel arrangement
Approved
RAN4 Ad-hoc#3 (June 2010)
Work plan
Approved
Task description and regulatory background
Approved
Discussion on specific BS RF requirements
Approved
Discussion on specific UE RF requirements (maximum output power with additional requirements, spurious emissions, reference sensitivity power level, blocking characteristics)
Approved
Agreement on band and channel arrangement
Approved
RAN4#56 (August 2010)
Agreement on specific BS RF requirements
Approved
Continue discussion on specific UE RF requirements
Approved
RAN4 Ad-hoc#4 (October 2010)
Agreement on specific UE RF requirements
Approved
Draft CRs for review and comment
Approved
RAN4#57 (November 2010)
Final TR
Approved
Final CRs
Approved |
41f4dd01af106b6509f05176f478e52b | 36.813 | 8 Open issues | None as of December, 2010.
Annex A (informative):
Configuration Example
This section provides one example of how a practical L-Band eNodeB may be configured. The example uses the following parameters: Two 10 MHz LTE carriers in a given sector.
● Centre frequency of Carrier-1: 1526-1536MHz
◦ ○ Channel Power : 20Watt +20watts (2Tx )
◦ ○ Power of Carrier-1: Maximum 32 dBW
● Centre frequency of Carrier-2: 1545.2-1555.2 MHz
◦ ○ Channel Power : 20Watt + 20watts (2Tx)
◦ ○ Power of Carrier-2: Maximum 32 dBW
● Peak antenna gain: 16 dBi
● Cable Loss: 0.5-2 dB
The emission mask and the actual BTS power spectral density measured at the antenna connector is shown below in Figure A.1
Figure A.1: BTS PSD measured at the antenna connector (LTE 2*10 MHz)
It is noteworthy that this is no more than an example. It is technically feasible to deploy at other centre frequencies anywhere in the L-band (subject to coordination with other satellite operators such as Inmarsat), at other BTS power levels, with other types of filters offering greater selectivity, and with other antenna gains.
While it is acknowledged that meeting the GPS emission level gets more demanding as one gets closer to the upper edge of the band (1559 MHz), several deployment options exist that make it feasible to use frequencies up to 1559 MHz for ATC. These include the following:
● Reducing the BTS power level (e.g. use for microcells)
● Using a post-selector filter per carrier – the above example uses a single (band-wide) filter to cover both carriers
● Use a bulkier filter with more elements – the present filter was designed for use on remote radio heads
● Use lower antenna gain
Annex B (informative):
Change history
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
2010-05
RAN4 #55
R4-102213
TR skeleton created from 3GPP TS template.
0.0.1
2010-06
RAN4 AH #3
R4-102590
TR updated to include L-Band description of changes to specifications; addition of TS 36.307
0.0.1
0.0.2
2010-08
RAN4 #56
R4-103402
TR updated to include changes to sections 4.2, 5.1, 5.3, 6.7, 7.1, and 8
0.0.2
0.1.0
2010-08
RAN4 #56
R4-103430
TR updated to include changes to sections 4.1, 4.2, 5.1.5, 5.3, 6.2, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, and 7.1
0.1.0
0.2.0
2010-08
RAN4 #56
R4-103453
TR updated to include changes to sections 5.2, 6.1, 6.2, 7.1, and 8
0.2.0
0.3.0
2010-08
RAN4 #56
R4-103462
TR corrects Band 24 parameter references in the tables listed in section 5.2.1, and removes operator references in section 5.2.3 and section 8
0.3.0
0.3.1
2010-09
RAN #49
RP-100995
TR updated to v1.0.0 based on completion status.
0.3.1
1.0.0
2010-11
RAN4 #57
R4-104678
TR updated to include changes in section 2, 3.1, 4, 5.1.5, 5.2.3, 5.3.1, 5.3.2, 5.3.3, 5.3.4, 6.5, 6.10, 6.11, 6.12, 6.13. 6.14, 7.1, 8, and removed brackets for Band [24] references and parameters throughout the TR
1.0.0
1.1.0
2010-11
RAN4 #57
R4-104970
TR updated to include changes in sections: 5.1.5, 5.3.2, 5.3.6.2, 7.1, and 9
1.1.0
1.2.0
2010-12
RAN #50
RP-10285
TR updated to v2.0.0 based on completion status and presented to RAN for approval
1.2.0
2.0.0
2010-12
RAN #50
RP-10285
TR Approved
2.0.0
10.0.0
2011-04
RP-51
RP-110118
002
1
Overload Characteristics of GPS Receivers in Proximity to LTE L-band Terrestrial Base Stations (BTS)
10.0.0
10.1.0 |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 1 Scope | The present document contains the up-to-date SA5 Work Item Descriptions (WIDs) and captures the status of all SA5 work items in the current Release.
This TR is used as a mean to provide input to the 3GPP work plan handled by MCC. |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 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. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] http://www.3gpp.org/ftp/Information/WORK_PLAN/
[2] http://www.3gpp.org/ftp/Information/WI_Sheet/ |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 3 Feature: Enhanced Home NodeB / eNodeB UID_400035 | |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 3.1 BB: 3G Home NodeB Gateway OAM&P (HNB-OAM_GW) UID_420035 | Technical Specification Group Services and System Aspects TSGS#42(08)0794
Meeting #42, 8 - 11 December 2008,
Athens, Greece
Technical Specification Group Services and System Aspects TSGS#47(10)0087
Meeting #47; Vienna, Austria; 22-25 March 2010
3GPP TSG-SA5 (Telecom Management) S5-100889
Meeting SA5#70, 1-5 Mar 2010, Xiamen, P.R. China revision of S5-100786
Source: China Mobile
Title: Update HNB-OAM_GW WID in R9
Document for: Approval
Agenda Item: 6.2
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900.
3G HNB GW and LTE HeNB GW OAM&P HNB-OAM_GW UID_420036 |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 1 3GPP Work Area * | X
Radio Access
X
Core Network
Services |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 2 Classification of WI and linked work items | |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 2.0 Primary classification * | This work item is a … *
Study Item (go to 2.1)
Feature (go to 2.2)
Building Block (go to 2.3)
X
Work Task (go to 2.4) |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 2.1 Study Item | Related Work Item(s) (if any]
Unique ID
Title
Nature of relationship
Go to §3. |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 2.2 Feature | Related Study Item or Feature (if any)
Unique ID
Title
Nature of relationship
Go to §3. |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 2.3 Building Block | Parent Feature (or Study Item)
Unique ID
Title
TS
This work item is …
X
Stage 1 (go to 2.3.1)
X
Stage 2 (go to 2.3.2)
X
Stage 3 (go to 2.3.3)
Test spec (go to 2.3.4)
Other (go to 2.3.5)
2.3.1 Stage 1
Source of external requirements (if any)
Organization
Document
Remarks
none
Go to §3.
2.3.2 Stage 2
Corresponding stage 1 work item
Unique ID
Title
TS
[this WI]
[this WI]
Other source of stage 1 information
TS or CR(s)
Clause
Remarks
None
If no identified source of stage 1 information, justify:
Go to §3.
2.3.3 Stage 3
Corresponding stage 2 work item (if any)
Unique ID
Title
TS
[this WI]
[this WI]
Else, corresponding stage 1 work item
Unique ID
Title
TS
None
Other justification
TS or CR(s)
Or external document
Clause
Remarks
None
If no identified source of stage 2 information, justify:
Go to §3.
2.3.4 Test spec
Related Work Item(s)
Unique ID
Title
TS
Go to §3.
2.3.5 Other
Related Work Item(s)
Unique ID
Title
Nature of relationship
TS / TR
Go to §3.
2.4 Work task
Parent Building Block
Unique ID
Title
TS |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 3 Justification * | The target of SON is to maintain network quality and performance with a minimum of manual intervention from the operator.
Self-optimization functionality will monitor and analyse performance management data, and will automatically trigger optimization action on the affected network node(s) when necessary. This will significantly reduce manual interventions and replace them with automatically triggered re-optimizations, re-configurations, or software reloads/upgrades thereby helping to reduce operating expense.
The ongoing work in TSG RAN on SON for RRM also requires OAM support.
As a consequence the scope of SON self optimization also includes:
Load balancing
Handover Parameter optimization
Interference control
Capacity and coverage optimization
RACH optimization |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 4 Objective * | Collect and document Self-Optimization OAM requirements for SON.
Define in cooperation with RAN WGs inputs to and outputs from the Self-Optimization Entity, its location in the management architecture, and the degree of standardisation of the associated algorithms.
Identify and document required Self-Optimization related additions to the affected specifications.
Ensure that the OAM specifications support load balancing, HandOver (HO) parameter optimization, interference control, capacity and coverage optimization and RACH optimization.
Based on the above, a set of new TSs should capture the "SON Self-Optimization OAM Requirements". Some existing specifications (i.e., NRM, PM, etc.) may need some modification according to the output of the work task. |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 5 Service Aspects | None |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 6 MMI-Aspects | None |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 7 Charging Aspects | None |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 8 Security Aspects | None |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 9 Impacts * | Affects:
UICC apps
ME
AN
CN
Others
Yes
X
X
No
X
X
Don't know
X |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 10 Expected Output and Time scale * | New specifications *
[If Study Item, one TR is anticipated]
Spec No.
Title
Prime rsp. WG
2ndary rsp. WG(s)
Presented for information at plenary#
Approved at plenary#
Comments
32.521
Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP): Requirements
SA5
SA#44 Jun 2009
SA#47 Mar 2010
32.522
Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)
SA5
SA#47 Mar 2010
SA#47 Mar 2010
32.523
Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
SA5
SA#47 Jun 2010
SA#47 Jun 2010
32.525
Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition
SA5
SA#48 Jun 2010
SA#48 Jun 2010
Affected existing specifications *
[None in the case of Study Items]
Spec No.
CR
Subject
Approved at plenary#
Comments
32.425
Addition of measurements for SON
SA#48 Jun 2010
11 Work item rapporteur(s) *
Huawei Technologies (zlan@huawei.com)
12 Work item leadership *
SA5
13 Supporting Individual Members *
3GPP TSG-SA5 (Telecom Management) S5-100311
Meeting SA5#69, 18 – 22 January 2010, Valencia, SPAIN
TSG SA Meeting #46 SP-090869
07 - 10 December 2009,
Sanya, China
TSG SA Meeting #44 SP-090317
01 - 04 June 2009,
Oranjestad, Aruba
3GPP TSG-SA5 (Telecom Management) S5-092066
Meeting #64 March 30 - April 3, 2009, Hangzhou, CHINA
Source: Nokia Siemens Networks, Orange, Telefonica
Title: New WT-level WID on Automatic Radio Network Configuration Data Preparation (AURANCODAP)
Document for: Approval
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900.
Automatic Radio Network Configuration Data Preparation - OAM9 – UID_440067 |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 10 Expected Output and Time scale | New specifications
[If Study Item, one TR is anticipated]
Spec No.
Title
Prime rsp. WG
2ndary rsp. WG(s)
Presented for information at plenary#
Approved at plenary#
Comments
32.507
Self Configuration of Network Elements Integration Reference Point (IRP): SOAP Solution Set (SS) (Release 9)
SA#47 Mar 2010
SA#47 Mar 2010
Affected existing specifications
[None in the case of Study Items]
Spec No.
CR
Subject
Approved at plenary#
Comments
32.501
SA#47 Mar 2010
Self-Configuration of Network Elements; Concepts and IRP Requirements
32.502
SA#48 Jun 2010
Self-Configuration of Network Elements IRP; Information Service
32.503
SA#48 Jun 2010
Self-Configuration of Network Elements IRP; CORBA Solution Set
32.505
SA#48 Jun 2010
Self-Configuration of Network Elements IRP: XML file format definition
11 Work item rapporteur(s)
Clemens Suerbaum, Nokia Siemens Networks, clemens.suerbaum@nsn.com
12 Work item leadership
SA5
13 Supporting Individual Members
Supporting IM name
Nokia Siemens Networks
Orange
Telefonica
Ericsson
Huawei
Alcatel-Lucent
T-Mobile
Vodafone |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 4 Multi-Media Telephony Service enhancements UID_400032 | Technical Specification Group Services and System Aspects TSGS#43(09)0051
Meeting #43, 9 - 12 March 2009, Biarritz, France
3GPP TSG-SA5 (Telecom Management) S5-091540
Meeting SA5#63, 16-20 February 2009, Prague, CZ revision of S5-091174
Source: SA5 (Telecom Management)
Title: New WID on Multimedia Telephony Service and Supplementary Services : (MMTel) Online Charging and completion for Offline Charging (all supplementary services)
Document for: Approval
Agenda Item: 7.02
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900.
Multimedia Telephony (MMTel) Service and Supplementary Services - Online Charging and completion for Offline Charging (all supplementary services) UID_430031 |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 5 User Data Convergence | TSG SA Meeting #44 SP-090309
01 - 04 June 2009,
Oranjestad, Aruba
3GPP TSG-SA5 (Telecom Management) S5-092483
Meeting SA5#65, 11-15 May 2009, Tallinn, Estonia revision of S5-092426
Source: China Mobile, T-Mobile, Ericsson
Title: New Umbrella BB-level WID for the SA5 work on User Data Convergence - Modelling and Management
Document for: Approval
Agenda Item: 6.02
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900.
User Data Convergence - Modelling and Management (UDC-MMAN) UID_440060 |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 6 MBMS support in EPS UID_400039 | Technical Specification Group Services and System Aspects TSGS#43(09)0052
Meeting #43, 9 - 12 March 2009, Biarritz, France
3GPP TSG-SA5 (Telecom Management) S5-091541
Meeting SA5#63, 16-20 February 2009, Prague, CZ revision of S5-091309
Source: SA5 (Telecom Management)
Title: New WID on MBMS support in EPS:
MBMS Charging in EPS
Document for: Discussion and Approval
Agenda Item:
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900.
MBMS Charging in EPS UID_430033 |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 7 Feature: OAM&P 9 UID_420029 | BB: Network Infrastructure Management UID_420030
Technical Specification Group Services and System Aspects TSGS#42(08)0756
Meeting #42, 8 - 11 December 2008, Athens, Greece
3GPP TSG-SA5 (Telecom Management) S5-081836
Meeting SA5#61, 13~17 October 2008, Dalian, China (revision of S5-081557)
Source: Huawei Technologies, Nokia Siemens Network
Title: New WT-level WID on Software Management
Document for: Approval
Agenda Item: 6.2
3GPP™ Work Item Description
Title:
Management of software entities residing in Network Elements UID_420031
Acronym: OAM9-NE_SWM |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 1 3GPP Work Area | X
Radio Access
Core Network
Services |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 2.0 Primary classification | This work item is a Feature
Study Item (go to 2.1)
Feature (go to 2.2)
Building Block (go to 2.3)
X
Work Task (go to 2.4) |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 3 Justification | Self-Configuration, 3GPP TS 32.501 has a chapter 6.5.2.6 titled “Radio Configuration Data”, but its only content is “FFS”. Consequently 32.502 and 32.503 contain nothing to fulfil some of the requirements listed in clause 5.1.5.1 of TR 32.816.
When radio Network Elements (e.g. cells and/or eNBs) are inserted into an operational radio network, some network configuration parameters cannot be configured before-hand because they have interdependencies with the configuration of operational Network Elements. ”Dynamic Radio Network Configuration Data Preparation” comprises the generation and distribution of such interdependent parameters to the newly inserted network element and optionally already operational Network Elements.
This functionality is urgently needed to allow a fully automatic establishment of an eNB into a network. Otherwise a network operator would have to administer these configurations manually. Without this functionality self-configuration cannot be considered not fully as “self”. |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 4 Objective | It is proposed to work on technical solutions for Automatic Radio Network Configuration Data Preparation, i.e.:
Analyse which configuration parameter cannot be determined before-hand by the IRPAgent or by the self-configuration process and what input might be needed to generate them.
Define new functionality to trigger distribution of such parameters. This functionality should fit to the existing self-configuration functionalities and re-use existing IRPs, if possible.
The required activities to achieve these objectives may include:
Refine/define the requirements
Define the Resource model
Define operation and notifications (information service)
Define solution set/s |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 9 Impacts | Affects:
UICC apps
ME
AN
CN
Others
Yes
X
X
No
X
X
Don't know
X |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 11 Work item rapporteur(s) * | Frode Nergard (frode.nergard@ericsson.com) |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 12 Work item leadership * | SA5 |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 13 Supporting Individual Members * | Supporting IM name
Ericsson
Verizon Wireless
Alcatel-Lucent
T-Mobile
Nokia Siemens Networks
BB: Self-Organizing Networks (SON) UID_430043
Technical Specification Group Services and System Aspects TSGS#39(08)0067
Meeting #39, 10 - 13 March 2008, Puerto Vallarta, Mexico
Source: SA5 (Telecom Management)
Title: New WT-level WID on SON Self-Optimization & Self-Healing handling
Document for: Approval
Agenda Item: 10.34 (SAES) - 3GPP System Architecture Evolution Specification - Evolved Packet System (non RAN aspects)
Work Item Description
Title
SON Self-Optimization & Self-Healing handling UID_390007 - Moved from Rel-8
Acronym: LTE_SON-OAM
Technical Specification Group Services and System Aspects TSGS#47(10)0091
Meeting #47; Vienna, Austria; 22-25 March 2010
3GPP TSG-SA5 (Telecom Management) S5-101077
Meeting SA5#70, 1 Mar- 5 Mar 2010, Xiamen, China revision of S5-100956
TSG SA Meeting #46 SP-090762
07 - 10 December 2009,
Sanya, China
3GPP TSG-SA5 (Telecom Management) S5-094355
Meeting SA5#68 09-13 Nov 2009, Shanghai, China
Source: Huawei Technologies
Title: Revised WID on SON self-optimization management
Document for: Approval
Agenda Item: 6.5.1
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900.
Title * : SON Self-Optimization & Self-Healing handling
Acronym * : LTE-SON-OAM
Unique identifier * 390007 |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 8 Charging Management and Small Enhancements (CH9) UID_440068 | Technical Specification Group Services and System Aspects TSGS#47(10)0090
Meeting #47; Vienna, Austria; 22-25 March 2010
3GPP TSG-SA5 (Telecom Management) S5-101075
Meeting SA5#70, 1-5 Mar 2010, Xiamen, P.R. China revision of S5-100975
TSG SA Meeting #44 SP-090312
01 - 04 June 2009,
Oranjestad, Aruba
3GPP TSG-SA5 (Telecom Management) S5-092656
Meeting SA5#65, 11-15 May 2009, Tallinn, Estonia revision of S5-092540
Source: Orange
Title: New WID on IWLAN mobility charging
Document for: Approval
Agenda Item: 7.02
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900.
IWLAN mobility charging (eIWLAN_Mob) UID_440063 Moved to Rel-10 |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 9 Feasibility Studies | Technical Specification Group Services and System Aspects TSGS#36(07)0306
Meeting #36, 4 – 7 June 2007, Busan, KOREA
Source: SA5 (Telecom Management)
Title: WID Study of System Maintenance by Itf-N
Document for: Approval
Agenda Item: 11.28 (OAM-Study) - OAM&P Studies
3GPP TSG-SA5 (Telecom Management) S5-071006
Meeting SA5#53, 07 - 11 May 2007, Sophia Antipolis, FRANCE
Work Item Description
Title:
Study of System Maintenance over Itf-N UID_360006 - Moved from Rel-8
Acronym: FS_OAM-Maint-Itf-N
Is this Work Item a "Study Item"? (Yes / No): Yes
1 3GPP Work Area
X
Radio Access
X
Core Network
Services
2 Linked work items
OAM&P 8 (Operations, Administration, Maintenance & Provisioning) Feature: OAM8, ID 340063
3 Justification
The EMS (Element Management System) plays an important role in network management architecture.
In general, the EMS is provided by Vendors of the nodes and
Operators, using IRPManager, can manage the nodes through the EMS.
Therefore, when EMS is unavailable or down, the Operator, using IRPManager, would not be able to manage the nodes. Vendors of EMS supply proprietary interface via which the EMS itself can be managed and maintained.
Currently, the management of EMS is not standardized.
Issues to be part of this study:
1) If new 3GPP specification is required (e.g. use potentially existing industry or de facto commercial standards)
2) EMS configuration data backup and restoration
3) Time Synchronization between IRP Manager and IRP Agent
4) Resources monitoring on IRP Agent
5) Software version management of EMS
6) Should Communication Surveillance IRP, e.g. enhancement, to be included in this study
The currently existing 3GPP SA5 IRPs are mainly focused on the management of nodes such as UMTS network nodes (e.g. CM IRPs, Common IRPs, FM IRPs, PM IRP, Trace IRP).
As shown in figure1, currently there are no IRPs to support the management of EMS.
4 Objective
The EMS (e.g. IRPAgent and its associated YyyIRPs) is vital for network management in that network management activities would cease if EMS is unavailable or down. Because of its vital role, it is important that the EMS should be properly managed and maintained.
No doubt, vendors have been providing proprietary means to manage their EMS.
This study is to evaluate if some key or core EMS management functions can be standardized to support a better (most cost/effective) management paradigm in a multi-vendor network environment.
This study will focus on managing the EMS, including as examples:
1) what kind of maintenance operations can be standardized,
2) what kind of information in IRPAgent and YyyIRP shall be modelled.
3) what standard/de facto standards currently exist; comparison; benefits of having a 3GPP specified solution.
The study result can be the baseline of the maintenance of IRPAgent system and may lead to define a new interface IRP in a subsequent implementation work item.
5 Service Aspects
None
6 MMI-Aspects
None
7 Charging Aspects
None
8 Security Aspects
Not known |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 10 Expected Output and Time scale (to be updated at each plenary) | New specifications
[If Study Item, one TR is anticipated]
Spec No.
Title
Prime rsp. WG
2ndary rsp. WG(s)
Presented for information at plenary#
Approved at plenary#
Comments
TR 32.824
Study on SOA compliant need and additional capabilities for existing/currently planned Interface IRPs
SA5
SA#43 Sep 2009
SA#44 June 2009
Affected existing specifications
[None in the case of Study Items]
Spec No.
CR
Subject
Approved at plenary#
Comments
11 Work item rapporteur(s)
Edwin TSE (Ericsson)
12 Work item leadership
SA5
13 Supporting Companies
Ericsson, Huawei, Nortel, TeliaSonera, Nokia Siemens Networks
14 Classification of the WI (if known)
X
Study Item (no further information required)
Feature (go to 14a)
Building Block (go to 14b)
Work Task (go to 14c)
Technical Specification Group Services and System Aspects TSGS#41(08)0464
Meeting #41, 15 - 18 September 2008,
Kobe, Japan
Source: SA5
Title: New SID on Rc Reference Point
Document for: Approval
Agenda Item: 12.18
3GPP TSG-SA5 (Telecom Management) S5-081204
Meeting SA5#60, 7 - 11 Jul 2008, Sophia Antipolis, FRANCE
Source: Huawei, China Mobile
Title: New SID on Rc Reference Point
Document for: Approval
Agenda Item:
Study Item Description
Title
Study on Rc Reference Point Functionalities and Message Flows UID_410044 -Moved to Rel-10
Technical Specification Group Services and System Aspects TSGS#43(09)0048
Meeting #43, 9 - 12 March 2009, Biarritz, France
3GPP TSG-SA5 (Telecom Management) S5-091460
Meeting SA5#63, 16-20 February 2009, Prague, Czech Republic
Source: Alcatel-Lucent, China Mobile, Huawei, Orange, Telefonica, T-Mobile, Vodafone
Title: Proposal for a new Study Item on Energy Savings Management
Document for: Approval
Agenda Item: 6.02 – New OAM Work Item proposals
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900.
Telecommunication Management; Energy Savings Management (ESM) UID_430044-Moved to Rel-10
TSG SA Meeting #44 SP-090318
01 - 04 June 2009,
Oranjestad, Aruba
3GPP TSG-SA5 (Telecom Management) S5-092147
Meeting SA5#64, 30 Mar – 3 Apr 2009 Hangzhou, CHINA revision of S5-091xyw
Source: SA5 (Telecom Management)
Title: New SID on Study on EPC Charging enhancement
Document for: Approval
Agenda Item: 7.02
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900.
Study on EPC Charging enhancement (FS_EPCcharg) UID_440050-Moved to Rel-10
TSG SA Meeting #44 SP-090462
01 - 04 June 2009,
Oranjestad, Aruba
3GPP TSG-SA5 (Telecom Management) S5-092064
Meeting #64 March 30 - April 3, 2009, Hangzhou, CHINA
Source: Motorola, Qualcomm Europe, Vodafone, T-Mobile, Telefonica, Telecom Italy, Orange
Title: New SID on Study on User Equipment Management (UEM)
Document for: Approval
Agenda Item: 6.x
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900.
Study on Integration of device management information with Itf-N (FS_UEM) UID_440069-Moved to Rel-10
Annex A:
Status list of Work items
This list reflects work items, ongoing, completed or stopped.
400035
Enhanced Home NodeB / eNodeB
EHNB
420036
3G HNB Gateway and LTE HeNB Gateway OAM&P
HNB-OAM_GW
430012
3G HNB and LTE HeNB OAM&P Type 1 Interface
HNB_eHNB-OAM_Type1
440066
3G HNB and LTE HeNB OAM&P Type 2 Interface
HNB_eHNB-OAM_Type2
400032
Multi-Media Telephony Service enhancements
eMMTel
430031
Multimedia Telephony (MMTel) Service and Supplementary Services - Online Charging and completion for Offline Charging (all supplementary services)
eMMTel-SS-CH
430032
Support of Real-time Transfer of Tariff Information (RTTI) in IMS charging
IMSTSS-RTTI-CH
400034
User Data Convergence
UDC
440060
User Data Convergence - Modelling and Management
UDC-MMAN
440062
UDC – Framework for Model Handling and Management
UDC-MMAN-MFRM
440061
UDC – Common Baseline Information Model
UDC-MMAN-CBIM
400039
MBMS support in EPS
MBMS_EPS
430033
MBMS Charging in EPS
MBMS_EPS
420029
OAM&P 9
OAM9
420030
Network Infrastructure Management
OAM9-NIM
420031
Software Management for Network Elements
OAM9-NE_SWM
440064
Service Oriented Architecture (SOA) for IRP
OAM9
440065
IRP SOAP Solution Sets continuation from Rel-8
OAM9
420032
Performance Management
OAM9-PM
430041
Enhancement of E-UTRAN Performance Measurements
OAM9
430042
Enhancement of EPC Performance Measurements
OAM9
440059
Enhancement of UTRAN Performance Measurements
OAM9
420033
Deleted - Trace
OAM9-Trace
430043
Self-Organizing Networks (SON) - OAM aspects
OAM9-SON
390007
SON self-optimization management
LTE_SON-OAM
440067
Automatic Radio Network Configuration Data Preparation
OAM9
440058
Subscription Management (SuM) evolution
OAM9-SuM
440068
Charging Management small Enhancements
CH9
360006
Study on System Maintenance over Itf-N
FS_OAM-Maint-Itf-N
360007
Study on Self-Organizing Networks (SON) related OAM interfaces for Home NodeB
FS_OAM-SON-HNB
390017
Study on Self-healing of Self-Organizing Networks (SON)
FS_OAM-SON-SH
400029
Study on Service Oriented Architecture (SOA) for IRP
FS_OAM_SOA_IRP
Annex B:
Change history
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
2010-09
SA#49
SP-100525
--
--
Presentation to SA for Information and Approval
---
1.0.0
2010-10
--
--
--
--
Publication
1.0.0
9.0.0 |
8a916e998185fce27065b78e6b079636 | 32.535 | 32.531 Telecommunication management; Software management; Concepts and Integration Reference Point (IRP) Requirements | |
8a916e998185fce27065b78e6b079636 | 32.535 | 32.532 Telecommunication management; Software management Integration Reference Point (IRP); Information Service (IS) | |
8a916e998185fce27065b78e6b079636 | 32.535 | 32.533 Telecommunication management; Software management Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | |
8a916e998185fce27065b78e6b079636 | 32.535 | 32.535 Telecommunication management; Software management Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions | Software Management, in general, provides the operator with the ability to manage effectively the software entities residing in the 3G network. Software Management function is useful especially when there is a need to manage a large number of software residing in the managed elements widely distributed geographically. The main focus is the management of new software releases and correction patches [1].
The software management operations are initiated by the operator or by functions in the Operations Systems (OSs) either on single NE or across several NEs of the 3G network. |
8a916e998185fce27065b78e6b079636 | 32.535 | 1 Scope | The present document provides the XML file format definition for the Software Management Integration Reference Point (IRP) IS [3] V9.2.X.
The present document specifies the XML Definitions for the Software Management Integration Reference Point (IRP) as it applies to Itf-N, in accordance with Software Management IRP IS definitions [3] as well as Notification Log IRP XML Definitions [4]. |
8a916e998185fce27065b78e6b079636 | 32.535 | 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. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements”.
[2] 3GPP TS 32.102: “Telecommunication management; Architecture”.
[3] 3GPP TS 32.532: “Telecommunication management; Software management Integration Reference Point (IRP); Information Service (IS)”
[4] 3GPP TS 32.335: “Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): eXtensible Markup Language (XML) solution definitions”.
[5] 3GPP TS 32.331: “Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Requirements”. |
8a916e998185fce27065b78e6b079636 | 32.535 | 3 Definitions and abbreviations | |
8a916e998185fce27065b78e6b079636 | 32.535 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], and 3GPP TS 32.331 [5] apply. |
8a916e998185fce27065b78e6b079636 | 32.535 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply:
IRP Integration Reference Point
IS Information Service
NL Notification Log
NRM Network Resource Model
SwM Software Management
UML Unified Modelling Language
XML eXtensible Markup Language |
8a916e998185fce27065b78e6b079636 | 32.535 | 4 Software Management IRP XML Definitions | |
8a916e998185fce27065b78e6b079636 | 32.535 | 4.1 Software Management IRP XML Definitions | This section provides XML definitions of Software Management IRP IOCs and notifications as defined in [3].
4.2 XML Schema for Software Management IRP Notifications (file name “swManagementIRPNotif.xsd”)
<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xe="http://www.3gpp.org/ftp/specs/archive/32_series/32.305#notification" xmlns:xswm="http://www.3gpp.org/ftp/specs/archive/32_series/32.535#swManagementIRPNotif" xmlns:xswmi="http://www.3gpp.org/ftp/specs/archive/32_series/32.535#swManagementIRPIOCs" targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.535#swManagementIRPNotif" elementFormDefault="qualified" attributeFormDefault="unqualified">
<import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.305#notification"/>
<import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.535#swManagementIRPIOCs"/>
<simpleType name="SwVersionToBeInstalledConditional">
<restriction base="string"/>
</simpleType>
<complexType name="OfferedFinalAdministrativeStateInformation">
<sequence>
<element name="OfferedFinalAdministrativeStateValue" type="xswmi:FinalAdministrativeStateValue" maxOccurs="3"/>
</sequence>
</complexType>
<simpleType name="TriggerForDeletion">
<restriction base="string">
<enumeration value="IRP_AGENT_TERMINATION"/>
<enumeration value="IRP_MANAGER_TERMINATION"/>
<enumeration value="AUTOMATED_SWM_SUCCESFULLY_CONCLUDED"/>
<enumeration value="SELF_CONFIGURATION_SUCCESFULLY_CONCLUDED"/>
</restriction>
</simpleType>
<simpleType name="RequestID">
<restriction base="unsignedLong"/>
</simpleType>
<simpleType name="DownloadNESwOperationStatus">
<restriction base="string">
<enumeration value="NE_SWDOWNLOAD_SUCCESSFUL"/>
<enumeration value="NE_SWDOWNLOAD_FAILED"/>
<enumeration value="NE_SWDOWNLOAD_PARTIALLY_SUCCESSFUL"/>
</restriction>
</simpleType>
<simpleType name="FileLocation">
<restriction base="string"/>
</simpleType>
<complexType name="NESwInfo">
<sequence>
<element name="fileLocation" type="xswm:FileLocation" maxOccurs="unbounded"/>
</sequence>
</complexType>
<complexType name="FailedSwEntry">
<sequence>
<element name="failedSw" type="xswm:FileLocation"/>
<element name="failureReason" type="xswm:FailureReason"/>
</sequence>
</complexType>
<complexType name="FailedSwInfo">
<sequence>
<element name="failedSwEntry" type="xswm:FailedSwEntry" maxOccurs="unbounded"/>
</sequence>
</complexType>
<simpleType name="FailureReason">
<restriction base="string"/>
</simpleType>
<simpleType name="InstallNESwOperationStatus">
<restriction base="string">
<enumeration value="NE_SW_INSTALLATION_SUCCESSFUL"/>
<enumeration value="NE_SW_INSTALLATION_FAILED"/>
<enumeration value="NE_SWINSTALLATION_PARTIALLY_SUCCESSFUL"/>
</restriction>
</simpleType>
<simpleType name="ActivateNESwOperationStatus">
<restriction base="string">
<enumeration value="NE_SW_ACTIVATION_SUCCESSFUL"/>
<enumeration value="NE_SW_ACTIVATION_FAILED"/>
<enumeration value="NE_SWACTIVATION_PARTIALLY_SUCCESSFUL"/>
</restriction>
</simpleType>
<complexType name="NotifySwMProfileChange">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="versionNumber" type="xswmi:VersionNumber"/>
<element name="nEInformation" type="xswmi:NEInformation"/>
<element name="swVersionToBeInstalled" type="xswm:SwVersionToBeInstalledConditional"/>
<element name="stepsAndSelectedStopPointList">
<complexType>
<complexContent>
<extension base="xswmi:StepsAndSelectedStopPointList"/>
</complexContent>
</complexType>
</element>
<element name="selectedFinalAdministrativeState" type="xswmi:FinalAdministrativeStateValue"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifyNewSwAvailability">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="nEandSWversion" type="string"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifySwMProcessDeletion">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="triggerForDeletion" type="xswm:TriggerForDeletion"/>
<element name="additionalInformation" type="string" minOccurs="0"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifySwMProcessStage">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="stepInfoList" type="xswmi:StepInfoList"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifySwMProcessCreation">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="nEIdentification" type="xswmi:Id"/>
<element name="profileId" type="xswmi:ProfileId"/>
<element name="matchingNEInformation" type="xswmi:NEInformation"/>
<element name="stepInfoList" type="xswmi:StepInfoList"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifySwMProfileDeletion">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="id" type="xswmi:Id"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifySwMProfileCreation">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="versionNumber" type="xswmi:VersionNumber"/>
<element name="nEInformation" type="xswmi:NEInformation"/>
<element name="swVersionToBeInstalled" type="xswm:SwVersionToBeInstalledConditional"/>
<element name="stepsAndSelectedStopPointList">
<complexType>
<complexContent>
<extension base="xswmi:StepsAndSelectedStopPointList"/>
</complexContent>
</complexType>
</element>
<element name="selectedFinalAdministrativeState" type="xswmi:FinalAdministrativeStateValue"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifyDownloadNESwStatusChanged">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="downloadProcessId" type="xswm:RequestID"/>
<element name="downloadOperationStatus" type="xswm:DownloadNESwOperationStatus"/>
<element name="downloadedNESwInfo" type="xswm:NESwInfo" minOccurs="0"/>
<element name="failedSwInfo" type="xswm:FailedSwInfo" minOccurs="0"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifyInstallNESwStatusChanged">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="installProcessId" type="xswm:RequestID"/>
<element name="installOperationStatus" type="xswm:InstallNESwOperationStatus"/>
<element name="installedNESwInfo" type="xswm:NESwInfo" minOccurs="0"/>
<element name="failedSwInfo" type="xswm:FailedSwInfo" minOccurs="0"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifyActivateNESwStatusChanged">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="activateProcessId" type="xswm:RequestID"/>
<element name="activateOperationStatus" type="xswm:ActivateNESwOperationStatus"/>
<element name="swVersionActivated" type="string" minOccurs="0"/>
<element name="failureReason" type="xswm:FailureReason" minOccurs="0"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="NotifySwMProfileCreation" type="xswm:NotifySwMProfileCreation"/>
<element name="NotifySwMProfileDeletion" type="xswm:NotifySwMProfileDeletion"/>
<element name="NotifySwMProcessCreation" type="xswm:NotifySwMProcessCreation"/>
<element name="NotifySwMProcessStage" type="xswm:NotifySwMProcessStage"/>
<element name="NotifySwMProcessDeletion" type="xswm:NotifySwMProcessDeletion"/>
<element name="NotifyNewSwAvailability" type="xswm:NotifyNewSwAvailability"/>
<element name="NotifySwMProfileChange" type="xswm:NotifySwMProfileChange"/>
<element name="NotifyDownloadNESwStatusChanged" type="xswm:NotifyDownloadNESwStatusChanged"/>
<element name="NotifyActivateNESwStatusChanged" type="xswm:NotifyActivateNESwStatusChanged"/>
<element name="NotifyInstallNESwStatusChanged" type="xswm:NotifyInstallNESwStatusChanged"/>
</schema>
4.3 XML Schema for Software Management IRP IOCs (file name “swManagementIRPIOCs.xsd”)
<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xswmi="http://www.3gpp.org/ftp/specs/archive/32_series/32.535#swManagementIRPIOCs" xmlns:xn="http://www.3gpp.org/ftp/specs/archive/32_series/32.625#genericNrm" targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.535#swManagementIRPIOCs" elementFormDefault="qualified" attributeFormDefault="unqualified">
<import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.625#genericNrm" schemaLocation="genericNrm.xsd"/>
<simpleType name="NEInformation">
<restriction base="string"/>
</simpleType>
<simpleType name="Id">
<restriction base="xn:dn"/>
</simpleType>
<simpleType name="VersionNumber">
<restriction base="unsignedShort"/>
</simpleType>
<complexType name="ProfileId">
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="versionNumber" type="xswmi:VersionNumber"/>
</sequence>
</complexType>
<simpleType name="FinalAdministrativeStateValue">
<restriction base="string">
<enumeration value="LOCKED"/>
<enumeration value="UNLOCKED"/>
<enumeration value="DETERMINED_BY_CONFIGURATION_DATA"/>
</restriction>
</simpleType>
<complexType name="OfferedFinalAdministrativeStateInformation">
<sequence>
<element name="OfferedFinalAdministrativeStateValue" type="xswmi:FinalAdministrativeStateValue" maxOccurs="3"/>
</sequence>
</complexType>
<complexType name="StepsAndOfferedStopPointListEntry">
<sequence>
<element name="nameOfStep" type="xswmi:NameOfStep"/>
<element name="sequenceNumberInProcess" type="xswmi:SequenceNumberInProcess"/>
<element name="stopPointCanBeSetBeforeThisStep" type="xswmi:StopPointCanBeSetBeforeThisStep"/>
</sequence>
</complexType>
<complexType name="StepsAndOfferedStopPointList">
<sequence>
<element name="stepsAndOfferedStopPointListEntry" type="xswmi:StepsAndOfferedStopPointListEntry" maxOccurs="unbounded"/>
</sequence>
</complexType>
<simpleType name="StopPointCanBeSetBeforeThisStep">
<restriction base="boolean"/>
</simpleType>
<complexType name="StepsAndSelectedStopPointListEntry">
<sequence>
<element name="nameOfStep" type="xswmi:NameOfStep"/>
<element name="sequenceNumberInProcess" type="xswmi:SequenceNumberInProcess"/>
<element name="stopPointSetIndication" type="xswmi:StopPointSetIndication"/>
</sequence>
</complexType>
<complexType name="StepsAndSelectedStopPointList">
<sequence>
<element name="stepsAndSelectedStopPointListEntry" type="xswmi:StepsAndSelectedStopPointListEntry" maxOccurs="unbounded"/>
</sequence>
</complexType>
<simpleType name="StopPointSetIndication">
<restriction base="string">
<enumeration value="STOP_POINT_IS_SET_BEFORE_THIS_STEP"/>
<enumeration value="STOP_POINT_IS_NOT_SET"/>
</restriction>
</simpleType>
<simpleType name="SequenceNumberInProcess">
<restriction base="unsignedShort"/>
</simpleType>
<simpleType name="NameOfStep">
<restriction base="string">
<enumeration value="SW_DOWNLOAD"/>
<enumeration value="SW_INSTALLATION"/>
<enumeration value="SW_ACTIVATION"/>
<enumeration value="PREPARE_BASIC_CONFIGURATION_AND_OAMLINK"/>
<enumeration value="RETRIEVE_CONFIGURATION_DATA"/>
<enumeration value="SETUP_PRECONFIGURED_SIGNALLING_LINKS"/>
<enumeration value="SET_FINAL_STATE_OF_NE "/>
</restriction>
</simpleType>
<simpleType name="StepProgress">
<restriction base="string">
<enumeration value="NOT_YET_STARTED"/>
<enumeration value="RUNNING"/>
<enumeration value="COMPLETED"/>
<enumeration value="AWAITING_RESUME"/>
<enumeration value="FAILURE"/>
<enumeration value="TERMINATED"/>
</restriction>
</simpleType>
<complexType name="StepInfoListEntry">
<sequence>
<element name="nameOfStep" type="xswmi:NameOfStep"/>
<element name="sequenceNumberInProcess" type="xswmi:SequenceNumberInProcess"/>
<element name="stopPointSetIndication" type="xswmi:StopPointSetIndication"/>
<element name="stepProgress" type="xswmi:StepProgress"/>
</sequence>
</complexType>
<complexType name="StepInfoList">
<sequence>
<element name="stepInfoListEntry" type="xswmi:StepInfoListEntry" maxOccurs="unbounded"/>
</sequence>
</complexType>
<complexType name="swMCapabilityIOC">
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="neInformation" type="xswmi:NEInformation"/>
<element name="stepsAndOfferedStopPointList" type="xswmi:StepsAndOfferedStopPointList"/>
<element name="offeredFinalAdministrativeStateInformation" type="xswmi:OfferedFinalAdministrativeStateInformation"/>
</sequence>
</complexType>
<complexType name="swMProfileIOC">
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="versionNumber" type="xswmi:VersionNumber"/>
<element name="neInformation" type="xswmi:NEInformation"/>
<element name="stepsAndSelectedStopPointList" type="xswmi:StepsAndSelectedStopPointList"/>
<element name="selectedFinalAdministrativeState" type="xswmi:FinalAdministrativeStateValue"/>
</sequence>
</complexType>
<complexType name="swMProcessIOC">
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="nEIdentification" type="xswmi:NEInformation"/>
<element name="profileId" type="xswmi:ProfileId"/>
<element name="stepInfoList" type="xswmi:StepInfoList"/>
</sequence>
</complexType>
</schema>
Annex A (informative):
Void
Annex B (informative):
Change history
Change history
Date
TSG #
TSG Doc.
CR
R
Subject/Comment
Cat
Old
New
Dec 2009
SA#46
SP-090736
--
--
Presentation to SA for Information and Approval
--
--
1.0.0
Dec 2009
--
--
--
--
Publication
--
1.0.0
8.0.0
Dec 2009
-
-
-
-
Update to Rel-9 version
--
8.0.0
9.0.0
Mar 2010
SA#47
SP-100035
0001
-
Discontinue from Rel-9 onwards the XML schema extraction and storage
F
9.0.0
9.1.0
Mar 2010
SA#47
SP-100035
0002
-
To add XML solution set for Non Automated Software Management notifications
F
9.0.0
9.1.0 |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 1 Scope | This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
The present document shall analyse the current network selection mechanism and will highlight its limitations based on known operational problems. It will also consider issues brought about by the advent of new access systems.
Potential changes shall be described to the selection mechanism to provide a better user and network operator experience.
The present document is applicable to both GERAN and UTRAN. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 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. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TS 22.011: "Service Accessibility"
[2] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station"
[3] 3GPP TS 22.234: "Requirements on 3GPP system to Wireless Local Area Network (WLAN) interworking"
[4] 3GPP TS 24.234: "3GPP System to Wireless Local Area Network (WLAN) interworking; User Equipment (UE) to network protocols" |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 3 Definitions, symbols and abbreviations | |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply.
R-UIM Removable User Identity Module (note this is a 3GPP2 term) |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply:
AP Access Point
CN Core Network
CS Circuit Switched
CSD Circuit Switched Data
FBS Full Band Scan
FPLMN Forbidden Public Land Mobile Network
HPLMN Home Public Land Mobile Network
I-WLAN Interworking WLAN
ME Mobile Equipment
OOS Out Of Service
OTA Over The Air
PLMN Public Land Mobile Network
PS Packet Switched
RAN Radio Access Network
RAT Radio Access Technology
R-UIM Removable User Identity Module
SMS Short Message Service
SN Service Network
UE User Equipment
VPLMN Visited Public Land Mobile Network
WLAN Wireless Local Area Network |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 4 Network Selection overview | The Stage 1 Requirements for Network Selection are found in TS 22.011 [1]. This describes the behaviour that is expected from a UE in order to select a PLMN from which to gain service.
Two modes of operation are supported: Automatic and Manual. At power on, and the UE is required to revert to the last mode used at power off. At any time, the user may request the UE to initiate reselection and registration onto an alternative available PLMN.
As defined in Release 6 the Automatic Mode will attempt to connect the UE to a PLMN using the following order; the RPLMN (or its EPLMNs) followed by the HPLMN followed by PLMNs indicated on the User and then the Operator controlled Preferred Lists, followed by those PLMNs with sufficient signal quality in random order, and finally those in descending order of signal strength.
The Manual Mode presents the user with a list of the networks that are available and the user then selects which network the UE should connect to in order to gain service.
In the case of the Automatic mode periodic network selection attempts may be enabled by the HPLMN to search for and connect to higher priority PLMNs if they have become available. In Release 7 the Equivalent HPLMN feature has been introduced which allows multiple PLMNs to be treated as the HPLMN and hence share the highest priority during network selection attempts.
The detailed Network Selection Procedure is contained in TS23.122 [2]
The Stage 1 Requirements for Network Selection when access is available through I-WLAN are detailed in TS 22.234 [3]. This is provides for both an automatic and a manual mode similar to that specified in TS 22.011 [1]. This introduces a number of additional priority lists, which enable Network Operators to give different preferences to PLMNs that are available via I-WLAN and also to indicate preferred WLAN ID’s in the case that it is possible to connect to the same PLMN via more than one WLAN AP.
The detailed Network Selection Procedure for I-WLAN is contained in TS 24.234 [4]. The Network Selection Procedures defined for I-WLANs are decoupled from the network selection procedures for cellular protocols specified in TS 23.122 [2], though they share some similarities. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5 High level principles | |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.1 General | This clause describes the principles that are applicable in network selection up to Rel-6 and that are not expected to be challenged by the enhancements introduced to the network selection procedures. Furthermore the expectations of the three main stakeholders in the network selection procedures (customer, home operator, visited network operator) are also described. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.2 Key principles | The following is a set of principles that should be preserved when devising a new procedure to perform the registration to the serving mobile network. The assumption made in this paragraph is that the term “network” has to be interpreted as the core network of the mobile operator with whom the subscriber has direct relation (i.e. the home PLMN) or indirect via the home PLMN (e.g. a Visited PLMN).
Principle 1: the subscriber selects and registers with a public land mobile network regardless of the radio access technology employed to attain connectivity. This is then regarded as the registered PLMN (RPLMN).
Principle 2: the home PLMN operator and the user can prioritise by means of lists the available PLMNs/Access technologies combinations for roaming. If only networks for which no priority is defined are available, then those networks with sufficient radio quality are chosen at random, then the rest are chosen in order of decreasing signal strength. Furthermore the home PLMN operator has control over the periodicity the UE attempt to register on a PLMN with higher priority than the current registered one.
Principle 3: the HPLMN and any other PLMN declared as equivalent to the HPLMN (EHPLMN) of the subscriber has by default the highest priority, however the UE shall first attempt to attain service from the last PLMN it successfully registered on (last registered PLMN or the equivalent PLMNs).
Principle 4: the PLMN has priority over the particular radio access technology that the UE may prefer to use. When the PLMN supports multiple access technologies, the UE shall use in priority preferred RAT on the USIM preferred list to attain connectivity on that PLMN. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.3 Backward compatibility | Enhancements to the network selection principles will not negatively affect the functionality of existing devices.
Enhancements to the Network Selection procedure in the core network shall be done such that backwards compatibility with existing UEs is maintained.
The network selection principles should allow for at least the following combination of entities:
- HPLMN and USIM are Rel-7: HPLMN/EHPLMN (Rel-7) - VPLMN (pre-Rel-7) - ME (pre-Rel-7) - USIM (Rel-7)
- HPLMN and ME are Rel-7: HPLMN/EHPLMN (Rel-7) - VPLMN (pre-Rel-7) - ME(Rel-7) - (U)SIM (pre-Rel-7)
- VPLMN is Pre-Rel-7: HPLMN/EHPLMN (Rel-7) - VPLMN (pre-Rel-7) - ME (Rel-7) - USIM (Rel-7)
- All the entities are Rel-7: HPLMN/EHPLMN (Rel-7) - VPLMN (Rel-7) - ME(Rel-7) - USIM (Rel-7) |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.4 Customer expectations | Following switch-on where there is no last registered PLMN, the user should be registered on non-forbidden PLMN as fast as possible (typically within 20 seconds). This period includes the execution of any 3GPP defined functionality (e.g. after any PIN verification) that is performed by the mobile device but excludes any additional functionality (e.g. operating system device initialisation).
Following switch-on if the last registered PLMN is available, and no higher priority PLMN is available (e.g. HPLMN) the user should be registered on that PLMN (typically within 5 seconds). This period includes the execution of any 3GPP defined functionality as described above.
Following switch-on if the last registered PLMN is available, and a higher priority PLMN is available (e.g. HPLMN) the user should be registered on the Highest priority PLMN available (typically within 20 seconds). This period includes the execution of any 3GPP defined functionality as described above.
If not limited by subscriptions and other commercial framework and technical feasible, roaming users should always be able to access all their services and their services shall always work correctly as if they were on the home network.
Users shall be able to choose the PLMN they wish to receive service from. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.5 Home operator expectations | The home operator's users' devices should select the home operator's preferred network and access type while roaming.
The home operator should be able to set which preferred networks are in the customer’s device. The home operator should be able to set the mix of networks and access types that can be used by each roaming user for each visited network (i.e. apply per user per country). This should include which networks are preferred in selected countries in priority order.
User preferences or manual PLMN selection may override operator preferences.
The HPLMN can direct the user to a VPLMN that is capable of providing the best possible service to match the "at home experience". However, the VPLMN needs to have over-riding control over the use of its own capabilities. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.6 Visited operator expectations | It should be possible for the visited operator to direct traffic from roamers onto the appropriate access technology to manage network capacity and loading (e.g. to use 2G for voice and 3G for high speed data services). The ability to change the access in real-time for roamers according to their usage should be possible. The visited operator should be able to choose the most appropriate access technology in order to meet the service requirements of the user subject to network conditions and availability. This should cover data rates also, for example, the visited network should be able to allocate 128kbps even though the user may usually use 384kbps. The visited operator should be able to allocate access technology and data rates on the basis of the IMSI of the inbound roamer. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.7 UICC and USIM considerations | In terms of Network Selection Procedures, the USIM contains several sets of data that are used either for automatic or manual selection:
- User controlled PLMN selector with Access Technology
- Operator controlled PLMN selector with Access Technology
- Higher Priority PLMN search period
- Forbidden PLMNs
- HPLMN selector with Access Technology
- Network Parameters
And for I-WLAN:
- User controlled PLMN selector for WLAN Access
- Operator controlled PLMN selector for WLAN Access
- User controlled WLAN Specific Identifier List
- Operator controlled WLAN Specific Identifier List |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.