Policy and Charging Rules Function (PCRF) and how it reflects on mobile subscribers.

Policy and Charging Rules Function (PCRF) is the software node designated in real-time to determine policy rules in a multimedia network.^[1] 

As a policy tool, the PCRF plays a central role in next-generation networks.^[2] 

Unlike earlier policy engines that were added onto an existing network to enforce policy, the PCRF is a software component that operates at the network core and accesses subscriber databases and other specialized functions, such as a charging system, in a centralized manner.^[3] 

Because it operates in real time, the PCRF has an increased strategic significance and broader potential role than traditional policy engines. This has led to a proliferation of PCRF products since 2008.^[4] 

Mobile carriers need PCRF to dictate the rules their subscribers must follow when using the network. These rules could include data allowance, mobility and roaming to name but a few. The Policing and Charging function has been defined both for 3G and Long Term Evolution (LTE) scenarios by the 3rd Generation Partnership Project (3GPP) , and is typically done by a dedicated system with access to subscriber information databases, charging systems and mobile gateways. 

The PCRF is the part of the network architecture that aggregates information to and from the network, operational support systems, and other sources (such as portals) in real time, supporting the creation of rules and then automatically making policy decisions for each subscriber active on the network. Such a network might offer multiple services, quality of service (QoS) levels, and charging rules.^[5]

PCRF can provide a network agnostic solution (wire line and wireless) and can also enable multi-dimensional approach which helps in creating a lucrative and innovative platform for operators.^[6]

PCRF can also be integrated with different platforms like billing, rating, charging, and subscriber database or can also be deployed as a standalone entity.^[6] 

With this software component, mobile carriers have a real-time control on their subscribers as for example they can regulate the maximum permitted speed for data transmission of every registered mobile equipment.

I am facing a clear example of PCRF data speed limitation by my mobile carrier Tim Brazil, in fact my subscribed LTE (4G) line is being forcibly limited to work at a speed of 0.3Mbps in download and upload, whereas it could reach a medium rate of 20 Mbps or beyond, we know that theoretically 4G is capable of the following data speeds:

Peak download: 100 Mbps; Peak upload: 50 Mbps 

In the image below, the result obtained on April 9^th 2014 from my mobile equipment, a Nokia Lumia 920:

Nokia Lumia 710 aggiornamento firmware

Dopo due anni di onorato servizio, ho messo in pensione il mio fidato Nokia E63 e ho comprato uno dei nuovi Nokia Lumia con sistema operativo Windows Phone, per la precisione il modello Lumia 710.

In questo post non voglio fare recensioni di questo telefono perché ne esistono già diverse e ben dettagliate sulla rete, piuttosto voglio scrivere alcune impressioni personali e soprattutto spiegare come eseguire l'aggiornamento del firmware senza attendere quello ufficiale Nokia/Windows Phone, installabile tramite il software di gestione Zune

Il telefono che ho comprato (vivo in Brasile) ha  product code: RM-809 e inizialmente aveva il firmware: 1600.3013.8107.11502.

Utilizzando le applicazioni NaviFirm e Nokia Care sono riuscito ad aggiornarlo alla versione 1600.3030.8773.12120.

Con questa nuova release del firmware ho riscontrato migliorie generali di prestazioni e sopratutto un abbassamento del consumo della batteria del telefono che da molti utenti è stato segnalato come risultare estremamente alto.

Inoltre col nuovo firmware, viene resa disponibile la nuova caratteristica di condivisione Internet configurabile dal telefono, utile per trasformare il terminale in una sorta di hotspot Wi-Fi.

Maggiori dettagli delle migliorie introdotte con l'aggiornamento del firmware, potete vederli in questo video

Per quanto posso dire del telefono, funziona bene con grande fluidità e rapidità di risposta; quello che non mi è piaciuto è la mancanza di supporto completo del interfaccia Bluetooth in quanto mancano le funzioni per il trasferimento files e per la connessione con il modem interno. Queste funzioni a detta Windows Phone, forse saranno implementate attraverso un futuro aggiornamento del firmware

Per poter eseguire l'aggiornamento del firmware è necessario scaricare i seguenti applicativi:

Nokia Care Suite: Scaricabile da questo link

NaviFirm Plus: Scaricabile da quest link

Oltre al software suddetto, ovviamente avremo bisogno del cavo di connessione dati USB.

Una volta installato i due programmi nel nostro computer, dobbiamo installare i drivers per far riconoscere il vostro terminale dalla Suite di Nokia Care. A questo percorso “C:\Program Files (x86)\Nokia\Nokia Care Suite\Drivers” trovate i driver, installate quello identificato dal nome “WinUSB Drivers x64” o “WinUSB Drivers x86” in base alla versione del vostro sistema operativo.

A questo punto possiamo lanciare il NaviFirm per scoprire quale sia l'ultima versione disponibile del firmware per il nostro telefono.

Nel mio caso risultava essere appunto la 1600.3030.8773.12120 ma invece di scaricarla direttamente col NaviFirm ho proceduto in modo diverso da come pubblicato in altri blog che trattano di Nokia, utilizzando direttamente la suite Nokia Care, tramite l'opzione Product Support Tool tramite la quale è possibile scaricare direttamente l'aggiornamento avendo l'accortezza di scegliere il Product Code giusto.

Esempio:

