Добавил:
linker.pp.ua Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
4g - LTE / Rel-08_description_20140924 / Rel-08_description_20140924.doc
Скачиваний:
77
Добавлен:
15.12.2018
Размер:
3.85 Mб
Скачать

25 Geran Studies

25.1 Study on a-interface over ip (aintip) uid_50589

Resources: GP

References

Document

Title/Contents

WID(s)

GP-071562

SID on A-interface over IP

Impacted Specifications

-

-

New Dedicated Specifications/Reports

TR 43.903

A-interface over IP Study (AINTIP)

Supporting Individual Members: China Mobile, Vodafone, Telecom Italia, Ericsson, Huawei, ZTE, Alcatel-Lucent, Nokia Siemens Networks, Motorola, Nortel Networks.

BSS (Base Station System) over IP is a trend in wireless network evolution, which can construct high bandwidth, high efficiency and low cost basic networks. BSS over IP involves Gb interface and A interface over IP (AINTIP). Gb interface over IP was standardized in Rel-4. For AINTIP, control plane signalling over IP (SIGTRAN) has been introduced in Rel-7 while certain features (e.g. MSC in Pool and Layered Architecture) require an intermediate signalling network for best performance.

During the specification in Rel-7 of A interface control plane signalling over IP, some operators expressed the concern that in order to take full advantage of IP based technologies the protocols of A interface user plane should be adapted for IP based transport. The IP based transport protocols provide a low cost intermediate network which is very attractive to the operators because CAPEX and OPEX can be significantly reduced.

AINTIP can also simplify the implementation of MSCs in a pool. Furthermore, UTRAN and more advanced RAN can use a common IP backhaul with GERAN.

This study shows it is feasible to introduce in 3GPP specifications the User Plane transport over IP for the A-interface (BSS – MGW interface). In particular it is possible to define a solution that, at the same time:

  • benefits from the flexibility of the IP transport on the A-interface,

  • improves bandwidth efficiency through the use of 3GPP Codecs on the A-interface,

  • allows to reuse installed Transcoder equipment,

  • allows to remove Transcoders from the BSS,

  • enables Transcoder Free Operation (TrFO) in the BSS,

  • maximizes the likelihood for end-to-end TrFO and therefore improves service quality vs. existing TDM-based BSS.

TR 43.903 made a detailed analysis of all requirements, except:

  1. All teleservices, bearer services, VGCS and supplementary services defined for GSM shall be supported on the BSC-MGW interface (Comment: Not studied in full detail, but no issues are expected.)

  2. GSM/AMR Codec adaptation shall be possible, e.g. due to overloading of the BSC or radio conditions. The GSM/AMR Codec adaptation delay shall be in the same order as in the current A-interface solution. (Comment: This requirement could be understood as "Codec Type" adaptation or as "AMR Codec Mode" adaptation. AMR Codec Mode adaptation is addressed under Requirement 18, see below. Codec Type adaptation has been studied in clause 7. Several feasible solutions have been identified.)

  3. End-to-end speech delay shall not be increased. Congestion in the IP transport may introduce additional delay; however the end-to-end delay shall not exceed the ITU G.114. (Comment: Not studied. This will be investigated further. It is, however, expected that the selected solution complies with this requirement.)

  4. It shall be possible to secure the BSC-MGW interface (see item e) below). (Comment: Not studied in full detail, but the same method as for SIGTRAN should be applicable.)

  5. Speech interruption times during handovers shall be in the same order as in the current TDM implementations (Comment: Not studied. This will be investigated further. It is, however, expected that the selected solution complies with this requirement.)

  6. The interaction of dynamic AMR Codec change and TrFO shall not degrade the overall quality of the speech in the case of MS to MS calls. (Comment: Not studied in full detail. No issues are expected because AMR Codec Mode adaptation for MS-to-MS calls in TrFO is already specified in TS 45.009.)

From the items under "further investigation" two items have not been addressed in detail:

  • Since IP transport is vulnerable to unauthorized intrusions, security aspects shall be investigated. (Comment: Not studied in full detail, but the same method as for SIGTRAN should be applicable.)

  • Support for GAN (Comment: Not studied in detail, no issues expected.)

The investigated solution allows smooth migration from legacy, TDM-based A-interface to new, IP-based A-interface.

Working Assumptions were formulated to guide the specification phase.

The investigated solution assumes support on the MSC-MGW- (Mc) and the MGW-MGW- (Nb) interfaces and therefore cooperation with TSGs CT and SA is required.

Spin-off UID_50591 Rel-8 Feature AoIP (A-interface over IP).

Соседние файлы в папке Rel-08_description_20140924