hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.1 General | The performance requirements for the UE in this clause is specified for the measurement channels specified in annex C and the propagation conditions specified in annex D. Unless otherwise stated the receiver characteristics are specified at the antenna connector of the UE. For UE(s) with an integral antenna only, a reference antenna with a gain of 0 dBi is assumed. UE with an integral antenna may be taken into account by converting these power levels into field strength requirements, assuming a 0 dBi gain antenna. For UEs with more than one receiver antenna connector the fading of the signals and the AWGN signals applied to each receiver antenna connector shall be uncorrelated. The levels of the test signal applied to each of the antenna connectors shall be as defined in the respective sections below.
Table 12.1: Summary of UE performance targets
Test Chs.
Information Data Rate
Performance metric
Static
Multi-path
Case 1
Multi-path Case 3
DCH
12.2 kbps
BLER<10-2
BLER<10-2
BLER<10-2
64 kbps
BLER<10-1
BLER<10-1
BLER<10-1
All Block Error ratio (BLER) measurements in clause 12 shall be performed according to the general rules for statistical testing in Annex F.6. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.1.2 Definition of Additive White Gaussian Noise (AWGN) Interferer | The minimum bandwidth of the AWGN interferer shall be 1.5 times chip rate of the radio access mode. (e.g. 5.76 MHz for a chip rate of 3,84 Mcps). The flatness across this minimum bandwidth shall be less than 0.5 dB and the peak to average ratio at a probability of 0.001% shall exceed 10 dB. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.2 Demodulation of DCH in static propagation conditions | |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.2.1 Definition and applicability | The performance requirement of DCH in static propagation conditions is determined by the maximum Block Error Ratio (BLER ). The BLER is specified for each individual data rate of the DCH. DCH is mapped into the Dedicated Physical Channel (DPCH).
The requirements and this test apply to all types of 1.28 Mcps TDD UE of Release 11 and later. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.2.2 Minimum requirements | |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.2.2.1 3.84 Mcps TDD Option | [FFS] |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.2.2.2 1.28 Mcps TDD Option | For the parameters specified in Table 12.2.2.2a and and Table 12.2.2.2b the BLER should not exceed the piece-wise linear BLER curve specified in Table 12.2.2.2c. The reference for this requirement is TS 25.102 [1] clause 12.2.1.2.
Table 12.2.2.2a: DCH parameters in static propagation conditions (12.2 kbps)
Parameters
Unit
Test 1
Test 2
Test 3
Number of DPCHo
4
12
28
Scrambling code and basic midamble code number of SS#1*
19
19
19
Scrambling code and basic midamble code number of SS#2*
58
58
58
Scrambling code and basic midamble code number of SS#3*
85
85
85
DPCH Channelization Codes of SS#1*
C(k,Q)
C(i,16)
i=1,2
C(i,16)
i=1,2
C(i,16)
i=1,2
DPCHo Channelization Codes of SS#2*
C(k,Q)
C(i,16)
1≤ i ≤2
C(i,16)
1≤ i ≤6
C(i,16)
1≤ i ≤14
DPCHo Channelization Codes of SS#3*
C(k,Q)
C(i,16)
1≤ i ≤2
C(i,16)
1≤ i ≤6
C(i,16)
1≤ i ≤14
of SS#2
dB
10
5
0
of SS#3
dB
4
-1
-6
SFN-SFN Observed Timing Difference Type 2 between SS#1 and SS#2
chip
0
0
0
SFN-SFN Observed Timing Difference Type 2 between SS#1 and SS#3
chip
0
0
0
Power of SS#2**
dBm
-67
-67.22
-68.54
Power of SS#3**
dBm
-73
-73.22
-74.54
Ioc
dBm/1,28MHz
-80
Midamble
Default midamble (Kcell = 8)
*Note: Refer to TS 25.223 for definition of channelization codes, scrambling code and basic midamble code.
**Note: Power of SS can be calculated from and Ioc.
Table 12.2.2.2b: DCH parameters in static propagation conditions (64 kbps)
Parameters
Unit
Test 4
Test 5
Test 6
Number of DPCHo
4
12
28
Scrambling code and basic midamble code number of SS#1*
19
19
19
Scrambling code and basic midamble code number of SS#2*
58
58
58
Scrambling code and basic midamble code number of SS#3*
85
85
85
DPCH Channelization Codes of SS#1*
C(k,Q)
C(i,16)
1≤ i ≤8
C(i,16)
1≤ i ≤8
C(i,16)
1≤ i ≤8
DPCHo Channelization Codes of SS#2*
C(k,Q)
C(i,16)
1≤ i ≤2
C(i,16)
1≤ i ≤6
C(i,16)
1≤ i ≤14
DPCHo Channelization Codes of SS#3*
C(k,Q)
C(i,16)
1≤ i ≤2
C(i,16)
1≤ i ≤6
C(i,16)
1≤ i ≤14
of SS#2
dB
10
5
0
of SS#3
dB
4
-1
-6
SFN-SFN Observed Timing Difference Type 2 between SS#1 and SS#2
chip
0
0
0
SFN-SFN Observed Timing Difference Type 2 between SS#1 and SS#3
chip
0
0
0
Power of SS#2**
dBm
-67
-67.22
-68.54
Power of SS#3**
dBm
-73
-73.22
-74.54
Ioc
dBm/1,28MHz
-80
Midamble
Default midamble (Kcell = 8)
*Note: Refer to TS 25.223 for definition of channelization codes, scrambling code and basic midamble code.
**Note: Power of SS can be calculated from and Ioc.
Table 12.2.2.2c: Minimum requirements in static propagation conditions
Test Number
[dB]
BLER
1
-0.3
10-2
2
2.8
10-2
3
8.7
10-2
4
4.1
10-1
5
10.7
10-1
6
12.9
10-1 |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.2.2.3 7.68 Mcps TDD Option | [FFS] |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.2.3 Test purpose | The test purpose is to verify the ability of the receiver to receive a predefined test signal ,representing a static propagation channel for the wanted and for the co-channel signals from serving and adjacent cells, with a block error ratio (BLER) not exceeding a specified value. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.2.4 Method of test | |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.2.4.1 Initial conditions | Test environment: normal; see clauses G.2.1 and G.2.2.
Frequencies to be tested: mid range; see clause G.2.4.
1) Connect the SS, AWGN Generator and additional components to the UE antenna connector as shown in figure A.19.
2) A call is set up according to the Generic call setup procedure. The characteristic of the call shall be according to the DL reference measurement channels (12,2 kbit/s) or (64 kbit/s) specified in annex C for 1.28Mcps TDD option.
3) Enter the UE into loopback test mode and start the loopback test. (test 1) and/or activate the Ack/Nack test mode.
4) The levels of the wanted signal and the co-channel signals are set according to Table 12.2.2.2a, Table 12.2.2.2b and Table 12.2.2.2c for the 1,28 Mcps TDD Option. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.2.4.2 Procedure | Measure the BLER of DCH received from the UE at the SS for all tests specified in Table 12.2.2.2a and Table 12.2.2.2b for 1,28 Mcps TDD Option. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.2.5 Test requirements | |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.2.5.1 3.84Mcps TDD Option | [FFS] |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.2.5.2 1.28Mcps TDD Option | The measured BLER shall not exceed the values indicated in table 12.2.5.2 for 1.28 Mcps TDD Option.
Table 12.2.5.2: Performance requirements in static propagation conditions
Test Number
[dB]
BLER
1
0.3
10-2
2
3.4
10-2
3
9.3
10-2
4
4.7
10-1
5
11.3
10-1
6
13.5
10-1
NOTE: If the Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.2.5.3 7.68Mcps TDD Option | [FFS] |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.3 Demodulation of DCH in Multipath fading Case 1 conditions | |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.3.1 Definition and applicability | The performance requirement of DCH in Multipath fading Case 1 conditions is determined by the maximum Block Error Ratio (BLER). The BLER is specified for each individual data rate of the DCH. DCH is mapped into the Dedicated Physical Channel (DPCH).
The requirements and this test apply to all types of 1.28 Mcps TDD UE of Release 11 and later. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.3.2 Minimum requirements | |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.3.2.1 3.84 Mcps TDD Option | [FFS] |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.3.2.2 1.28 Mcps TDD Option | For the parameters specified in Table 12.3.2.2a and and Table 12.3.2.2b the BLER should not exceed the piece-wise linear BLER curve specified in Table 12.3.2.2c. The reference for this requirement is TS 25.102 [1] clause 12.3.1.2.
Table 12.3.2.2a: DCH parameters in Multipath fading Case 1 conditions (12.2 kbps)
Parameters
Unit
Test 1
Test 2
Test 3
Number of DPCHo
4
12
28
Scrambling code and basic midamble code number of SS#1*
19
19
19
Scrambling code and basic midamble code number of SS#2*
58
58
58
Scrambling code and basic midamble code number of SS#3*
85
85
85
DPCH Channelization Codes of SS#1*
C(k,Q)
C(i,16)
i=1,2
C(i,16)
i=1,2
C(i,16)
i=1,2
DPCHo Channelization Codes of SS#2*
C(k,Q)
C(i,16)
1≤ i ≤2
C(i,16)
1≤ i ≤6
C(i,16)
1≤ i ≤14
DPCHo Channelization Codes of SS#3*
C(k,Q)
C(i,16)
1≤ i ≤2
C(i,16)
1≤ i ≤6
C(i,16)
1≤ i ≤14
of SS#2
dB
10
5
0
of SS#3
dB
4
-1
-6
SFN-SFN Observed Timing Difference Type 2 between SS#1 and SS#2
chip
0
0
0
SFN-SFN Observed Timing Difference Type 2 between SS#1 and SS#3
chip
0
0
0
Power of SS#2**
dBm
-67
-67.22
-68.54
Power of SS#3**
dBm
-73
-73.22
-74.54
Ioc
dBm/1,28MHz
-80
Midamble
Default midamble (Kcell = 8)
*Note: Refer to TS 25.223 for definition of channelization codes, scrambling code and basic midamble code.
**Note: Power of SS can be calculated from and Ioc.
Table 12.3.2.2b: DCH parameters in Multipath fading Case 1 conditions (64 kbps)
Parameters
Unit
Test 4
Test 5
Test 6
Number of DPCHo
4
12
28
Scrambling code and basic midamble code number of SS#1*
19
19
19
Scrambling code and basic midamble code number of SS#2*
58
58
58
Scrambling code and basic midamble code number of SS#3*
85
85
85
DPCH Channelization Codes of SS#1*
C(k,Q)
C(i,16)
1≤ i ≤8
C(i,16)
1≤ i ≤8
C(i,16)
1≤ i ≤8
DPCHo Channelization Codes of SS#2*
C(k,Q)
C(i,16)
1≤ i ≤2
C(i,16)
1≤ i ≤6
C(i,16)
1≤ i ≤14
DPCHo Channelization Codes of SS#3*
C(k,Q)
C(i,16)
1≤ i ≤2
C(i,16)
1≤ i ≤6
C(i,16)
1≤ i ≤14
of SS#2
dB
10
5
0
of SS#3
dB
4
-1
-6
SFN-SFN Observed Timing Difference Type 2 between SS#1 and SS#2
chip
0
0
0
SFN-SFN Observed Timing Difference Type 2 between SS#1 and SS#3
chip
0
0
0
Power of SS#2**
dBm
-67
-67.22
-68.54
Power of SS#3**
dBm
-73
-73.22
-74.54
Ioc
dBm/1,28MHz
-80
Midamble
Default midamble (Kcell = 8)
*Note: Refer to TS 25.223 for definition of channelization codes, scrambling code and basic midamble code.
**Note: Power of SS can be calculated from and Ioc.
Table 12.3.2.2c: Performance requirements in Multipath fading Case 1 conditions
Test Number
[dB]
BLER
1
11.8
10-2
2
15.2
10-2
3
19.5
10-2
4
13.3
10-1
5
18.4
10-1
6
21.1
10-1 |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.3.2.3 7.68 Mcps TDD Option | [FFS] |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.3.3 Test purpose | The test purpose is to verify the ability of the receiver to receive a predefined test signal ,representing a static propagation channel for the wanted and for the co-channel signals from serving and adjacent cells, with a block error ratio (BLER) not exceeding a specified value. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.3.4 Method of test | |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.3.4.1 Initial conditions | Test environment: normal; see clauses G.2.1 and G.2.2.
Frequencies to be tested: mid range; see clause G.2.4.
1) Connect the SS, the fading simulator, AWGN Generator and additional components to the UE antenna connector as shown in figure A.20.
2) A call is set up according to the Generic call setup procedure. The characteristic of the call shall be according to the DL reference measurement channels (12,2 kbit/s) or (64 kbit/s) specified in annex C for 1.28Mcps TDD option.
3) Enter the UE into loopback test mode and start the loopback test. (test 1) and/or activate the Ack/Nack test mode.
4) The levels of the wanted signal and the co-channel signals are set according to Table 12.3.2.2a, Table 12.3.2.2b and Table 12.3.2.2c for the 1,28 Mcps TDD Option. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.3.4.2 Procedure | Measure the BLER of DCH received from the UE at the SS for all tests specified in Table 12.3.2.2a and Table 12.3.2.2b for 1,28 Mcps TDD Option. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.3.5 Test requirements | |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.3.5.1 3.84Mcps TDD Option | [FFS] |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.3.5.2 1.28Mcps TDD Option | The measured BLER shall not exceed the values indicated in table 12.3.5.2 for 1.28 Mcps TDD Option.
Table 12.3.5.2: Performance requirements in static propagation conditions
Test Number
[dB]
BLER
1
13.0
10-2
2
16.4
10-2
3
20.7
10-2
4
14.5
10-1
5
19.6
10-1
6
22.3
10-1
NOTE: If the Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.3.5.3 7.68Mcps TDD Option | [FFS] |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.4 Demodulation of DCH in Multipath fading Case 3 conditions | |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.4.1 Definition and applicability | The performance requirement of DCH in Multipath fading Case 3 conditions is determined by the maximum Block Error Ratio (BLER). The BLER is specified for each individual data rate of the DCH. DCH is mapped into the Dedicated Physical Channel (DPCH).
The requirements and this test apply to all types of 1.28 Mcps TDD UE of Release 11 and later. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.4.2 Minimum requirements | |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.4.2.1 3.84 Mcps TDD Option | [FFS] |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.4.2.2 1.28 Mcps TDD Option | For the parameters specified in Table 12.4.2.2a and and Table 12.4.2.2b the BLER should not exceed the piece-wise linear BLER curve specified in Table 12.4.2.2c. The reference for this requirement is TS 25.102 [1] clause 12.4.1.2.
Table 12.4.2.2a: DCH parameters in Multipath fading Case 3 conditions (12.2 kbps)
Parameters
Unit
Test 1
Test 2
Test 3
Number of DPCHo
4
12
28
Scrambling code and basic midamble code number of SS#1*
19
19
19
Scrambling code and basic midamble code number of SS#2*
58
58
58
Scrambling code and basic midamble code number of SS#3*
85
85
85
DPCH Channelization Codes of SS#1*
C(k,Q)
C(i,16)
i=1,2
C(i,16)
i=1,2
C(i,16)
i=1,2
DPCHo Channelization Codes of SS#2*
C(k,Q)
C(i,16)
1≤ i ≤2
C(i,16)
1≤ i ≤6
C(i,16)
1≤ i ≤14
DPCHo Channelization Codes of SS#3*
C(k,Q)
C(i,16)
1≤ i ≤2
C(i,16)
1≤ i ≤6
C(i,16)
1≤ i ≤14
of SS#2
dB
10
5
0
of SS#3
dB
4
-1
-6
SFN-SFN Observed Timing Difference Type 2 between SS#1 and SS#2
chip
0
0
0
SFN-SFN Observed Timing Difference Type 2 between SS#1 and SS#3
chip
0
0
0
Power of SS#2**
dBm
-67
-67.22
-68.54
Power of SS#3**
dBm
-73
-73.22
-74.54
Ioc
dBm/1,28MHz
-80
Midamble
Default midamble (Kcell = 8)
*Note: Refer to TS 25.223 for definition of channelization codes, scrambling code and basic midamble code.
**Note: Power of SS can be calculated from and Ioc.
Table 12.4.2.2b: DCH parameters in Multipath fading Case 3 conditions (64 kbps)
Parameters
Unit
Test 4
Test 5
Test 6
Number of DPCHo
4
12
28
Scrambling code and basic midamble code number of SS#1*
19
19
19
Scrambling code and basic midamble code number of SS#2*
58
58
58
Scrambling code and basic midamble code number of SS#3*
85
85
85
DPCH Channelization Codes of SS#1*
C(k,Q)
C(i,16)
1≤ i ≤8
C(i,16)
1≤ i ≤8
C(i,16)
1≤ i ≤8
DPCHo Channelization Codes of SS#2*
C(k,Q)
C(i,16)
1≤ i ≤2
C(i,16)
1≤ i ≤6
C(i,16)
1≤ i ≤14
DPCHo Channelization Codes of SS#3*
C(k,Q)
C(i,16)
1≤ i ≤2
C(i,16)
1≤ i ≤6
C(i,16)
1≤ i ≤14
of SS#2
dB
10
5
0
of SS#3
dB
4
-1
-6
SFN-SFN Observed Timing Difference Type 2 between SS#1 and SS#2
chip
0
0
0
SFN-SFN Observed Timing Difference Type 2 between SS#1 and SS#3
chip
0
0
0
Power of SS#2**
dBm
-67
-67.22
-68.54
Power of SS#3**
dBm
-73
-73.22
-74.54
Ioc
dBm/1,28MHz
-80
Midamble
Default midamble (Kcell = 8)
*Note: Refer to TS 25.223 for definition of channelization codes, scrambling code and basic midamble code.
**Note: Power of SS can be calculated from and Ioc.
Table 12.4.2.2c: Performance requirements in Multipath fading Case 3 conditions
Test Number
[dB]
BLER
1
6.5
10-2
2
8.8
10-2
3
11.6
10-2
4
10.9
10-1
5
14.3
10-1
6
17.0
10-1 |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.4.2.3 7.68 Mcps TDD Option | [FFS] |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.4.3 Test purpose | The test purpose is to verify the ability of the receiver to receive a predefined test signal ,representing a static propagation channel for the wanted and for the co-channel signals from serving and adjacent cells, with a block error ratio (BLER) not exceeding a specified value. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.4.4 Method of test | |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.4.4.1 Initial conditions | Test environment: normal; see clauses G.2.1 and G.2.2.
Frequencies to be tested: mid range; see clause G.2.4.
1) Connect the SS, the fading simulator, AWGN Generator and additional components to the UE antenna connector as shown in figure A.20.
2) A call is set up according to the Generic call setup procedure. The characteristic of the call shall be according to the DL reference measurement channels (12,2 kbit/s) or (64 kbit/s) specified in annex C for 1.28Mcps TDD option.
3) Enter the UE into loopback test mode and start the loopback test. (test 1) and/or activate the Ack/Nack test mode.
4) The levels of the wanted signal and the co-channel signals are set according to Table 12.4.2.2a, Table 12.4.2.2b and Table 12.4.2.2c for the 1,28 Mcps TDD Option. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.4.4.2 Procedure | Measure the BLER of DCH received from the UE at the SS for all tests specified in Table 12.4.2.2a and Table 12.4.2.2b for 1,28 Mcps TDD Option. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.4.5 Test requirements | |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.4.5.1 3.84Mcps TDD Option | [FFS] |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.4.5.2 1.28Mcps TDD Option | The measured BLER shall not exceed the values indicated in table 12.4.5.2 for 1.28 Mcps TDD Option.
Table 12.4.5.2: Performance requirements in static propagation conditions
Test Number
[dB]
BLER
1
7.7
10-2
2
10.0
10-2
3
12.8
10-2
4
12.1
10-1
5
15.5
10-1
6
18.2
10-1
NOTE: If the Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 12.4.5.3 7.68Mcps TDD Option | [FFS] |
852c5999d703da168048fd5b505d5d2d | 30.820 | 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.
Status list of Work items can be found in Annex A of the present document. |
852c5999d703da168048fd5b505d5d2d | 30.820 | 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/
TSG SA Meeting #46 SP-090761
07 - 10 December 2009,
Sanya, China |
852c5999d703da168048fd5b505d5d2d | 30.820 | 3 Local IP Access and Selected Internet IP Traffic Offload UID_450035 | TSG SA Meeting #51 SP-110131
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-111532
SA5#76, 28 Feb - 4 Mar 2011, San Diego, USA revision of S5-111079
3GPP TSG-SA5 (Telecom Management) MCC merger of S5-094347 and S5-0904339
Meeting SA5#68, 9 Nov-13 Nov 2009, Shanghai, China
TSG SA Meeting #45 SP-090618
21 - 24 September 2009, Seville, Spain
3GPP TSG SA WG2 Meeting #75 TD S2-096108
31 August – 4 September, 2009, Kyoto, Japan |
852c5999d703da168048fd5b505d5d2d | 30.820 | 3.1 OAM&P for LIPA_SIPTO UID_450040 | Clauses 3.1 and 3.2 share the same SA-wide WI description reported in 3.2. |
852c5999d703da168048fd5b505d5d2d | 30.820 | 3.2 Charging for LIPA_SIPTO UID_460039 | Local IP Access and Selected IP Traffic Offload UID_LIPA_SIPTO |
852c5999d703da168048fd5b505d5d2d | 30.820 | 1 3GPP Work Area * | Radio Access
X
Core Network
Services |
852c5999d703da168048fd5b505d5d2d | 30.820 | 2 Classification of WI and linked work items | |
852c5999d703da168048fd5b505d5d2d | 30.820 | 2.0 Primary classification * | This work item is a … *
Study Item (go to 2.1)
Feature (go to 2.2)
X
Building Block (go to 2.3)
Work Task (go to 2.4) |
852c5999d703da168048fd5b505d5d2d | 30.820 | 2.1 Study Item | Related Work Item(s) (if any]
Unique ID
Title
Nature of relationship
Go to §3. |
852c5999d703da168048fd5b505d5d2d | 30.820 | 2.2 Feature | Related Study Item or Feature (if any) *
Unique ID
Title
Nature of relationship
Go to §3. |
852c5999d703da168048fd5b505d5d2d | 30.820 | 2.3 Building Block | Parent Feature (or Study Item)
Unique ID
Title
TS
410030
Network Improvements for Machine-Type Communications
-
This work item is … *
Stage 1 (go to 2.3.1)
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.3 Stage 3 *
Corresponding stage 2 work item (if any)
Unique ID
Title
TS
490037
Stage 2 for Network Improvements for Machine-Type Communications
23.060, 23.236, 23.401 |
852c5999d703da168048fd5b505d5d2d | 30.820 | 3 Justification * | Excerpt from TR 22.868 on Machine-to-Machine communications:
“It appears that there is market potential for M2M beyond the current "premium M2M market segment" i.e. the market segments that are currently using M2M. In particular it is possible to identify potential applications for mass M2M service, e.g. consumer products manufacturers could keep in touch with their products after they are shipped – car manufacturers could serve as an example for that. Another example is in the home environment where remote maintenance of heating and air condition, alarm systems and other applications can also be identified.”
The study on Machine-to-Machine communications indicated the potential for machine-type communications over mobile networks. However, for example wireless sensor networks (e.g. Zigbee) in combination with fixed network communications are also a contender for the implementation of such applications. For mobile networks to be competitive for mass machine-type applications, it is important to optimise their support for machine-type communications. The current mobile networks are optimally designed for Human-to-Human communications, but are less optimal for machine-to-machine, machine-to-human, or human-to-machine applications. It is also important to enable network operators to offer machine-type communication services at a low cost level, to match the expectations of mass-market machine-type services and applications. |
852c5999d703da168048fd5b505d5d2d | 30.820 | 4 Objective * | The objective is to enhance existing PS/EPS charging with Machine-Type Communications (MTC) information in alignment to the Rel-10 stage 2 description for MTC service support. Only Charging requirements specified in stage 1 TS 22.368 shall be addressed in this work item. |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5 Service Aspects | Covered by the parent Feature |
852c5999d703da168048fd5b505d5d2d | 30.820 | 6 MMI-Aspects | Covered by the parent Feature |
852c5999d703da168048fd5b505d5d2d | 30.820 | 7 Charging Aspects | This is a Charging Work Item |
852c5999d703da168048fd5b505d5d2d | 30.820 | 8 Security Aspects | Covered by the parent Feature |
852c5999d703da168048fd5b505d5d2d | 30.820 | 9 Impacts * | Affects:
UICC apps
ME
AN
CN
Others
Yes
X
No
X
X
X
X
Don't know |
852c5999d703da168048fd5b505d5d2d | 30.820 | 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
Affected existing specifications *
[None in the case of Study Items]
Spec No.
CR
Subject
Approved at plenary#
Comments
32.251
MTC charging enhancements
SA#51 Mar 2011
Charging Data Record (CDR) parameter description
32.298
CDR enhancements for MTC
SA#51 Mar 2011
Packet Switched (PS) domain charging
32.299
Diameter charging application enhancements for MTC
SA#51 Mar 2011
Diameter charging applications
11 Work item rapporteur(s) *
Patrik Teppo (patrik teppo at ericsson dot com)
12 Work item leadership *
SA5
13 Supporting Individual Members *
Supporting IM name
Alcatel-Lucent
AT&T
Ericsson
Huawei
Nokia Siemens Networks
Orange
Vodafone
ZTE
Annex A:
Status of SA5 Work Items
This list reflects work items moved, ongoing, completed or stopped.
510040
Charging for Network Improvements for Machine-Type Communication
NIMTC-CH
450035
Local IP Access and Selected Internet IP Traffic Offload
LIPA_SIPTO
450040
OAM&P for Local IP Access and Selected Internet IP Traffic Offload
LIPA_SIPTO
460039
Charging for Local IP Access and Selected Internet IP Traffic Offload
LIPA_SIPTO
450041
IP Flow Mobility and seamless WLAN offload
IFOM
470021
Charging for IP Flow Mobility and seamless WLAN offload
IFOM
460028
Optimal Media Routing
OMR
500013
Charging for Optimal Media Routing
OMR
460031
Rel-10 Operations, Administration, Maintenance and Provisioning (OAM&P)
OAM10
460032
Network Infrastructure Management
OAM10-NIM
460033
Common RAT Network Resource Model (NRM)
RAT_NRM_common
470035
IRP Solution Set specification organisation improvements
OAM-IRP-SS
470036
Deleted - Service Oriented Architecture (SOA) for IRP continuation from Rel-9
OAM-SOA-IRP
480042
IRP Overview, Profiles & Usage Guide
OAM-NIM-IRP_OPU
510041
Alarm Correlation and Root Cause Analysis
OAM-AC-RCA
510042
Inventory Management Network Resource Model enhancements
OAM-IM-NMR
460034
Self-Organizing Networks (SON) - OAM aspects
OAM10-SON
460035
SON Self-optimization management continuation
LTE-SON-OAM_SO
460036
SON Self-healing management
LTE-SON-OAM_SH
470037
OAM aspects of Energy Saving in Radio Networks
OAM-ES
470038
Subscription Management (SuM) evolution
OAM10-SuM
470039
Performance Management
OAM10-PM
470040
Key Performance Indicators (KPIs) for IMS
OAM-PM-KPI_IMS
470041
Key Performance Indicators (KPIs) for EPC
OAM-PM-KPI_EPC
470042
Management of UE based network performance measurements
OAM-PM-UE
470142
Management of UE based network performance measurements
OAM-PM-UE
470043
3G HNB and LTE HeNB Subsystem performance measurements
OAM-PM-HeNS
470044
Rel-10 Charging Management small Enhancements
CH10
440063
IWLAN mobility charging
eIWLAN_Mob
470046
Advice of Charge (AoC) service support enhancements
eAoC
470047
SA5 part - AoC enhancements
eAoC
410044
Study on Rc Reference Point Functionalities and Message Flows
FS_OAM_Rc
430044
Study on Telecommunication Management; Energy Savings Management
FS_OAM_ESM
440069
Study on Integration of Device Management Information with Itf-N
FS_IDMI_Itf-N
460037
Study on Alignment of 3GPP Generic NRM IRP and TMF Shared Information Data (SID) model
FS_3GNRM_TMFSID
460038
Study on Harmonization of 3GPP Alarm IRP and TMF Interface Program (TIP) Fault Management
FS_3G_TMF_FM
480045
Study on Alarm Correlation and Alarm Root Cause Analysis
FS_AC_ARCA
480046
Study on Alignment of 3GPP PM IRP and TMF Interface Program (TIP) PM
FS_3G_TMF_PM
440050
Deleted - Study on EPC Charging enhancement
FS_EPCcharg
Annex B:
Change history
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
Sep 2011
SP-53
SP-110516
--
--
Presentation to SA for information and approval
---
1.0.0
Sep 2011
--
--
--
--
Publication
1.0.0
10.0.0 |
852c5999d703da168048fd5b505d5d2d | 30.820 | 4 IP Flow Mobility and seamless WLAN offload UID_450041 | Technical Specification Group Services and System Aspects TSGS#47(10)0089
Meeting #47; Vienna, Austria; 22-25 March 2010
3GPP TSG-SA5 (Telecom Management) S5-101018
Meeting SA5#70, 01 - 05 Mar 2010, Xiamen, China
3GPP TSG-SA5 (Telecom Management) S5-100484
Meeting SA5#69, 18 - 22 Jan 2010, Valencia, Spain revision of S5-100190
TSG SA Meeting #46 SP-090804
07 - 10 December 2009,
Sanya, China
Title: Updated Feature WID: IP Flow Mobility and seamless WLAN offload
Source: SA WG2
Agenda Item: 11.10
TSG SA WG2 Meeting #76 S2-097477
16-20 November, 2009, San Jose del Cabo, Mexico
This is a proposed update of the IFOM WID to:
• add that system description for non-seamless WLAN offload will be specified in TS 23.402.
• update the reference and title of the new TS created by this work
• add more supporting companies.
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900. |
852c5999d703da168048fd5b505d5d2d | 30.820 | 4.1 Charging for IFOM UID_470021 | |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.1 Network Infrastructure Management UID_460032 | Technical Specification Group Services and System Aspects TSGS#48(10)0293
Meeting #48; Seoul, Republic of Korea; 07-10 June 2010
3GPP TSG-SA5 (Telecom Management) S5-101530
Meeting SA5#71, 10-14 May 2010, Montreal, Canada revision of SP-090758
TSG SA Meeting #46 SP-090758
07 - 10 December 2009,
Sanya, China |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.1.1 Common RAT Network Resource Model (NRM) - RAT_NRM_common – UID_460033 | |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.1.2 IRP Solution Set Specification Organisation Improvements (OAM-IRP-SS) UID_470035 | |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.1.3 Service Oriented Architecture (SOA) for IRP; continuation (OAM-SOA-IRP) UID_470036 | Technical Specification Group Services and System Aspects TSGS#47(10)0076
Meeting #47; Vienna, Austria; 22-25 March 2010
3GPP TSG-SA5 (Telecom Management) S5-100890
Meeting SA5#70, 1-5 March 2010, Xiamen, China revision of S5-100603 |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.1.4 IRP Overview, Profiles & Usage Guide (OAM-NIM-IRP_OPU) UID_ 480042 | 3GPP TSG SA Meeting #52 SP-110277
Bratislava, Slovakia, 06 – 08 June, 2011
3GPP TSG-SA5 (Telecom Management) S5-112084
SA5#77, 09 May – 13 May 2011; Shenzhen, China revision of SP-100777
TSG SA Meeting #50 SP-100777
13-15 Dec 2010, Istanbul, Turkey
Technical Specification Group Services and System Aspects TSGS#48(10)0388
Meeting #48; Seoul, Republic of Korea; 07-10 June 2010
3GPP TSG-SA5 (Telecom Management) S5-101421
Meeting SA5#71, 10-14 May 2010, Montreal, CANADA revision of S5-101400 |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.1.5 Alarm correlation and root cause analysis (OAM-AC-RCA) UID_510041 | TSG SA Meeting #51 SP-110137
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-111498
SA5#76, 28 Feb - 4 Mar 2011; San Diego, USA revision of S5-111(198,343) |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.1.6 Inventory Management Network Resource Model enhancements (OAM-IM-NMR) UID_510042 | TSG SA Meeting #51 SP-110141
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-111493
SA5#76, 28 Feb - 4 Mar 2011; San Diego, USA revision of S5-111346 |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.2 Self-Organizing Networks OAM aspecsts (OAM-10-SON) UID_ 460034 | TSG SA Meeting #51 SP-110130
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-111414
SA5#76, 28 Feb - 4 Mar 2011; San Diego, USA revision of S5-111088
TSG SA Meeting #51 SP-110130
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-111414
SA5#76, 28 Feb - 4 Mar 2011; San Diego, USA revision of S5-111088
TSG SA Meeting #46 SP-090756
07 - 10 December 2009,
Sanya, China
3GPP TSG-SA5 (Telecom Management) S5-094092
Meeting SA5#68 09-13 Nov 2009, Shanghai, China |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.2.1 SON self-optimization management continuation - LTE-SON-OAM-SO UID_460035 | |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.2.2 SON self-healing management (LTE-SON-OAM-SH) UID_460036 | TSG SA Meeting #51 SP-110150
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-111524
SA5#76, 28 Feb - 4 Mar 2011; San Diego, USA revision of SP-100776
TSG SA Meeting #50 SP-100776
13-15 Dec 2010, Istanbul, Turkey
3GPP TSG-SA5 (Telecom Management) S5-103369
SA5#74-OAM , 15 - 19 Nov 2010; Jacksonville, USA revision of S5-10abcd
TSG SA Meeting #46 SP-090757
07 - 10 December 2009, Sanya, China
3GPP TSG-SA5 (Telecom Management) S5-094354
Meeting SA5#68 09-13 Nov 2009, Shanghai, China |
852c5999d703da168048fd5b505d5d2d | 30.820 | 11 Work item rapporteur(s) * | ZTE ([email protected]) |
852c5999d703da168048fd5b505d5d2d | 30.820 | 12 Work item leadership * | SA5 |
852c5999d703da168048fd5b505d5d2d | 30.820 | 13 Supporting Individual Members * | Supporting IM name
ZTE
Vodafone
China Mobile
Nokia Siemens Networks
Huawei Technologies.
Motorola
T-Mobile
Orange
Telecom Italia
Telefonica
TeliaSonera
China Telecom |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.2.3 OAM aspects of Energy Saving in Radio Networks (OAM10-ES) UID_470037 | TSG SA Meeting #51 SP-110128
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-110533
SA5#75, 24 - 28 Jan 2011; Sorrento, ITALY revision of SP-110226
Technical Specification Group Services and System Aspects TSGS#47(10)0226
Meeting #47; Vienna, Austria; 22-25 March 2010 revision of SP-100077
3GPP TSG-SA5 (Telecom Management) S5-100891
Meeting SA5#70, March 01-05 2010, Xiamen, China revision of S5-10693
Source: Nokia Siemens Networks, Vodafone, Huawei, NEC Corporation
Title: New WID on OAM aspects of Energy Saving in Radio Networks |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.3 Subscription Management (SuM) evolution OAM10-SuM UID_470038 | Technical Specification Group Services and System Aspects TSGS#47(10)0086
Meeting #47; Vienna, Austria; 22-25 March 2010
3GPP TSG-SA5 (Telecom Management) S5-100709
Meeting SA5#70, 01-05 March 2010, Xiamen, P.R.China
Source: Ericsson, Verizon Wireless, Alcatel-Lucent, Nokia Siemens Networks
Title: New WID on Subscription Management (SuM) evolution
Document for: Approval
Agenda Item: 6.02 New OAM Work Item proposals |
852c5999d703da168048fd5b505d5d2d | 30.820 | 1 3GPP Work Area | X
Radio Access
X
Core Network
Services |
852c5999d703da168048fd5b505d5d2d | 30.820 | 2.0 Primary classification | This work item is a …
X
Study Item (go to 2.1)
Feature (go to 2.2)
Building Block (go to 2.3)
Work Task (go to 2.4) |
852c5999d703da168048fd5b505d5d2d | 30.820 | 4 Objective | The objective of this technical work is to study automated energy savings management features. Usage of existing IRPs is expected as much as possible, e.g. Configuration Management IRP, etc. However, this technical work may identify the need for defining a new IRP.
The following operations may be considered in this study item (but not necessarily limited to):
Retrieval of energy consumption measurements
Retrieval of traffic load measurements
Adjust Network Resources capabilities
Note that SA5 is willing to work in cooperation with RAN WGs that define e.g. eNodeB energy savings control mechanisms. |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.4 Performance Management (OAM10-PM) UID_470039 | Technical Specification Group Services and System Aspects TSGS#47(10)0083
Meeting #47; Vienna, Austria; 22-25 March 2010
3GPP TSG-SA5 (Telecom Management) S5- 100340
Meeting SA5#69, 18 - 22 Jan 2010, Valencia, Spain revision of S5-10xyzw
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900. |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.4.1 Key Performance Indicators (KPIs) for IMS (OAM-PM-KPI_IMS) UID_470040 | |
852c5999d703da168048fd5b505d5d2d | 30.820 | 3 Justification | Sustainable development is a long-term commitment in which all of us should take part. As part of sustainable development, our fight against global warming should be without respite. Our activities have a limited impact on environment: in 2007, the total footprint of the ICT sector was about 2% of the estimated total emissions from human activity and telecoms are only a part of ICT which represents no more than 25% of these 2%.
Nevertheless, most mobile network operators aim at reducing their greenhouse emissions, by several means such as limiting their networks' energy consumption.
In new generation Radio Access Networks such as LTE, Energy Savings Management function takes place especially when mobile network operators want e.g. to reduce Tx power, switch off/on cell, etc. based on measurements made in the network having shown that there is no need to maintain active the full set of NE capabilities.
By initiating this Work Item about Energy Savings Management, we hope to contribute to the protection of our environment and the environment of future generations. |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.4.2 Key Performance Indicators (KPIs) for EPC (OAM-PM-KPI_EPC) UID_470041 | |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.4.3 Management of UE based network performance measurements (OAM-PM-UE) UID_470042 | |
852c5999d703da168048fd5b505d5d2d | 30.820 | 9 Impacts | Affects:
UICC apps
ME
AN
CN
Others
Yes
X
X
No
X
X
X
Don't know |
852c5999d703da168048fd5b505d5d2d | 30.820 | 10 Expected Output and Time scale | New specifications
[If Study Item, one TR is anticipated]
Title
Prime rsp. WG
2ndary rsp. WG(s)
Presented for information at plenary#
Approved at plenary#
Comments
TR 32.xx1
Study on Energy Savings Management -Concepts and Requirements
SA5
SA#47 Mar 2010
SA#47 Mar 2010
The TR shall describe concepts and requirements for Energy Savings Management
Affected existing specifications
[None in the case of Study Items]
Spec No.
CR
Subject
Approved at plenary#
Comments
11 Work item Rapporteur(s)
Orange, Jean-Michel Cornilly; Vodafone
12 Work item leadership
SA5
13 Supporting Individual Members
Supporting IM name
Alcatel-Lucent
China Mobile
Huawei Technologies
Orange SA
Telefonica
T-Mobile
Vodafone
Technical Specification Group Services and System Aspects TSGS#47(10)0088
Meeting #47; Vienna, Austria; 22-25 March 2010
3GPP TSG-SA5 (Telecom Management) S5-101014
Meeting SA5#70, 01 - 05 Mar 2010, Xiamen, China
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. |
852c5999d703da168048fd5b505d5d2d | 30.820 | 5.4.4 3G HNB and LTE HeNB Subsystem performance measurement (OAM-PM-HeNS) UID_470043 | |
852c5999d703da168048fd5b505d5d2d | 30.820 | 6 Charging Management small Enhancements (CH10) UID_470044 | 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
Source: Orange
Title: WID Update: IWLAN Mobility charging
Document for: Approval
Agenda Item: |
852c5999d703da168048fd5b505d5d2d | 30.820 | 6.1 IWLAN mobility charging (IWLAN_Mob) UID_440063 Moved from Rel-9 | |
852c5999d703da168048fd5b505d5d2d | 30.820 | 6.2 Add solutions for Rc (reference point within OCS) (CH-Rc) UID_470045 Moved to Rel-11 | |
852c5999d703da168048fd5b505d5d2d | 30.820 | 7 Advice of Charge (AoC) service support enhancements (eAoC) UID_470046 | Technical Specification Group Services and System Aspects TSGS#47(10)0080
Meeting #47; Vienna, Austria; 22-25 March 2010
3GPP TSG-SA5 (Telecom Management) S5-101030
Meeting SA5#70, 01 - 05 Mar 2010, Xiamen, China revision of S5-100905
Source: Deutsche Telekom
Title: New WID proposal on Advice of Charge (AoC) service support enhancements
Document for: Approval
Agenda Item:
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900. |
852c5999d703da168048fd5b505d5d2d | 30.820 | 7.1 Advice of Charge (AoC) service support enhancements (eAoC) UID_470047 | |
852c5999d703da168048fd5b505d5d2d | 30.820 | 8 Feasibility studies | 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 |
852c5999d703da168048fd5b505d5d2d | 30.820 | 8.1 Study on Rc Reference Point Functionalities and Message Flows UID_410044 – Moved from Rel-9 | Is this Work Item a "Study Item"? (Yes / No): Yes
1 3GPP Work Area
Radio Access
X
Core Network
Services
2 Linked work items
Release 8 Small charging enhancements
3 Justification
The purpose of this SID is to serve as a basis for detailed specification of OCS interfaces Rc in SA5. Under a comprehensive consideration of the status of OCS, it is proposed to start study of Rc reference point solution. It is therefore recommended to have a study item to guide further specification of the Rc reference point.
4 Objective
This Study Item aims to have a study report and recommendation for Rc Reference Point.
5 Service Aspects
None/Text
6 MMI-Aspects
None/Text
7 Charging Aspects
8 Security Aspects
None/Text |
852c5999d703da168048fd5b505d5d2d | 30.820 | 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
32.825
Telecommunication management; Charging management; Rc Reference Point Study
SA5
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
11 Work item rapporteur(s)
Mingjun Shan, Huawei [[email protected]]
12 Work item leadership
SA5
13 Supporting Companies
Huawei, China Mobile, Orange, China Unicom, ZTE
14 Classification of the WI (if known)
Study Item (no further information required)
Feature (go to 14a)
Building Block (go to 14b)
X
Work Task (go to 14c) |
852c5999d703da168048fd5b505d5d2d | 30.820 | 14a The WI is a Feature: List of building blocks under this feature | (list of Work Items identified as building blocks) |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.