Showing posts with label Architecture. Show all posts
Showing posts with label Architecture. Show all posts

4G Heterogeneous Networks General Architecture



The 4G Mobile communications will be based on the Open Wireless Architecture (OWA) to ensure that the single terminal can seamlessly and automatically connect to the local high-speed wireless access systems when the users are in the offices, homes, airports or shopping centers where the wireless access networks (i.e. Wireless LAN, Broadband Wireless Access, Wireless Local Loop, HomeRF, Wireless ATM, etc) are available. When the users move to the mobile zone, the same terminal can automatically switch to the wireless mobile networks (i.e. GPRS, W-CDMA, cdma2000, TD-SCDMA, etc.).
The advantages of this converged wireless communications are:
  1. Spectrum efficiency is greatly increased.
  2. Highest Data rate to the wireless is mostly ensured.
  3. Best sharing of the network resources and channel terminal utilization.
  4. Optimally manage the service quality and multimedia applications.
The modules within the architectural framework should be able to incorporate the following high-level mobility issues (Figure 1):
  • Users: This focuses on the movement of user, and allows user access to his/her home network while on the move, which involve the provision of personal communication.
  • Terminals: This allows the provision of services at any time and anywhere. Terminal mobility allows mobile clients to roam across geographic boundaries of wireless networks. The greatest challenge in providing terminal mobility within a 4G Infrastructure is to locate and update the locations of the terminals in various systems.
  • Networks: Network mobility is the ability of the network to support roaming of an entire subnet work, structured or ad hoc.
  • Applications: Mobile application should refer to a user's profile so that it can be delivered in a way most preferred by the subscriber, such as context based personalized services.
 
Figure 1: Mobility dimensions
The incorporation of new functions into existing mobility protocols and mechanisms does not appropriately solve the demands of future communication scenarios. Therefore a new‘Mobility Architecture’ needs to be defined, based on the following principles: Diversity, Harmonization among layers, Legacy Awareness, Concept of mobile entities and Naming and name management.
With the acceleration of technology, there is competition among commercial houses to create significant growth and they are looking for various technological solutions for Fourth Generation Mobile Communication Systems

Solutions and Recommendations | WIRELESS ROUTER ARCHITECTURE

In the proposed architecture, the wireless routers (WRs) situated in different cells perform message routing in addition to the traditional Base Station (BS) functions. In fact, the traditional functions of the base stations, BSC (Base Station Controller), and MSC (Mobile Switching Center) in the legacy systems are lumped together and distributed across various WRs in the new wireless architecture. Figure 1 is a very high level depiction of various inter-router links as well as the control links between the proposed WRs, and the traffic and control interfaces. The inter-router links include: i) wireless specific virtual tunnels i. e. Multi Protocol Label Switch (MPLS) paths based on IP packets, ii) RSVP (Resources Reservation Protocol)/LDP (label Distribution Protocol) signaling channel, iii) routing message channel, iv) wireless specific virtual channel to carry MPLS based radio frames, and v) one or more wireless-specific control channels for call setup and maintenance including a signaling channel for usage by any signaling protocol (SP) such as extended RSVP and a routing channel for usage by any radio routing protocol (RRP) such as extended OSPF (Open Shortest Path First), RIP (Routing Information Protocol), or BGP (Boarder Gateway Protocol). The bold and dashed lines in the figure indicate the data and control channels, respectively.


Figure 1: Proposed wireless router links to peer routers and various control interfaces
 
For supporting wireless traffic services, the WRs access traffic and control interfaces that include media gateway controllers, WAP (Wireless Application Protocol) servers, policy management servers, call agent controllers, mobility managers, and AAA (Authentication, Authorization, and Accounting) servers. WRs communicate with these interfaces through MGCP (Media Gateway Controller Protocol), COPS (Common Open Policy Service), and other suitable protocols.

The WR architecture proposed herein facilitates wireless-access technology (e.g. CDMA or TDMA) independent network routing with the help of wireless interfaces to disparate wireless peripherals as shown in Figure 2, and hence is pivotal to an all-IP (Internet Protocol) radio access network (RAN) that seamlessly inter-works with the backhaul IP network with interfaces to various network peripherals. For communication with the backhaul networks at the other end, the WR includes wire-line interfaces to various network peripherals as well. At the heart of the WR lies the traffic control with various modules as follows: i) Quality of Service (QOS) engine for traffic conditioning and effective management of transmission resources, ii) Selection and Distribution Unit (SDU), iii) Central Processing Unit (CPU), iv) Call Processor, v) Timing Unit for synchronization purpose, vi) Communication Module with various traffic-controller interfaces to gateways, services, policy managers, IP routers, base-stations, call agents, and other remote nodes and resources, vii) Power and Interference Manager, viii) Radio resources Manager, ix) Mobility Manger, X) Packet Classification Unit, and xi) Security (IP SEC) Module.