Ammettiamo che il Product Code relativo all' ultimo aggiornamento su NaviFirm sia RM809_059M505 e che il Product Code effettivo del nostro telefono sia 059MQ08, ebbene dovremo impostare il primo ID 059M505 in Nokia Care Product Support Tool, in modo da scaricare tutti i files necessari.

Una volta che il download sarà completato, prima di "flashare" la ROM del telefono, dovremo semplicemente rinominare il Product Code di cui sopra con il rispettivo ID del nostro telefono in questi tre files:

• RM809_059MQ08_1600.3030.8773.12120_017.dcp
• RM809_059MQ08_1600.3030.8773.12120_017.vpl
• RM809_059MQ08_1600.3030.8773.12120_017_signature.bin

Per caricare il nuovo firmware nel nostro terminale da Nokia Care Suite, selezioniamo la voce Product Support Tool, nella barra in basso a sinistra selezionate la voce “Programming -> Refurbish” che dovrebbe avvisarvi della presenza di un aggiornamento.

Basterà avviare la procedura con il tasto Start per iniziare l'aggiornamento.

ATTENZIONE: Installando la nuova ROM il telefono sarà ripristinato, quindi assicuratevi di salvare tutte le informazioni contenute in esso sul computer prima di effettuare la procedura.

Come aggiornare JAVA su openSUSE

Da qualche tempo JAVA (Sun-Oracle) non è più scaricabile dai repository di openSUSE, perciò chi come me ha bisogno di installare questo software e soprattutto mantenerlo aggiornato, consiglio di seguire le istruzioni riportate in questo URL:

http://sites.google.com/site/easylinuxtipsproject/java-for-opensuse

Intel Data Centre CTO: Moore’s Law is far from over

Intel Data Centre CTO: Moore’s Law is far from over

New 22-nm Intel Ivy Bridge Chips 37% Faster Than Previous Generation, Use 50% Less Energy

New 22-nm Intel Ivy Bridge Chips 37% Faster Than Previous Generation, Use 50% Less Energy

A bit of customizations for GNOME 3

Well,

Today I would like to spent some words about the latest GNOME Desktop Environment release, the successor of the glorious GNOME 2.x branch: I'm talking about GNOME 3, which represents a real innovation in terms of D.E. concept.

I let everyone who were eventually still unaware about this Desktop Environment, which so far is the bigger concurrent of KDE (another Desktop Environment based on Qt libraries) to see directly about what I'm talking about.

Now let's move directly to show the extensions and minor customizations I made on my GNOME 3 which is currently my default D.E. on my openSUSE 11.4 64bits.

My small cosmetic additions here reported are nothing in comparison to the top level development existent behind The GNOME Project itself, as well as the knowledge enclosed behind the smaller gnome-extensions, like the ones I'm presenting here which have been realized by some smart developers and free software enthusiasts around the globe as Finnbarr P. Murphy.

I installed the following Murphy's gnome-shell extensions since as it is per default GNOME 3 shell in my opinion appears a bit "crude and with little usability":

1. activities button
2. application button
3. themeselector
4. workspaces menu

Gnome 3 in all its splendor :-)

Gnome-Shell extensions: Activity and Applications buttons

Gnome-Shell user panel

Gnome-Shell "Windows"

Gnome-Shell Theme Selector

Gnome-Shell Workspaces-Menu

Gnome-Shell Applications Button (details)

gnome-shell extensions (default directory)

Gnome-Shell specific and simple settings of metadata.json

That's all Folks!

I hope to have at least suggested some ideas in order to give a different face and usability to latest GNOME.

See U later!

opensuse 11.4 Broadcom BCM4311 wireless

I will to write this brief notes due the fact I faced a frustrating situation when suddenly my wireless stopped to work.

I use an old HP Pavillion DV6230BR laptop which is equipped with an AMD Turion 64 processor (64bit), a BCM4311 802.11b/g Wireless LAN Controller and latest openSUSE 11.4 64bit O.S.

So far I used to install the Broadcom wireless drivers on previous openSUSE, by using the system supplied script:

/usr/sbin/install_bcm43xx_firmware

which allows to install a free version (reverse engineered) of Broadcom drivers.

But nowadays it seems that newer kernels require the new proprietary Broadcom drivers which are available through the Packman repository:

• broadcom-wl
• broadcom-wl-kmp-[kernel flavour]

To check what is the right broadcom-wl-kmp-[kernel flavour], simply issue a "uname -a" on your system console and choose consequently the package to be installed.
Also take care about the architeture if you have a 32 or 64 bit platform.

I.E. if "uname -a" returns with "2.6.37.6-0.5-desktop", then your package shall be:

broadcom-wl-kmp-desktop.

When you have installed the two broadcom packages above from Packman repository, you have to reboot your system.

Likely the wireless board doesn't went recognized at first glance, this is due the configuration file:

/etc/modprobe.d/50-broadcom-wl-blacklist.conf

which blacklists some kernel modules which went no loaded, then you have to play right on them in order to make your wireless work.

I.E. in my case the above configuration file has been modified in this way:

# modules blacklisted for broadcom-wl

blacklist bcm43xx

#blacklist ssb

#blacklist b43

blacklist ndiswrapper

blacklist brcm80211

blacklist wl

As you can see I blacklisted all but ssb and b43 which are essential to my wireless board to work.

Finally, after a second reboot, you will notice that the orange wireless led on the front of the laptop keyboard begins blue, confirming that correct Broadcom drivers have been loaded, then you can use your Wi-Fi connection as in the past.