Report itu-r m. 2038 Technology trends


Robust header compression



Download 490.99 Kb.
Page25/36
Date31.01.2017
Size490.99 Kb.
#13092
1   ...   21   22   23   24   25   26   27   28   ...   36

2.1 Robust header compression


IP header compression is a technique to significantly reduce the size of the IP header while maintaining the header information contents 100%. Several compression schemes exist in today’s Internet. However, for the mobile environment these schemes are not enough since they rely on very low header loss rate. In the mobile environment with fairly high loss rate, more robust header compression is needed. This requirement has been acknowledged by IETF in the ROHC WG that has developed a robust header compression scheme an RFC.

2.2 Signalling compression


The signalling needed for all-IP is envisaged to consist of SIP/SDP signalling which are not optimized for mobile environment in the sense that it is ASCII based. This leads to excessive signalling delays and loss of performance. Signalling compression is therefore essential in order to successfully support all-IP services.

3 Reuse of Internet technologies in the radio access networks


Although the radio access networks of the existing IMT 2000 technologies are to a large extent using other means of transport between their internal nodes than IP transport, work is ongoing in order to be able to use IP the transport technology. It is essential that the introduction of IP as transport technology in the radio access network does not degrade operability, performance and end-to-end QoS. The necessary mechanisms for IP transport between nodes in a radio access network are being developed for the ongoing enhancements of IMT 2000. Especially IPv6 is considered.

4 IP-based RAN

4.1 Architecture and transport network

4.1.1 Wireless access technology independence


– IP-based RAN shall at least support the current 2G and 3G radio technologies such as W CDMA and cdma2000. This requirement shall be based on the support of the complete backward compatibility and inter-operability. This requirement also makes sure that

IP based RAN architecture supporting UTRA can accommodate IP-based RAN architecture supporting cdma2000 just by replacing the radio-specific function from UTRA to IP-based cdma2000.

– IP-based RAN architecture may be flexible to support another non-cellular wireless technology, e.g. Wireless LAN and Bluetooth. This requirement also is based on the flexible architecture to support the radio-specific function with plug and play operation.

– IP-based RAN shall support inter-working and inter-operation to support the handoff among different wireless access technologies.


4.1.2 Backward compatibility


– IP-based RAN architecture and associate protocol set shall support the backward compatibility with the current RAN architecture from the ground up.

From the service perspective, no service and performance degradation are expected in IP based RAN comparing to the current RAN architecture. This requirement shall need some criteria to verify the backward compatibility.

– IP-based RAN architecture and associate protocol set shall provide at least the equivalent functionality to the current RAN architectures. The main changes in IP-based RAN architecture comparing to the current RAN architecture shall be easily identified.

4.1.3 Interoperability with legacy (2G/3G) networks and mobile terminals


– IP-based RAN architecture shall support interoperability between current 2G/3G core network (including GSM MAP, ANSI-41 Core Network) and IP-based RAN.

– IP-based RAN architecture shall support interoperability between current 2G/3G radio access networks and IP-based RAN.

– IP-based RAN architecture shall also provide support for legacy (2G/3G) mobile terminals.

4.1.4 Forward compatibility


– IP-based RAN architecture and associate protocol set shall allow the forward compatibility with the architecture accommodating the new radio technologies.

– IP-based RAN architecture shall easily accommodate any change to be expected by introducing new services (e.g. IP broadcast/multicast services).


4.1.5 Interoperability with all IP network and IP-based mobile terminals


– IP-based RAN architecture shall support the interoperability between the All IP core network and IP-based RAN.

– IP-based RAN architecture shall support the interoperability between the next generation following 2G/3G radio access networks and IP-based RAN.

– IP-based RAN architecture shall also provide support for IP-enabled mobile terminals.

4.1.6 Layered independent architecture


– IP-based RAN architecture shall support the layered architecture.

– IP-based RAN architecture shall support the separation among the user plane function, the control plane function, and the transport plane function.


4.1.7 Open interface support


– IP-based RAN architecture shall support open interfaces between any network entities in IP-based RAN that may be implemented by operators/ISPs and manufacturers as separate systems, subsystems, or network entities.

– IETF protocols shall be considered and adopted in these open interfaces wherever possible. For example, mobile IP mechanism can be another alternative for IP mobility in the RAN.


4.1.8 QoS support


– IP-based RAN architecture shall support the means to enable end-to-end QoS at least within RAN scope.

– IP-based RAN architecture shall satisfy the policy-based QoS architecture. This requirement can raise the issue, where the policy enforcement point and the policy decision point are.

– The resolution of QoS in IP-based RAN shall be consistent with the edge-to-edge (ETE) QoS on the core network level.

– IP-based RAN architecture should be capable of simultaneously supporting multiple levels of static QoS (negotiation of parameters before the session setup) as well as dynamic QoS (negotiation of parameters while the session is in progress) including in handoff scenarios.

– IP-based RAN architecture shall support the QoS enabled routing/handoff procedure. That is to say, the best selection of the routing path/handoff path satisfying the QoS required by the user shall be possible.

– IP-based RAN architecture shall support the configuration with load balancing for supporting the different level QoS requirement per user.

– IP-based RAN architecture shall support IPv6 enabled QoS resolutions.

– IP-based RAN architecture may support IPv4 enabled QoS resolutions.


4.1.9 IP transport


– IP-based RAN architecture shall transport bearer and control/signalling traffic based on IP technology.

– IP transport in the RAN shall be independent of the L1, L2 technology.

– IP-based RAN architecture shall support IPv6/IPv4 addressing mechanism.

4.1.10 Distributed dynamic configuration


– IP-based RAN architecture shall support the multiple dynamic configuration between functional entities. For example, the Node B functionality can select an appropriate RNC functionality for satisfying the QoS and the robustness (non-drop) during the call.

– IP-based RAN architecture shall support the distributed radio control and bearer control functions.

– IP-based RAN architecture shall support the distribution of cells dependent radio and bearer control functions towards the radio access points.

4.1.11 Radio resource management


– IP-based RAN architecture shall support the efficient radio resource management (allocation, maintenance, and release) in order to satisfy the QoS required by the user and the Policy required by the operator.

– IP-based RAN architecture shall support the function to optimize and negotiate the radio resource among the different wireless access technologies that are supported.


4.1.12 Performance


– The performances in IP-based RAN architecture regarding to link utilization, QoS, call drop rate, easy handoff, and so on shall be equal to or greater than those in the current RAN architecture.

– IP-based RAN architecture shall support increases in capacity without architectural impact.


4.1.13 Scaleable architecture


– IP-based RAN architecture shall provide network operators the ability to expand specific RAN function entities independently of other entities.

– IP-based RAN architecture shall allow network operators to gradually deploy network entities and expand their networks.


4.1.14 Security


– IP-based RAN architecture shall provide functions to protect its network resources and traffic from unauthorized access.

– IP-based RAN architecture shall handle multiple radio link authentication protocols (e.g., CAVE for IS-95, A5/1 for GSM).

– IP-based RAN architecture shall allow AAA to be present in the RAN or in the core network for access authentication, authorization.



Download 490.99 Kb.

Share with your friends:
1   ...   21   22   23   24   25   26   27   28   ...   36




The database is protected by copyright ©ininet.org 2024
send message

    Main page