For more details, you can read Alan Quayle's summary on his blog here.
Sunday, 5 May 2013
Thursday, 14 March 2013
So what exactly WebRTC is in technical terms. Here is a recent presentation from WebRTC Conference and Expo
And here is another presentation that explains where it fits in with the LTE Architecture.
Dean Bubley from Disruptive Analysis has writted extensively on this topic and his recent post "Is the telephony "threat" from VoIP & WebRTC about competition or contextualisation?" is an interesting read.
Iain Sharp from Netovate recently pointed out that 3GPP have 'nearly' approved a work item for WebRTC access to IMS.
It would be interesting to see how operators will view WebRTC. As an opportunity or as a threat. Please feel free to air your opinions via comments.
Thursday, 20 December 2012
Couple of old but interesting whitepapers from Spirent available, in case you are interesting in IMS. Available to download from here (registration required)
Related blog posts:
- IMS Release 10 Tutorial
- ETSI INT IMS/EPC Interoperability Standardisation: Motivation, Roadmap & First Results
- UICC and ISIM (IMS SIM)
Monday, 17 December 2012
Sunday, 26 August 2012
Wednesday, 15 August 2012
Saturday, 14 April 2012
Friday, 30 March 2012
Thursday, 22 March 2012
I have mentioned before that UICC is the physical card and 2G SIM/USIM/ISIM are applications on the UICC card. The IMS SIM holds data provided by the IMS Operator, generally the same operator that would provide USIM services that would allow to camp on the 3G or LTE network.
Private User Identity: This identifies the user uniquely with the IMS operator and is used when the user registers with the IMS network. This is used by the operator to check the subscription and which services the user can avail of.
Public User Identity: A user can have multiple public identities that can be used for different services. To avail a particular service, user has to register with the particular public identity that has been allowed for that service.
Security Keys: Security keys are used for authentication to the IMS Network.
Home Network Domain Name: This is the name of the entry point that the user uses to register. This makes sure that a users request is sent to the Home Network.
Access Rule Reference: This is used to store information about which personal identification number needs verification for accessing a particular application
Address of P-CSCF: If it is not possible do dynamically find the Proxy-Call Session Control Function then this address is helpful
Administrative Data: Some of this could be operator specific proprietary information
Wednesday, 14 December 2011
This was presented by Giulio Maggiore, Telecom Italia, ETSI TC INT Chairman in the 2nd FOKUS FUSECO Forum 2011, Berlin 17-18 Nov. 2011
From the ETSI leaflet (note that this is quite old information but still on the ETSI website here):
IMS interoperability is a key issue for boosting IMS (IP Multimedia Subsystem) roll-out and more specifically network interconnection between operators. Only through thorough testing in practical scenarios can operators ensure operational excellence in a multi-vendor and multi-provider environment.
IMS comprises a set of specifications designed to enable network operators to implement IP-based networks that can carry services for both fixed and mobile customers simultaneously.
IMS was developed originally in the mobile world (specifically in the specifications created by the 3rd Generation Partnership Project, 3GPP), and was adopted for fixed networks by ETSI’s TISPAN Technical Committee (Telecoms & Internet Converged Services & Protocols for Advanced Networks).
However this promise of advanced communications over the next generation network will only be delivered if those same networks can interconnect.
ETSI’s Technical Committee INT: IMS Network Testing
ETSI is bridging the existing gap between 3GPP IMS Core Network standards and the initial industry IMS implementations through the organization of IMS interoperability events in connection with ETSI’s Centre for Testing & Interoperability (CTI) and Plugtests™ interoperability testing service.
Our Technical Committee for IMS Network Testing (TC INT) is actively establishing close contact with a number of industry fora and organizations dealing with IMS interoperability, including 3GPP, GSMA, MSF (Multi Service Forum), IMS Forum and the ITU-T. TC INT develops IMS test specification according to conformance, network integration and interoperability testing methodologies. Other ongoing work includes development of tests for Supplementary Services based on regulatory requirements and IMS tests with legacy networks (e.g. SIP-I).
ETSI has already held two IMS interoperability events. The first examined interconnection aspects of 3GPP IMS Release 6, including such issues as basic call on the Mw interface. The second event had a wider scope that included the testing of 3GPP IMS Release 7 interworking, roaming, border control, and integration of application servers executing selected Multimedia Telephony supplementary services.
Future ETSI activities and events will go even deeper towards bridging 3GPP IMS standards and industry implementations. These will include the organization of further IMS interoperability events designed to boost the roll-out and take-off of IMS services and operators’ network interconnections.
Wednesday, 10 August 2011
Monday, 6 June 2011
Tuesday, 10 May 2011
Monday, 25 April 2011
Sunday, 24 April 2011
WeFi has launched a product that is intended to enable mobile operators to route traffic over the mobile macro network or a WiFi hotspot without the consumer having to manage their own settings.
The product, from WeFi, enables operators to set network management policies using a 3GPP-defined function for the Evolved Packet Core called ANDSF – Access Network Discovery and Selection Function. WeFi said that its WeANDSF is the first standards-compliant product on the market, although it said that as the standards are not yet fully finalised, the product is more accurately described as a pre-standards compliant product.
ANDSF, specified in 3GPP standards 23.402 and 24.312, is intended to allow mobile operators to set network management policies and priorities, and to control where, when and under what circumstances a subscriber’s device connects to which wireless network, be it cellular or Wi-Fi.
Operators may choose to route traffic according to application type to reduce network load, or to provide the best available customer experience. Although operators are increasingly looking at using WiFi for offload in congested areas, one problem for them is that once traffic is routed over WiFi control is lost over any traffic policies they have set for that user. ANDSF keeps a link to the operator's core network, allowing the operator visibility of traffic even when it is routed over WiFi.
WeFi said that the product is already in trials with several mobile operators. As handset manufacturers are yet to include the device element of ANDSF, WeFi is also providing a device client, although it sees that role diminishing as handset vendors deliver ANDSF-compliant handsets, “when these become available in the market by 2012”.The following presentation is by Fraunhofer Fokus on ANDSF:
For more details see:
Tuesday, 19 April 2011
Monday, 18 April 2011
Tuesday, 1 March 2011
Thursday, 20 January 2011
- Mechanisms to allocate resources for signaling and media with priority based on subscribed priority or based on priority indicated by service signaling.
- For a terminating IMS session over LTE, a mechanism for the network to detect priority of the session and treat it with priority.
- A mechanism to properly handle the priority terminating voice call and enable the target UE to establish the AS and NAS connection to fall-back to the GERAN/UTRAN/1xRTT.