Skip to main content

4G Technology!!

4G also called as Fourth-Generation Communications System, is a term used to describe the next step in wireless communications. A 4G system can provide a comprehensive IP solution where voice, data and streamed multimedia can be provided to users on an "Anytime, Anywhere" basis. The data transfer rates are also much higher than previous generations.

The main objectives of 4G are:

1)4G will be a fully IP-based integrated system.

2)This will be capable of providing 100 Mbit/s and 1 Gbit/s speeds both indoors and outdoors.


3)It can provide premium quality and high security.

4)4G offer all types of services at an affordable cost.

4G is developed to provide high quality of service (QoS) and rate requirements set by forthcoming applications such as wireless broadband access, Multimedia Messaging, Video Chat, Mobile TV, High definition TV content, DVB, minimal service like voice and data, and other streaming services.


4G technology allow high-quality smooth video transmission. It will enable fast downloading of full-length songs or music pieces in real time.


The business and popularity of 4Gmobiles is predicted to be very vast. On an average, by 2009, this 4Gmobile market will be over $400B and it will dominate the wireless communications, and its converged system will replace most conventional wireless infrastructure.



Comments

Post a Comment

Popular posts from this blog

Configuring Failover and Load Balancing with HAproxy using Keepalived

Network Scenario: LB1: 192.168.10.10 LB2: 192.168.10.11 Virtual IP: 192.168.10.12 APP_Server1: 192.168.10.20 APP_Server2: 192.168.10.21 Load Balancing: STEP 1 - Install HAProxy: HAProxy package is available under default yum repository for CentOS, Redhat systems. Use the following yum package manager command to install HAProxy on your system.   # yum install haproxy   STEP 2 - Configure HAProxy : Update your HAProxy configuration file /etc/haproxy/haproxy.cfg as per your requirement, You may also use below given configuration file as an example of setup and modify it. Keep the config file same of both servers i.e. LB1 and LB2.   ----------------------------------------------------------------------------------------------------------- global         log /dev/log    local0         log /dev/log    local1 notice     ...
2 comments
Read more

ElasticSearch Clustering and Backups

ElasticSearch Installation: The version we want to install is 2.x (latest sub version of 2). First we have to install java on centOS machine with following command: sudo yum install java-1.8.0-openjdk.x86_64 Install Public Signing Key:   rpm --import https://packages.elastic.co/GPG-KEY-elasticsearch Create new repo in your /etc/yum.repos.d/ directory. For example I have created elasticsearch.repo here. /etc/yum.repos.d/elasticsearch.repo -------------------------------------------------------------------------------------------- [elasticsearch-2.x] name=Elasticsearch repository for 2.x packages baseurl=http://packages.elastic.co/elasticsearch/2.x/centos gpgcheck=1 gpgkey=http://packages.elastic.co/GPG-KEY-elasticsearch enabled=1 --------------------------------------------------------------------------------------------- Now Elasticsearch 2.x will avilable for installation using yum   yum install elasticsearch After installation enable the service a...
Post a Comment
Read more

HAProxy automatic failover

HAProxy automatic failover HAProxy is a TCP load balancing tool with some useful features, including ACLs and SSL termination support. I’ve been using it for a while now on a number of load-balanced sites where scalability is key. What I haven’t yet looked at, however, is automated failover capabilities. My aims were simple: If a server fails, stop using it. If said server starts working again (i.e. because the problem is fixed) start using it again. If all servers in the load balancer pool fail, serve a temporary static page from another location. But first: Some basic HAProxy concepts HAProxy as a load balancer is fairly simple, and works on the basis of defined frontends and backends. A frontend is simply an IP and port declaration that you want the load balancer to listen on. A backend is the set of servers that requests to a frontend are sent to. Your HAProxy configuration lists the frontends and their respective backends, as well as the load balancing algorithm ...
Post a Comment
Read more