Figure 2: Internal structure of the proposed wireless router
 
In the traditional mobile networks, an SDU is placed centrally at the Base Station Controller (BSC) to manage the call processing at a number of base stations. It selects the best frame from a number of incoming radio frame instances from the mobile via different base-stations (BSs) for onward transmission to the intended destination through backhaul network, and distributes similarly the messages received from the backhaul to the target mobiles. Based on the quality of the frames received from different base-stations, an SDU also manages soft-handovers (that is, call redirections from one BS to the other). In our architecture, BS is replaced by the more versatile WR module. Additionally, it incorporates an innovative concept of a distributed SDU with every WR housing an SDU. These distributed SDUs in the present architecture facilitate distribution of intelligence, and switching and control functionality to individual cell sites.

The main advantage here is that the radio frames need not be transmitted to the BSC over the backhaul links. A very efficacious use of the backhaul network bandwidth this way, in turn, results tremendous cost savings for the customer. Additionally, this approach helps in averting traffic congestion. Common switching points leading to delayed/dropped traffic are reduced if not altogether eliminated. However, these advantages could be realized only by effective inter-router communication methods for mobility management by call redirection (soft handoff) and MPLS path reconfiguration as the mobile device transitions between cells. The proposed innovation should also be implemented without compromising the quality of service (QOS). In the following subsections, we describe the mechanisms for soft handoff and QOS in the proposed architecture.

ARCHITECTURE OF 4G


Add a note hereAt this moment it is very difficult to predict the exact architecture of the 4G mobile communication system. Looking at the present scenario of the 3G and the likes of WiMAX etc. we can only predict the probable architecture of the fourth generation architecture. However in labs and on an experimental basis there are already some of the architectures available for the 4G. Of course, with the advances of the technology in both the UMTS and the CDMA 2000 and their evolved versions the architectures will be updated. Here some of the experimental architectures and some of the predicted models of the 4G architecture have been presented.

Add a note here1. The OSI Model for 4G
Add a note hereThe best way to represent any communication system architecture is the OSI model, and here the probable OSI model of 4G model has been presented (Figure 1) with the understanding that may be some differences in specific future 4G systems. The OSI model of 4G can properly explain the different operations of and the underlying technologies. It is similar to the various layers found in the OSI model of internet, but as a result of basic differences they are arranged in a different fashion and some of the layers are absent. Here the physical layer and the MAC (medium access control sublayer) are quite important.


