hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 2 References, abbreviations and definitions | |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 2.1 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.
• Fo... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 2.2 Abbreviations | For the purposes of the present document, the following abbreviations apply:
FPS Frame Pattern Substitution
FSI Frame Start Identifier
ZSP Zero Sequence Position |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 2.3 Definitions | For the purposes of the present document, the following terms and definitions apply.
Substream: Stream of data with explicit or implicit numbering between splitter and combine functions.
Channel: A physical full rate channel on the radio interface (TCH/F) independent of the contents.
A interface circuit: The 8 bits tha... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 3 General approach | 3GPP TS 03.10 (clause 6) defines the PLMN connection types necessary to support the GSM PLMN data and telematic services.
Within the BSS , transcoder and IWF, there are several data rate adaptation functions which are combined as shown in 3GPP TS 03.10 as part of a connection type.
These functions are RA0, RA1, RA1/RA1... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 4 The RA0 Function | The RA0 function is specified in 3GPP TS 04.21 |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 5 The RA1 Function | For connections where only one channel is allowed used on the radio interface, the specification in 3GPP TS 04.21 for adaptation of synchronous data rates up to and including 9,6 kbit/s to intermediate rates 8 or 16 kbit/s shall apply.
For connection where more than one channel are used on the radio interface, rate ada... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 6 The RA1’’ Function | The RA1’’ function is specified in 3GPP TS 04.21. The RA1’’ function is only applicable in BSS for AIUR higher than 38,4 kbit/s. |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 7 Split/Combine and Padding Functions | The Split/Combine-function in the IWF shall be used in cases when up to and including 4substreams are used.
The Split/Combine-function in the BSS shall be used only when more than four substreams are used. |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 7.1 Data Frame distribution into the channels by the Split/Combine function | Described in 3GPP TS 04.21 |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 7.2 Substream numbering | Described in 3GPP TS 04.21 |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 7.3 Initial Substream Synchronisation for Transparent Services | Described in 3GPP TS 04.21 |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 7.4 Frame Synchronisation and Action on loss of Synchronisation | When in the IWF, the Split/Combine function is responsible for controlling the initial frame synchronisation procedure and re-synchronisation procedure as described in 3GPP TS 29.007. |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 7.5 Network Independent Clocking | NIC is specified in 3GPP TS 04.21 |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 7.6 Padding | Padding is specified in 3GPP TS 04.21 |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 8 The EDGE Multiplexing Function | In EDGE configurations where the number of radio interface channels and number of channels or substreams used between BTS and MSC do not match, a multiplexing function described below shall be used at BTS to perform data multiplexing/demultiplexing between the radio interface and network channel configurations. A simil... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 9 The RA1/RA1' Function | For AIURs less than or equal to 38,4 kbit/s, the RA1/RA1’ function in the BSS shall be applied on each of the n substreams and there are no significant differences between the single slot case and the multislot case. For AIURs less than or equal to 38,4 kbit/s RA1/RA1’ is as specified in 3GPP TS 04.21 for the single sl... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 9.1 Radio Interface rate of 12 kbit/s | Described in 3GPP TS 04.21. |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 9.2 Radio Interface rate of 6 kbit/s | Described in 3GPP TS 04.21. |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 9.3 Radio Interface rate of 3.6 kbit/s | Described in 3GPP TS 04.21. |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 9.4 Synchronisation | Refer to 3GPP TS 04.21. |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 9.5 Idle frames | Refer to 3GPP TS 04.21 |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 10 THE RA1'/RAA' FUNCTION | The RA1'/RAA' shall be applied only when TCH/F14.4, TCH/F28.8, or TCH/F43.2 channel coding is used. The RA1/RAA' converts 290-bit blocks from the channel coder or EDGE multiplexing function into E-TRAU frames and vice versa. The format of E-TRAU frame is specified in 3GPP TS 08.60.
The RA1'/RAA' function in the BSS sha... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 10.1 Radio Interface rate of 14,5 kbit/s | See 3GPP TS 08.60. |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 10.2 Synchronisation | See 3GPP TS 08.60. |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 10.3 Idle frames | See 3GPP TS 08.60. |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 11 THE RAA' FUNCTION | The RAA' function shall be applied only when TCH/F14.4, TCH/F28.8, or TCH/F43.2 channels are used.
The RAA' converts E-TRAU frame into A-TRAU frame and vice versa.
The format of the E-TRAU frame is specified in 3GPP TS 08.60. |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 11.1 Coding of A-TRAU frame | The format of the A-TRAU frame is given in Figure 5.
An A-TRAU frame carries eight 36 bit-data frames.
C Bits
Table 3
C1
C2
C3
C4
Date Rate
0
1
1
1
14,4 kbit/s
0
1
1
0
14.4 kbit/s idle (IWF to BSS only)
Table 4
C5
BSS to IWF
Frame Type
note 1
IWF to BSS
UFE (Uplink Frame Error)
1
idle
framing error
0
data
no framing er... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 11.2 Framing Pattern Substitution in A-TRAU frame | The Framing Pattern Substitution is used in each of the eight 36 bit data fields of the A-TRAU frame (see Figure 5) to avoid transmitting a sequence of eight zeroes (called Z sequence in the following).
The purposes of FPS is to avoid erroneous synchronisation to the A-TRAU due to sixteen zeroes occurring accidentally ... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 11.2.1 FPS encoding | A Zero Sequence Position (ZSP) field is used to account for the occurrence of eight zeroes in the 36 bit data field.
NOTE: A sequence of eight zeroes is considered as a block (e.g. a stream of eleven consecutive zeroes produces only one ZSP and not four ZSPs).
The ZSP field is defined as follows:
Table 5
1
2
3
4
5
6
7
... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 11.3 A-TRAU Synchronisation Pattern | The frame synchronisation is obtained by means of the first two octets in each frame, with all bits coded binary "0" and the first bit in octet no 2 coded binary "1". The following 17 bit alignment pattern is used to achieve frame synchronisation :
00000000 00000000 1XXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 12 THE RAA'' FUNCTION | On the IWF side of the A interface, the RAA" function shall convert between the A-TRAU format and a synchronous stream. FPS shall be performed by this function as well, see subclause 11.2. In transparent operation, the RAA" function shall handle the M1 and M2 bits as specified for the RA1' function in 3GPP TS 04.21.
In... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 13 The RA2 Function | Described in 3GPP TS 04.21. The RA2 function shall be applied only for single slot operations. |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 14 The A-interface Multiplexing Function | The multiplexing function shall be applied only for AIUR up to and including 57.6 kbit/s for multislot operations.
The multiplexing function is based on the ITU-T I.460. The multiplexing function is used to combine n (n=2 to 4) substreams of multislot intermediate rate of 8 kbit/s or n substreams of multislot intermedi... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 15 Support of non-transparent bearer services | |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 15.1 TCH/F9.6 and TCH/F4.8 kbit/s channel codings | In the case of non-transparent services the RA1/RA1' function shall perform the same mapping as that described for transparent services, using 12 and 6 kbit/s radio interface data rates, with the following modification.
The E2 and E3 bits in the modified ITU-T V.110 80 bit frames shown in Figure 3 (derived from the sta... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 15.1.1 Alignment | An alignment window spanning four modified ITU-T V.110 80 bit frames shall be used to search for the pattern of 8 bits described above in order to identify alignment with an RLP frame.
In the event of failure to detect the 8 bit pattern, the alignment window is shifted one complete modified V.110 80 bit frame, discardi... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 15.1.2 Support of Discontinuous Transmission (DTX) | The E1 bit in the modified ITU-T V.110 80 bit frame shown in Figure 3 shall be used in the direction MSC-BSS to indicate that DTX may be invoked (see 3GPP TS 24.022). The E1 bit in all of the four consecutive frames relating to the RLP frame to which DTX may be applied shall be set to 1. If DTX is not to be applied, th... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 15.1.3 Order of Transmission | The first bit of each quarter of an RLP frame to be transmitted shall correspond to bit D1 of a modified V.110 frame (figures 3 and 4). The remaining 59 bits of each quarter of an RLP frame shall correspond to the D and D' bits , D2 - D'12, in order left to right and top to bottom as shown in figures 3 and 4.
The first... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 15.2 TCH/F14.4, TCH/F28.8, and TCH/F43.2 channel codings | In case of non-transparent service, a 576 bit RLP frame shall be mapped over two consecutive A-TRAU frames.
Because of that mapping, it is required, following a transmission break and at start up, to determine which A-TRAU frame of the stream is the first for a particular RLP frame. This is needed so that correct align... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 15.2.1 Alignment | An alignment window spanning two 290 bit blocks in case of TCH/F14.4 channel shall be used to search for the pattern of 2 bits '01' described in subclause 15.2, in order to identify alignment with an RLP frame.
In the event of failure to detect the 2 bits pattern the alignment window is shifted one 290 bit block, disca... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 15.2.2 Support of Discontinuous Transmission (DTX) | The M2 bit in the A-TRAU frame shown in Figure 5 shall be used in the direction MSC to BSS to indicate that DTX may be invoked (see 3GPP TS 24.022). The M2 bit in all of the two consecutive A-TRAU frames relating to the RLP frame to which DTX may be applied shall be set to 1. If DTX is not to be applied, the M2 bit sha... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16 Support of transparent bearer services | |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16.1 TCH/F9.6 and TCH/F4.8 channel codings | |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16.1.1 User rate adaptation on the A interface, AIUR less than or equal to 38,4 kbit/s | The ITU-T V.110 80 bit frame shall be used for transparent data on the A interface. These frames are transmitted on up to four substreams multiplexed into one stream sent over the A interface. The split/combine function is applied on the substreams as specified in clause 5 of this GSM TS. The relation between the AIUR ... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16.1.2 User rate Adaptation on the A-interface, AIUR greater than 38,4 kbit/s | For AIUR of 48 kbit/s, 56 kbit/s and 64 kbit/s one stream consisting of ITU-T V.110 32 bit frames or 64 bit frames, as specified in 3GPP TS 04.21 shall be transmitted over the A-interface. Splitting/Combining which occurs in the BSS, is as specified in 3GPP TS 04.21.
Table 11 gives the relation between the User Rate, S... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16.1.3 Relation between AIUR and the number of channels | Table11: Relationship between the AIUR, substream rate, channel coding, intermediate rate and number of channels
AIUR
Number of channels x Substream Rate
Channel Coding
(Multislot) intermediate Rate (Note1)
2,4 kbit/s
2-8 times duplication of each bit to reach 4,8 kbit/s
TCH/F4.8
8 kbit/s
4,8 kbit/s
4,8 kbit/s
TCH/F4.... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16.1.4 Handling of status bits X, SA, SB | In the single slot case, status bit SA shall be coded repeatedly as S1, S3, S6, S8, and SB is coded repeatedly as S4 and S9 in Figure 2. In the multislot case, status bit SA is coded repeatedly as S6, S8 and SB is coded as S9 in figures 2, 5 and 6.
The handling of the status bits shall comply with the synchronisation p... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16.1.5 Handling of bits E1 to E7 | Bits E1 to E3 shall be used according to 04.21.
Bits E4 to E7 may be used for network independent clocking as indicated in 3GPP TS 04.21. |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16.2 TCH/F14.4, TCH/F28.8, and TCH/F32.0 channel codings | |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16.2.1 User rate adaptation on the A interface, AIUR less than or equal to 56 kbit/s | The A-TRAU frame shall be used for transparent user data rates other than 32 kbit/s on the A interface. The A-TRAU frames are transmitted on up to four substreams multiplexed into one stream sent over the A interface. The split/combine function is applied on the substreams as specified in clause 7 of this TS. The relat... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16.2.2 User Rate Adaptation on the A-interface, AIUR greater than 56 kbit/s | For AIUR of 64 kbit/s one stream consisting of ITU-T V.110 32 bit frames or 64 bit frames, as specified in 3GPP TS 04.21 shall be transmitted over the A-interface. Splitting/Combining which occurs in the BSS, shall be as specified in 3GPP TS 04.21.
Table 12 gives the relation between the User Rate, Substream Rate Chann... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16.2.3 Relation between AIUR and the number of channels | Table 12: Relationship between the AIUR, AIUR per substream, channel coding, intermediate rate and number of substreams
AIUR
Number of substreams x
AIUR per substream
Channel Coding
Multislot intermediate Rate (note 1)
14,4 kbit/s
14,4 kbit/s
TCH/F14.4
16 kbit/s
28,8 kbit/s
2X14,4 kbit/s
TCH/F14.4
TCH/F28.8
16 kbit/s
3... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 16.2.4 Handling of status bits X and SB | The X and SB bits shall be carried over the A interface in a multiframe structure as described in subclause 8.1.1.1 of 3GPP TS 04.21. SA bit is not carried over the A interface.
The handling of the status bits shall comply with the synchronisation procedures for transparent services which are as described in 3GPP TS 29... |
d584819bc08aaf1044fa432bfa99ac6d | 08.20 | 17 Frame Formats | Octet
Bit number
No.
0
1
2
3
4
5
6
7
0
0
0
0
0
0
0
0
0
1
1
D1
D2
D3
D4
D5
D6
S1
2
1
D7
D8
D9
D10
D11
D12
X
3
1
D13
D14
D15
D16
D17
D18
S3
4
1
D19
D20
D21
D22
D23
D24
S4
5
1
E1
E2
E3
E4
E5
E6
E7
6
1
D25
D26
D27
D28
D29
D30
S6
7
1
D31
D32
D33
D34
D35
D36
X
8
1
D37
D38
D39
D40
D41
D42
S8
9
1
D43
D44
D45
D46
D47
D48
S9
Fig... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.1 Bearer capabilities | |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.1.1 Bearer capabilities | The EDGE radio interface shall be designed to work in all typical GSM radio environments like rural area (RA), typical urban (TU) and an indoor environment. EDGE shall also work in a Hilly Terrain (HT) environment however the main focus is on channels with lower delay spread than HT, as specified in GSM05.05.
The peak ... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.1.1.1 Enhanced GPRS | EGPRS shall provide a range of bearer capabilities that depend upon the environment and user’s speed. The peak rate shall at least be:
EGPRS
Indoor/Low range outdoor
Urban/Suburban outdoor
Rural outdoor
EGPRS
384 kbps (48 kbps/timeslot)
384 kbps (48 kbps/timeslot)
144 kbps (18kbps/timeslot)
Speed
up to 10 km/h
up to 10... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.1.1.2 Enhanced CSD | ECSD shall provide a range of bearer capabilities (per time slot) that depend upon the environment and user’s speed. The peak rates should at least be:
ECSD/T
Indoor/Low range outdoor
Urban/Suburban outdoor
Rural outdoor
ECSD/T
32 kbps/timeslot *)
32 kbps/timeslot *)
-
Speed
up to 10 km/h
up to 100 km/h
-
Propagation c... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.1.2 Bearer service attributes | The same bearer service attributes used for GPRS and CSD should be used for EGPRS and ECSD. Some new bearer service parameters relevant to the radio interface may be needed. For EGPRS the same QoS classes should apply. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.1.3 Hand over/cell re-selection | The same hand over/cell re-selection mechanisms as for CSD/GPRS apply. Re-selection methods should allow the operator to optimise the service availability for EDGE users.
Seamless transition ECSD-> CSD -> ECSD and EGPRS classic->GPRS -> EGPRS classic.
Seamless transition from EGPRS Classic->EGPRS Compact->EGPRS Classic... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.2 Operational requirements | |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.2.1 Compatibility with services provided by present core networks | EDGE will enhance the GPRS and CSD service by providing higher data rates. That means, that EDGE will rely on underlying GSM functionality. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.2.2 Operating environments | The operational scenario for EDGE includes international operation across various EDGE radio operating environments (850/900/1800/1900 MHz bands). Further, EDGE will support a variety of services with a range of bit rates. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.2.3 Radio Access network planning | EDGE should not require a modification of actual frequency/coverage planning defined for GSM air interface when introduced. Frequency/coverage re-planning may be used to maximise the throughput in the system.
An EDGE network shall support at least 4/12, 3/9 and 1/3 frequency reuse patterns. EGPRS Compact shall support ... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.2.4 Operators | All GSM900/1800/1900 operators should be able to deploy EDGE without licensing problems. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.3 Efficient spectrum usage | |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.3.1 Spectral Efficiency | The spectral efficiency of EDGE should be significantly higher than in GSM.
The radio interface should be designed to maximise spectral efficiency.
EGPRS Compact shall be possible to implement in less than 1 MHz initial spectrum. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.3.2 Spectrum utilisation | It should be possible to use EDGE in all GSM bands.
It should be possible to mix EDGE and non EDGE timeslots on the same carrier.
If simultaneous EDGE and non EDGE operation in the same time slot is required or not is for further investigation.
If EDGE is used on the BCCH carrier, it should not have any impact on BCCH ... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.3.3 Coverage/capacity | The peak service rates may be provided only in a limited coverage area. Link adaptation shall provide a mechanism to have a smooth degradation of the service rates for the outer cell areas.
EDGE should be designed to maximise the area where high data rates can be achieved.
SMG2 should define appropriate evaluation crit... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.3.4 Evolution requirements | With EDGE several 3rd generation services can be provided in GSM. The technical parameters for EDGE should allow an evolution for coverage and capacity, as well as provisioning of future 3rd generation services. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.3.4.1 Coverage evolution | The radio coverage for the EDGE may be:
- contiguous coverage;
- island coverage;
- spot coverage.
EDGE should be sufficiently flexible to support a variety of initial coverage configurations and facilitate coverage evolution. Coverage can be increased by deploying cell planning parameters optimised for EDGE usage and/... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.3.4.2 Capacity evolution | EDGE should facilitate the implementation and use of appropriate capacity improvement techniques, if applicable, in the various radio operating environments.
EDGE should not prevent capacity improvements, e.g. adaptive antennas, advanced power control, efficient resource allocation etc. It is desirable that the EDGE do... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.4 Complexity / Cost | |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.4.1 Mobile complexity and cost | Hand portable and PCMCIA card sized EDGE terminals should be optimised in terms of size, weight, operating time, range, effective radiated power and cost/performance ratio. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.4.2 Network complexity and cost | The cost/performance ratio of development and equipment should be kept at a reasonable level. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.4.3 Mobile Station / Base Station types | The EDGE standard should support multislot operation for ECSD and EGPRS. It should be possible to provide a variety of Mobile Station as well as Base Station types of varying complexity, cost and capabilities in order to satisfy the needs of different types of users. The number of mobile classes should though be minimi... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.5 Requirements from bodies outside SMG | |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.5.1 Electromagnetic compatibility | The modulation characteristics have to be such that the degree of interference caused to other equipment is not higher than in today's systems. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.5.2 RF Radiation effects | EDGE shall be operative at RF emission power levels which are in line with the recommendations related to electromagnetic radiation. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.5.3 Security | The EDGE radio interface should be able to accommodate at least the same level of security as the GSM radio interface does. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.6 Co-existence with other systems | A GSM system with EDGE should be capable to co-exist with a GSM system without EDGE deployment within the same or neighbouring band as well on neighbouring time slots. Furthermore should the performance of GSM channels without EDGE not be worsened by the fact that the neighbouring channel is a GSM channel with EDGE and... |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.7 Further Work Areas | |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.7.1 Services coordination | Possibility to have same or similar services in EDGE as in UMTS needs to be investigated. Investigation of hand-over between GSM and UMTS is necessary. |
12a04a2241e852c6515b51dc33bf8149 | 10.59 | 14.7.3 Measurements in existing GSM | It should be studied if there is a need to modify existing measurements for EDGE or other work items.
History
Document history
16th February 1998
First draft
20th February 1998
Update after Joint SMG1,2,3 & 4 EDGE workshop in Helsinki
27th April 1998
Update after SMG1 and SMG2 WPB#4
25th May 1998
Update after SMG4 and ... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 1 Scope | The purpose of this Technical Report is to study the feasibility of a core network CAMEL server controlling voice services carried by VoIP within a GPRS PDP Context using:
1) An architecture based on ITU-T, H.323 family of recommendations.
2) An architecture based on IETF SIP specifications. |
14ce710049a3c611ebb26f3972649957 | 21.978 | 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.
- Fo... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 3 Introduction | The GSM CAMEL feature for control of operator specific services when roaming has evolved over a number of years and work on the latest Phase (Phase 3) is planned for completion as part of Release '99. Work in other 3GPP groups, particularly S2, is focused on developing a reference architecture for an all IP PLMN. One ... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 4 Definitions and Abbreviations | BCSM Basic Call State Model
CAMEL Customised Application for Mobile networks Enhanced Logic
CAP CAMEL Application Protocol
CSI CAMEL Subscriber Information
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
HLR Home Location Register
IPSSF Internet Protocol Service Switching Function
MAP Mobile Applicatio... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 5 Proposition | An overall objective for this feasibility study is to demonstrate that CAMEL control of VoIP services in 3G networks can be readily specified and implemented by adapting standards and software used in 2G networks. This approach leads to services that function the same when a user roams between 2G and 3G networks, simpl... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 5.1 Relationship with Architecture work in S2 | Ongoing architecture work in S2 for 3G is documented in TS 23.121 and in the Technical Report on 'Architecture for an all IP network' (TR 23.922 V1.0.0). The work in this CAMEL control of VoIP services FTR is intended to aid/complement S2 work by analysing feasibility at a somewhat lower level of abstraction, focusing ... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 6 Service Requirements | In 3GPP, SA1 has responsibility for the definition of service requirements. Requirements for Release '00 are at a very early stage of development. When considering feasibility it is very useful to have in mind the services that a 3G network may be required to support. This section lists many example 2G network voice se... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 6.1 Basic Services | Example basic services that may require CAMEL control in a 3G network:
- Speech
- Emergency calls
- Low bit rate data
- Medium bit rate data
- High bit rate data
- High quality audio
- Low bandwidth video
- High bandwidth video |
14ce710049a3c611ebb26f3972649957 | 21.978 | 6.2 Supplementary Services | Example 2G supplementary services that may require CAMEL control in a 3G network:
- Operator determined barring
- User defined barring
- Call screening
- Call deflection
- Call forwarding unconditional
- Call forwarding on busy, no reply and not reachable
- Call waiting
- Call hold
- Call transfer
- Calling number iden... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 6.3 Operator Specific Services | Example 2G operator specific services that may require CAMEL control in a 3G network:
- Short number dialling
- Prepay
- VPN |
14ce710049a3c611ebb26f3972649957 | 21.978 | 6.4 Other Services | Example services not listed in the ‘Basic Services’, ‘Supplementary Services’ or ‘Operator Specific Services categories that may require CAMEL control in a 3G network:
- Lawful interception
- Voice group-call service
- Voice broadcast service
- SMS
- Fax
- ASCI
- MExE
- Location Services
- SoLSA |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7 H.323 Solution | |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.1 Description | ITU-T defines a family of recommendations known as H.323 for multimedia communications over packet based networks. The majority of VoIP products available today support H.323.
Figure 2: H.323 Environment
The H.323 environment is illustrated in Figure 2. A 'terminal' is a network endpoint that provides real-time, voice... |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.2 Architecture | |
14ce710049a3c611ebb26f3972649957 | 21.978 | 7.2.1 Introduction | This section of the report provides information flows that illustrate simple MO and MT calls with CAMEL interactions. It is based upon an architecture that proposed in references [6] and [7]. The objective is to provide further understanding of the proposed architecture and to further progress the work in the feasibili... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.