Add a note here 
Figure 1: The OSI model of4G
Add a note hereThe OSI model of 4G depicts the different layers and their functions in a proper sequence. The physical layer, or bottom one, deals with the signals in the OFDM format. Above it lies the transmission convergence sublayer (CS), which is between the physical layer and MAC layer. On top of that layer is the MAC layer, which has three sublayers. The uppermost layer of MAC, the convergence sublayer, supports both ATM services as well as IP based services. In 4G the MAC layer at the base station (BS) is responsible for the allocation of bandwidths to different users both in the uplink and downlink. MS only occasionally takes the control of bandwidth allocations when it has multiple sessions or it has connections with the BS. This is quite different from other services and ensures better quality of service. Most of the services of 4G would be IP based; as a result the optimization and QoS related improvements are done as per the IPv6 configuration and structure. ATM service facilities are also provided for the compatibility with other existing networks.
Add a note hereWhen we look at the first release of WiMAX standard in 2001, the IEEE 802.16 standard proposed applications for a fixed wireless scenario in licensed frequency bands in the range between 10 and 66 GHz, where the use of directional antennas were mandatory to obtain satisfactory performance figures. But difficulties were encountered in metropolitan sub-areas where line-of-sight operations cannot be ensured due to the presence of obstacles, buildings, towers etc. Thus, subsequent amendments to the standard (IEEE 802.16a and IEEE 802.16-2004) have extended the 802.16 air interface to non-line-of-sight applications in licensed and unlicensed bands in the 2-11 GHz frequency range. Additionally, after the revision of IEEE standard document 802.16e, some necessary mobility support will be provided. Revision of IEEE 802.16f is intended to improve multi-hop functionality, and 802.16g is supposed to deal with efficient handover and improved QoS. This revision also increased the range of WiMAX technology; according the WiMAX forum, it can reach up to a theoretical 50 Km coverage radius and achieve data rates up to 75 Mb/s. Of course, actual IEEE 802.16 equipment is still far from these performance figures, but it has been proved that with the use of MIMO antennas and OFDM based technologies the data rates can be made really high. For example, with 5 MHz bandwidth, a data rate of 18 MBPS is possible using this advanced MIMO technique. After looking at the success of these technologies in WiMAX, the 4G development research groups are ready to follow the same path. Most of the settings of 4G would be according to the IEEE 802.16m standards, and the new MAC layer bridging is waiting for some amendments of IEEE 802.16k.
Add a note hereDuplexing or bidirectional data transmission is provided by means of either Time Division Duplexing (TDD) or Frequency Division Duplexing (FDD). In TDD, the frame is divided into two sub-frames, one devoted to downlink and the other to the uplink. A Time-Division Multiple Access (TDMA) technique is used in the uplink subframe. The BS is in charge of assigning bandwidth to the SSs, while a Time Division Multiplexing (TDM) mechanism is employed in the downlink sub-frame. In case of FDD, the uplink and downlink sub-frames are concurrent in time, but are transmitted on separate carrier frequencies. There are supports for half-duplex FDD SSs, at the expense of some additional complexity. Each subframe is divided into physical slots. Each TDM/TDMA burst carries MAC Protocol Data Units (PDUs) containing data towards SSs or BS, respectively. The transmission convergence sublayer operates on top of the physical layer and provides the necessary interface with the MAC. This layer is specifically responsible for the transformation of variable length MAC PDUs into fixed length physical blocks. Here in 4G, the RR and the MM layers are different from the GSM RR and MM layers. Here the use of MIMO enabled antennas can manage the resources quite efficiently.
Add a note hereThere is a big demand for secure data transmissions, which has led to the native inclusion of a privacy sub-layer in 4G (which is very similar to the WiMAX), at the MAC level. There are some well-organized protocols to take care of the security related processes. Those protocols are responsible for encryption/decryption of the packet payload, according to the rules defined in the standard. IEEE 802.16 uses a wireless medium for communications, and one of its main targets of the MAC layer is to manage the resources of the radio interface in an efficient way, while ensuring that the QoS levels negotiated in the connection setup phase are fulfilled. Of course the IEEE 802.16 MAC protocol is connection-oriented and is based on a centralized architecture. There is a need for segmentation and resemblance of frames for proper security monitoring of all the packets. The common part sublayer is responsible for this segmentation and the resemblance of MAC service data units (SDUs), the scheduling and the retransmission of MAC PDUs. The common part sublayer also provides the basic MAC rules and signaling mechanisms for different system access, bandwidth allocation and connection maintenance. The core function of the protocol is bandwidth requests/grants management. A SS may request more bandwidth, by means of a MAC message, to indicate to the BS that it needs (additional) up-stream bandwidth. The request of bandwidth is processed on a per-connection basis to allow the BS uplink scheduling algorithm, to consider QoS-related issues in the bandwidth assignment process. The bandwidth granting methods as per the original 2001 standard encompassed two operational modes: Grant per Connection (GPC) and Grant per Subscriber Station (GPSS). Later in the 2004 release, the term "grant" refers only to the GPSS mode. Whereas, in the GPC mode, the BS allocates different scalable bandwidths to individual destinations. With this revision, BS got the control of all the centralized mechanisms, with all the intelligence placed in the BS, while the SSs act as merely passive stations. On the other hand the bandwidth, in the GPSS mode, is granted to each individual SS, which is then in charge of allocating the available resources to the currently active flows.
Add a note hereConvergence sublayer (CS) is the uppermost sublayer of the MAC layer. The CS associates the traffic coming from the upper layer with an appropriate Service Flow (SF) and Connection Identifier (CID) which gives the idea about its destination. The CS also provides payload header suppression when some entity is sent and reconstruction at the receiving entity. CS delivers the resulting CS PDU to the MAC Common Part Sublayer to confirm the negotiated QoS levels.
Add a note hereThe 4G standard defines two different Convergence Sublayers for mapping services to and from IEEE 802.16 MAC protocol like the WiMAX. The ATM convergence sublayer is there solely for ATM traffic, while the packet convergence sublayer is specific for mapping packet-oriented protocol suites, such as IPv4, IPv6, Ethernet and Virtual LAN etc. The IP Sublayer is as the name suggests is there to provide all IP enabled services. The classification of IP traffic and ATM traffic is done in the CS sublayer. However the system's IP architecture will be based completely on IPv6.

Network Architecture and Protocols | LTE for 4G

Add a note hereThe LTE network architecture is designed with the goal of supporting packet-switched traffic with seamless mobility, quality of service (QoS) and minimal latency. A packet-switched approach allows for the supporting of all services including voice through packet connections. The result in a highly simplified flatter architecture with only two types of node namely evolved Node-B (eNB) and mobility management entity/gateway (MME/GW). This is in contrast to many more network nodes in the current hierarchical network architecture of the 3G system. One major change is that the radio network controller (RNC) is eliminated from the data path and its functions are now incorporated in eNB. Some of the benefits of a single node in the access network are reduced latency and the distribution of the RNC processing load into multiple eNBs. The elimination of the RNC in the access network was possible partly because the LTE system does not support macro-diversity or soft-handoff.

Add a note hereWe discuss network architecture designs for both unicast and broadcast traffic, QoS architecture and mobility management in the access network. We also briefly discuss layer 2 structure and different logical, transport and physical channels along with their mapping.


All the network interfaces are based on IP protocols. The eNBs are interconnected by means of an X2 interface and to the MME/GW entity by means of an S1 interface as shown in Figure 1. The S1 interface supports a many-to-many relationship between MME/GW and eNBs.


Figure 1: Network architecture.

Add a note hereFigure 1: Network architecture.
Add a note hereThe functional split between eNB and MME/GW is shown in Figure 2. Two logical gateway entities namely the serving gateway (S-GW) and the packet data network gateway (P-GW) are defined. The S-GW acts as a local mobility anchor forwarding and receiving packets to and from the eNB serving the UE. The P-GW interfaces with external packet data networks (PDNs) such as the Internet and the IMS. The P-GW also performs several IP functions such as address allocation, policy enforcement, packet filtering and routing.

Figure 2.2: Functional split between eNB and MME/GW.

Add a note hereFigure 2.2: Functional split between eNB and MME/GW.
Add a note hereThe MME is a signaling only entity and hence user IP packets do not go through MME. An advantage of a separate network entity for signaling is that the network capacity for signaling and traffic can grow independently. The main functions of MME are idle-mode UE reachability including the control and execution of paging retransmission, tracking area list management, roaming, authentication, authorization, P-GW/S-GW selection, bearer management including dedicated bearer establishment, security negotiations and NAS signaling, etc.

Add a note hereEvolved Node-B implements Node-B functions as well as protocols traditionally implemented in RNC. The main functions of eNB are header compression, ciphering and reliable delivery of packets. On the control side, eNB incorporates functions such as admission control and radio resource management. Some of the benefits of a single node in the access network are reduced latency and the distribution of RNC processing load into multiple eNBs.

Add a note hereThe user plane protocol stack is given in Figure 3. We note that packet data convergence protocol (PDCP) and radio link control (RLC) layers traditionally terminated in RNC on the network side are now terminated in eNB.

Figure 3: User plane protocol.

Add a note hereFigure 3: User plane protocol.
Add a note hereFigure 4 shows the control plane protocol stack. We note that RRC functionality traditionally implemented in RNC is now incorporated into eNB. The RLC and MAC layers perform the same functions as they do for the user plane. The functions performed by the RRC include system information broadcast, paging, radio bearer control, RRC connection management, mobility functions and UE measurement reporting and control. The non-access stratum (NAS) protocol terminated in the MME on the network side and at the UE on the terminal side performs functions such as EPS (evolved packet system) bearer management, authentication and security control, etc.


Add a note hereFigure 4: Control plane protocol stack.
Figure 4: Control plane protocol stack.

Add a note hereThe S1 and X2 interface protocol stacks are shown in Figures 5 and 6 respectively. We note that similar protocols are used on these two interfaces. The S1 user plane interface (S1-U) is defined between the eNB and the S-GW. The S1-U interface uses GTP-U (GPRS tunneling protocol – user data tunneling) on UDP/IP transport and provides non-guaranteed delivery of user plane PDUs between the eNB and the S-GW. The GTP-U is a relatively simple IP based tunneling protocol that permits many tunnels between each set of end points. The S1 control plane interface (S1-MME) is defined as being between the eNB and the MME. Similar to the user plane, the transport network layer is built on IP transport and for the reliable transport of signaling messages SCTP (stream control transmission protocol) is used on top of IP. The SCTP protocol operates analogously to TCP ensuring reliable, in-sequence transport of messages with congestion control . The application layer signaling protocols are referred to as S1 application protocol (S1-AP) and X2 application protocol (X2-AP) for S1 and X2 interface control planes respectively.

Add a note hereFigure 5: S1 interface user and control planes.
Figure 5: S1 interface user and control planes.


Add a note hereFigure 6: X2 interface user and control planes.
Figure 6: X2 interface user and control planes.


Related Posts Plugin for WordPress, Blogger...