technical updates on - gruppo tim · 2020. 11. 12. · context or an eps bearer is...

09/10/18, 14)27Technical updates on

Pagina 1 di 12https://intranet.telecomitalia.it/it/Community/ProfessionalCommunities/Standard%20People/Pagine/Technical-updates-on.aspx

Intranet Menzioni Newsfeed I miei Documenti Nebiolo Marco

Standard PeopleNewsletter Standards FocusArchivio NewsletterDocumenti di lavoroBrevetti e StandardArea DiscussioneClub degli InventoriNewsInternazionale

RADIO

Update on 3GPP RAN activities…3GPP RAN is closing the activity on Release 12 and work started on Release 13features such as: use of LTE in unlicensed spectrum, study on Massive MIMO,Enhancements to direct communication and discovery, new carrier aggregationconfigurations (four carriers and signaling required to aggregate more than 5 carriers).In the second half of 2014, 3GPP RAN groups worked mainly on the finalization ofRelease 12 and started the activity related to Release 13.Within Release 12 framework, thespecification of direct communication(for Public Safety applications) anddiscovery services (both forcommercial and Public Safety)progressed, but the work was notcompleted in time for the freezing of therelease. As a consequence, the workwill continue in the first quarter of 2015with the goal to finalize the protocol andradio performance aspects. This featureis quite revolutionary since it implies adirect exchange of information betweendevices authorized by the network andout of network coverage in case ofPublic Safety applications. Another major activity in Release 12was the completion of the dualconnectivity work item. This featureallows a device to be simultaneouslyconnected to a macro cell and to asmall cell, by splitting the user andcontrol planes. As an example, thecontrol plane (e.g. mobility

Cerca...

MY COMPANY TOOLKIT PERSONAL AREA COMMUNITY

https://intranet.telecomitalia.it/https://intranet.telecomitalia.it/_catalogs/masterpage/TMOldRevisitedMaster/#https://my.telecomitalia.it/https://my.telecomitalia.it/https://my.telecomitalia.it/_layouts/15/MySite.aspx?MySiteRedirect=AllDocumentsjavascript:;javascript:;https://intranet.telecomitalia.it/it/Community/ProfessionalCommunities/Standard%20People/SitePages/Pagina%20iniziale.aspxhttps://intranet.telecomitalia.it/it/Community/ProfessionalCommunities/Standard%20People/Pagine/Newsletter-Standards-Focus.aspxhttps://intranet.telecomitalia.it/it/Community/ProfessionalCommunities/Standard%20People/Pagine/Archivio%20Newsletter.aspxhttps://intranet.telecomitalia.it/it/Community/ProfessionalCommunities/Standard%20People/Documenti%20condivisi/Forms/AllItems.aspxhttps://intranet.telecomitalia.it/it/Community/ProfessionalCommunities/Club%20degli%20Inventori/Documenti%20condivisi/Forms/Ambito.aspxhttps://intranet.telecomitalia.it/it/Community/ProfessionalCommunities/Standard%20People/Lists/Discussione%20communityhttps://intranet.telecomitalia.it/it/Community/ProfessionalCommunities/Club%20degli%20Inventori/SitePages/Home1.aspxhttps://intranet.telecomitalia.it/it/Community/ProfessionalCommunities/Standard%20People/News/Pagine/Default.aspxhttps://intranet.telecomitalia.it/it/Community/ProfessionalCommunities/Standard%20People/Pagine/Internazionale.aspxhttps://intranet.telecomitalia.it/https://intranet.telecomitalia.it/tim/Pagine/home.aspx



managements, session management, etc.) can be transmitted on the macro layer,while the user plane (i.e. the users' data) can be transmitted on the small cells. Themain advantage of this feature is to facilitate the handover procedures (i.e. no need toperform many handovers when moving from one small cell to another) and allowingenergy saving procedures. For example, when there is very low traffic the small cellscan be switched off and when a user wants to start the service the macro cell start thecontrol plane connection and can decide to wake up the small cell to serve the user'straffic.3GPP RAN also approved a number of Release 13 activities. The most important onesare:

Study on LTE in unlicensed spectrum. The activity will evaluate the feasibility ofusing LTE radio in spectrum currently used by WiFi (at 5 GHz), by aggregatingthe carriers in unlicensed spectrum with one in licensed spectrumStudy on massive MIMO. The activity will evaluate the feasibility of MIMOsolutions based on more than 8 antennas. The application of these techniqueswill be likely of interest for high frequency bands where the size of the antennasis relatively small and therefore large antenna arrays can be deployedRelease 13 enhancements to directcommunication and discovery. This activity isfocused on the specifications of features ofrelevance but not included in Release 12. Anexample is the relay function: the possibilityfor Public Safety user out of coverage toreach the network by contacting anotherPublic Safety device who act as a relaytowards the network. A lot of discussion wasdedicated to Vehicle to Vehicle communication, but at the moment the activitywas not approved.American operators required the specification of solutions to aggregate up to fourLTE carriersAn activity was approved to specify the physical layer and protocol modificationsrequired to specify the aggregation of up to 32 carriers (currently 3GPPspecifications are limited to 5 carriers, with maximum channelization equal to 20MHz). This feature is of particular interest to the use of LTE in unlicensedspectrum, where large chunks of spectrum may be available and therefore manycarriers can be aggregated. For example, if there are 100 MHz available to use,5 carriers need to be aggregated to operate in this band (plus at least a sixthcarrier in licensed spectrum).

Giovanni Romano

CORE NETWORK & SERVICES

IMEISV passed on Gi and SGi InterfaceFollowing a specific request from the Core Network & Infrastructures Dept, TelecomItalia helped fixing a bug in the 3GPP specification which will help the Operator tocollect correct statistical information on handset performance via the network. Anexample on how standards can pragmatically help everyday operations.A specific request had been raised by the CN&I Dept to the 3GPP coordination team,concerning the lack of transmission of the IMEISV in a specific network procedure overGi/SGi interface, which would make difficult to correctly monitor the networkperformance. Specifically, the IMEISV is used by operators in many operational processes. Someexamples include, but are not limited to: which UE types generates the most traffic;which UE types use which services; which UE types have high success/failure rates forsession maintenance; which kind of applications can be associated to a specific

mailto:[email protected]



device,…

For thispurposes, 3GPP TS 29.061 already specified that the IMEISV be passed to the AAAserver over the Gi/SGi interface as a RADIUS attribute when a primary/secondary PDPContext or an EPS bearer is activated/created. Unfortunately this behaviour onlypartially allowed to collect statistical information on a specific device on Gi/SGi,because information about IMEISV was not sent to AAA server during the bearerdeactivation procedures. In absence of this field, e.g. correlation between theAccounting-Request Start and Stop messages is complex in order to uniquelyidentifying the UE. Telecom Italia contribution to 3GPP CT3 (Antonio Ascolese, O.ET.GNT.ENT) fixed thisanomaly and proposed that the IMEISV be passed to the AAA server over the SGi/Giinterface when a primary/secondary PDP Context is deactivated or a EPS bearer isdeleted. The proposal was discussed and accepted by 3GPP for both Rel11 and Rel12specification and the vendor equipment will have to align it. The network operators willthen be able to gather more useful statistical information finally aiming at a bettercustomer experience.Antonio Ascolese, Maria Pia Galante

3GPP creates a new WG for Mission Critical Applications3GPP TSG SA#66 in December '14 formally established SA6, the new working groupaimed at progressing the work on applications for Mission Critical Communicationswithin 3GPP. This decision goes into the direction of delivering a single globaltechnology for mission critical applications on top of LTE, as requested by the PublicSafety markets worldwide.Following the great pressure from Public Safety sector to have LTE-based commercialtechnologies for the communications among their users (in particular US Dept ofCommerce and UK Home Office), 3GPP had agreed to work in Release 13 on thestandardization of Mission Critical Push To Talk (MCPTT) for the Public Safety and theCritical Communications market. Due to previous OMA and ETSI activities on thissubject, a workshop had been held (August '14) among 3GPP, OMA and ETSI TCCEon how to best cooperate. The outcome of the workshop was that there was stronginterest (in particular from the public safety stakeholders) to set up a dedicated groupwithin 3GPP to do all MCPTT work and that the technical basis for this group would bethe existing OMA and ETSI TCCE work.The goal was to create an organizationequally attractive for all relevantstakeholders. In order to be successful,this work would need the Public Safetyexperts from Government agencies, theexperts from legacy technologies(TETRA and P25) to ensure smooth migrations, and also the relevant standardstechnology experts that understand Push over Cellular, SIP/IMS, ProSe, GroupCommunications... In addition to people with an understanding of these relevanttechnologies, the involvement of the existing experts on the related 3GPPspecifications would be needed in order to ensure that proposals will operate efficientlyand not negatively impact the existing 3GPP system and traditional Telco services.All these requirements were discussed in the recent months, when considering the

mailto:[email protected];%[email protected]



details for organizing Mission Critical Push to Talk (MCPTT) work in 3GPP. InDecember, 3GPP TSG-SA#66 finally decided to create a new Working Group,referenced here as SA6 with the following Terms of Reference:Definition, evolution and maintenance of technical specification(s) for application layerfunctional elements and interfaces supporting critical communications (e.g. MissionCritical Push To Talk), including:

Relevant application architectural aspects (including both network and terminalaspects)Definition of reference points for interactions between application functionalelementsAllocation of application functions to particular subsystems and elementsGenerating information flows between reference points within scopeIdentification of application protocols

Based on clearly identified service and feature requirements and in co-operation withthe other 3GPP WGs, identify application related architecture, functional elements,interfaces, reference points, and protocol aspects required to support criticalcommunications that utilise 3GPP-based systems. Identify and provide application level functional requirements to other 3GPP WGs,according to their expertise, where additional functionality needs to be specified thatimpacts existing architecture, reference points, interfaces, protocols or transport bearercapabilities provided by the 3GPP-based system (e.g. IMS, EPS, ProSe). Design, specify and maintain application level requirements, architecture, interface(s)and protocol(s) to support interworking with other critical communication applications incollaboration with the relevant SDOs. Work with relevant groups from other SDOs to make use of expertise available tosupport the development of specifications under the responsibility of SA6. Initially Mission Critical Communications (e.g. MCPTT) will be the focus of work. Such decision as well as further organization details were communicated in a Liaisonto all the 3GPP working groups and external SDOs. You can read this communicationhere.Andrew Howell (UK Home Office) was appointed as convenor of the SA WG6 group forthe first meeting; formal elections for chair and vicechairmen will be held in February2015.Although the priority will be on voice services in the first phase, SA6 efforts will attemptto create service enablers (e.g., group management), which can be re-used in thefuture (Release 13for the standardization of other service types (e.g., video, data).Maria Pia Galante

Update on 3GPP Release 13 WorkplanAt SA#66, in December, 3GPP confirmed the current timeline for Release 13 and atthe same time discussed its priorities. It comes as no surprise that the enablement ofPublic Safety business on top of commercial LTE networks got the highest rank in thelist.At SA#66 (Maui,10-12 December) 3GPP confirmed the current timeline for Release13: after freezing the stage 1 in September last year, the stage 2 (functionalarchitecture) will be frozen in June and the stage 3 (final overall release) in December2015.

http://www.3gpp.org/ftp/tsg_sa/TSG_SA/TSGS_66/Docs/SP-140884.zipmailto:[email protected]



Onceagain, SA WG2 (architecture) turned out to be one of the most congested groups in3GPP and thus a prioritization exercise was needed in order to guarantee that theessential pieces of works (Work Items/Study Items) be completed in the available time(i.e. up to June). It was after all a good occasion for the 3GPP community (vendorsand Operators) to discuss and get more awareness on the current priorities for themobile industries, within the scope of approved work items/study items. Public Safety is a top priority for Release 13 - It came out as no surprise that themajority of the 3GPP companies expressed high interest for all the work items relatedto the enablement of Public Safety business on top of commercial LTE networks.There are four primary topic areas that are being directly addressed in 3GPP to helpmeet the needs of public safety with LTE standards:1. Proximity Services (ProSe)2. Group Communications System Enablers for LTE (GCSE_LTE)3. Isolated E-UTRAN Operation for Public Safety (IOPS)4. MBMS Enhancements (MBMS_enh)5. Mission Critical Push to Talk over LTE (MCPTT)

The first four, ProSe, GCSE_LTE, IOPS and MBMS_enh, are generic service enablersthat are intended to fill gaps that currently exist between underlying LTEinfrastructure/handset capabilities and public safety's definition of features that arerequired for signifying a service as being mission critical capable. Work on ProSe andGCSE_LTE began in Release 12, and for ProSe, continues into Release 13. IOPS,MBMS_enh and MCPTT both began in Release 13 and are underway.There are significant aspects of both ProSe andGCSE_LTE that will not be completed in Release 12,and thus must be completed in Release 13 in order toprovide the full capability necessary for services suchas MCPTT to leverage and to be truly mission criticalcapable. Likewise, IOPS remains a very importantcapability that must also be completed in Release 13.And of course MCPTT must be completed in Release13 with a minimum functionality that will allow for it tobe a replacement service to existing Private MobileRadio (PMR) systems.These thoughts reflected the perspective of, amongthe others, US Dept. of Commerce, as well as that ofUK and South Korean governments (deployments announced in 2016 and 2017respectively). Also Telecom Italia showed interests for these activities, in light of apossible business expansion to the Public Safety market.Apart from developing service enablers and new business opportunities, thediscussion in 3GPP SA showed also strong interest in continuing a stepwisedevelopment of the network as such to meet the never ceasing requirements on lower



CAPEX/OPEX, higher bandwidth, increased network stability, overload protectionmechanisms, increased security.Among the top rated activities in this area there were: DECOR (Dedicated CoreNetwork) and FMSS (Flexible Mobile Steering). Both these activities are supportedalso by Telecom Italia.

The objective of DÉCOR is to enable the deployment of dedicated core networkswhere each dedicated core network is dedicated to UEs sharing the samecharacteristics (e.g. as machine type devices, MVNO, data usage, …). Thespecific dedicated core network that serves a UE is selected based onsubscription information and operator configuration, without requiring the UEs tobe modified.FMSS specifies how the 3GPP core network provides policies for mobile servicesteering in the (S)Gi-LAN, e.g. policies that will be used to select required serviceenablers of the operator service network.

Activities like the ones above were considered of "medium" priority. SA WG2leadership will anyway strive to progress work also in these areas.

Finally, inorder to make an effective prioritization a bunch of minor WID/SIDs were de-prioritizedand put on hold until further notice from TSG-SA. Among these, there is the "CSFBenhancement" study item, which would investigate how the CSFB procedures could beimproved for shortening call setup time. The proposal was considered of relatively highimportance only to its proponents (Huawei and China Mobile), therefore it will not befurther progressed for the Release 13.Maria Pia Galante

IETF update on HTTP 2.0 and the encryption issueMobile Internet technologies are moving to data optimisation (compression) and dataencryption mechanisms which challenge our existing way to provide mobile Internetservices and traffic. HTTP2.0Some browser editors (Google, Microsoft) areimplementing and pre-deployingconfigurations where all the Internet traffic isrouted to a server controlled by the browsereditor (proxy-based browser). At the sametime, IETF is working to the evolution of HTTPstandards (HTTP/2.0) which is promoting theuse of systematically encrypted Internettraffic. The conjunction of these two factorsmay disrupt the management of existing mobile services. In fact, currently Operatorsare able to propose differentiated mobile offers depending on usage and users profiles,for example: offer social networks to teenagers for free or the capability to display apersonalised portal for each of our customers. This is possible thanks to our added-

mailto:[email protected]



value enablers.During IETF #91 meeting (November 2014), the HTTPbis working group discussed theuse of the Web Proxy Definition mechanism proposed by Ericsson and AT&T that isintended enable the definition of a new in-network proxy entity. The IETF communityhas agreed to work on the topic of a better specification for generic proxy entities, butthe discussion is still going on. In the last meeting the working group dealt also with thedefinition of an opportunistic encryption mechanism to implement HTTP2/TLS avoidingthe use of certificates issued by Certification Authorities that is generally consideredexpensive. The opportunistic encryption proposal is however maintained separatedfrom the core HTTP2 specifications, that are undergoing final review and willsupposedly be published in the next few months.

IAB Statement on Internet Confidentiality

As aconsequence of the long discussion spurred by the privacy leaks episodes thatreached world fame during 2014, the Internet Architecture Board (IAB), the principaltechnical board recognised by the Internet community, released a statement indicatinghow important confidentiality is for Internet communications. Deployable securitysolutions are thus considered as important as the technology that enables the networkto do its work: routers, switches, DNS servers, but also caches, content optimisationplatforms. The IAB urges protocol designers to design for confidential operation bydefault and strongly encourages developers to include encryption in theirimplementations, and to make them encrypted by default. They similarly encouragenetwork and service operators to deploy encryption where it is not deployed yet, andthey urge firewall policy administrators to permit encrypted traffic. The new approachwill influence the specification of new protocols - HTTP2 and WebRTC included - toprovide security and confidentiality capabilities in their default mode of operation. Thestatement reflects the high interest of Internet companies (e.g. Google) around theneed to mandatorily offer an encryption functionality able to ensure a high privacylevel. A full header encryption allows companies like Google to be able to monetize anexclusive and dominant access to customer data (e.g. via targeted advertising) but atthe same time it severely impacts the Telco business, since network operators cannotenforce any traffic management technique (e.g. based on packet inspection) to ensurethe required levels of Service Quality (QoE) or to offer premium services.Maria Pia Galante - Emanuele Zingale




WebRTC video codec: the final decisionIETF made some progress on the question of what codecs are going to require forWebRTC implementations intended to support video. We give here details andimplications of such long-awaited decision.IETF made some long-awaited progress on the question of what codecs are going torequire for implementations intended to support video, and, for the first time, the face-to-face IETF #91 meeting (Nov ’14) has registered consensus as follows:

WebRTC Browsers mustimplement both VP8 andH.264.WebRTC Non-Browsers/Devices mustimplement both VP8 andH.264. If compelling evidencearises that one of the codecs isavailable for use on a royalty-free basis then only that codeccan be picked.WebRTC-compatible endpoints(e.g. gateway) are free to implement any video codec they see fit. Whether it's awatch, a wearable, or any other device, this opens up the world of browserinteroperability where people building applications on these end-points now haveaccess to the WebRTC ecosystem. This is particularly interesting and will helpbreak down walled gardens which exist today between the WebRTC and non-WebRTC world.

The decision, if confirmed in the ongoing mailing-list discussion, will greatly helpinteroperability and has registered consensus from a broad set of main players, suchas Google, Mozilla, Cisco and Orange. Now the future of WebRTC depends on browser/endpoint vendors to do the right thingfor the developers, the industry, and the future of real-time communications (at the timeof the IETF decision, Firefox was the only browser supporting both VP8 and H.264).Emanuele Zingale

VIRTUALIZATION

ETSI NFV: a new start after phase 1 completionETSI NFV enters into the phase 2, extending its charter until 2017. The goal is tofacilitate the transition from the Requirements Phase to the Implementation Phase forNFV with a deep work on External and Internal Interfaces.The 8th meeting of the ETSI NFV ISG in November was attended by 245 delegates,registering still an increment in companies participation, with a number of 37Operators. Revised Technical Leadership – In NFV#8 ISG Diego Lopez Telefonica (onlycandidate) was appointed Technical Manager, and Joan Triay Marques (DOCOMO)was elected as Assistant Technical Manager; there have been also appointed thecaretakers for new WGs with the task of guiding the same until the elections to be heldin the meeting NFV # 9. Elena Demaria (Telecom Italia) has been appointed caretakerfor the WG Evolution and Ecosystem. New Vice Chairs – In December 2014, Tetsuya Nakamura (NTT Docomo) resigned asVice Chair, opening a new period of election for 3 new Vice-Chairs; the election willend in January and at present Bruno Chatras (Orange) has been formally elected,whereas the others 6 candidates are all from vendor companies (Alu, Cisco, Ericsson,HP, Huawei, Nokia) for 2 Vice Chairs Positions. Completion of Phase 1 and formal approval of the documents - All technicaldocuments NFV 'Release 1' were completed and after the period of approvalprocedure, the official publication was done in January 2015; you can find the




approved documents here.NFV Phase2 structure – the structure of the group ETSI phase 2 has been defined andapproved, consisting of the following 5 working Groups:

EVE: Evolution and EcosystemIFA: Architecture and InterfacesTST: Testing, Implementation and Open SourceREL: Reliability, Availability and AssuranceSEC: Security

Compared to the Phase 1 (structured following the architectural components:Infrastructure, MANO and SWA), the new Phase 2 organization reflects the need ofintegration among components as interoperability will be a key objective, so includingnormative work where appropriate, formalized dialogue with other industry andstandards organizations including open source communities, and a continuedemphasis on encouraging open NFV implementations and Proof of Concepts. Telecom Italia Contributions: Telecom Italia participated in the definition of the workinggroups and technical proposals, and proposed some technical Work Item that wereapproved. The documents are available on the ETSI NFV site.

NFV (14) 000284r3: New WG structure proposalNFV (14) 000279r8: Or-Vnfm Interface Requirements SpecificationNFV (14) 000278r5: Or-I Interface RequirementsNFV (14) 000277r3: You-Vnfm Interface Requirements SpecificationNFV (14) 000152r6: Not hypervisor-based virtualisation

Next Meetings - The ISG NFV will hold his first Phase 2 Official meeting in Prague inFebruary 2015. At that time, the new Vice-Chairs leadership will assume theirresponsibilities.Elena Demaria - Andrea Pinnola

OPNFV: after the start the project is gaining momentumAs the main goal of the Open Platform for NFV is to develop and integrate a CarrierClass NFV Platform in order to speed up NFV implementation, after the start projectsproposals are popping up consolidating a coherent overall picture. Under the drive of several operators and vendors and the hosting of the LinuxFoundation the OPNFV Project was launched at the end of September 2014 to createan open source reference platform for NFV. The initial scope of OPNFV will be to buildthe Virtualized Infrastructure and VI Manager required for Virtualized NetworkFunctions (VNF). As many open source building blocks exist, OPNFV established towork to evolve and integrate upstream projects (e.g. OpenStack, KVM, OpenDayLight)to reach the goal of a first release delivery in 2015. Following the initial 33 starting companies, with a group of 10 Operators and a diverseteam of vendors, the OPNFV community has been growing steadily with the addition ofnew member companies bringing the total of 44 today, also promoting community




participation from not memberscompanies and single individuals. More than 30 projects ideas werediscussed at the first HackFestimmediately after launch, many ofwhich started the formal reviewprocess established in OPNFV to become TSC approved projects. As the activity isnot top down driven, a waterfall process was established: it has been of interest to seethe composing projects to form, gain consensus and then being reviewed andapproved by the Technical Steering Committee (TSC). A coherent picture is emergingfrom the proposals covering the different aspects of defining requirements for CarrierClass use of the platform, collaborative development and testing and integration. Atthe current date 11 projects have been started after approval whereas around 20 arebeing discussed and revised to collect consensus and a critical mass to start. Thecommunity and TSC have been also busy reviewing and establishing methodologiesfor community collaboration. In November 2014, OPNFV participants also gathered at OpenStack Summit in Paris,as an opportunity to meet the OpenStack community and to find ways to collaborateon feature development and testing. Cross community collaboration will be a key focusarea for 2015 with the OPNFV community looking to invest in and providing value bothto user and developer communities. Next Meetings - The OPNFV community has plans to meet and collaborate at thefollowing events in February: a Meet-up at the Linux Foundation Collaboration Summit,at Santa Rosa, Calif, and Hackfests around ETSI NFV#9 in Prague.Andrea Pinnola

Telecom Italia contribution to define BBF involvement invirtualisationBBF is one of the most relevant standard organization that have started working atvirtualization technology and Telecom Italia is bringing contributions in the areas ofinterest.Flexible Service Chaining, SDN and Virtualisation are among the most relevant topicswhich the Broad Band Forum has been focusing on lately, with activities being carriedon in its SIMR (Service Innovation & Market Requirements) group.

SIMR actsas an incubator for the development of the most innovative topics and defines highlevel recommendations and business requirements for the groups that work at thetechnical detail specifications once a subject has reached a certain maturity, allowingto start a traditional standardisation path.Several initiatives and project proposals exist in BBF-SIMR at present, confirming thegrowing interest for SDN and virtualisation, and recently an ad-hoc committee, calledVPPTF (Virtualization Project Planning Task Force), has also been set up with the goalto structure a concrete work plan and to define a roadmap for these activities in BBF.Telecom Italia actively participated in the scouting and study phase of the relevanttopics, bringing, with several contributions, the company's vision. In particular thecontribution has been to the Study Document on Flexible Service Chaining, proposingseveral use cases that highlight important aspects of service chaining, as the sharedusage of virtual and physical resources, the centralisation in the Data Centre of somefunctionalities and the system resilience.Diego Daino

mailto:[email protected]:[email protected]



APPLICATION LAYER

OMATechnical Work in OMA in 2015 will be focused on the evolution of APIs (both networkand device), evolution of device management solutions in new areas (M2M,automotive) and to study how to adapt NFV concepts into the OMA architectureDuring 4Q2014, OMA has finalized the "RESTful Network API for Quality of Service,"that enables an application to govern thequality of service (QoS) applied on end usernetwork connections on a temporary basis.This is an important element to enableoperators to become "Smart", in other wordsto leverage unique service abilities to providevalue beyond that of data connectivity onlyor in a wider sense, beyond traditional core business.OMA has also finalized the "Management Interface for M2M V1.0," defining (jointly withoneM2M) a set of requirements for the Northbound Interface from Device Management(DM) server to the Machine to Machine (M2M) systems on top of it, allowing the M2Mservice layer to access the DM server functionality, such as device and servicemanagement areas. Always in the area of remote device management, OMA will beholding a LWM2M (OMA Lightweight M2M v1.0) TestFest and Workshop event, hostedby Vodafone Innovation Park with the collaboration of the Eclipse Foundation, from 26-29 January 2015 in Dusseldorf, Germany (http://openmobilealliance.org/event/oma-lwm2m-testfest-event-workshop/). OMA held its meeting in January 2015 where some new work items to be started in2015 have been proposed both to progress in the area of Device Management andNetwork and Device APIs. Besides to be pointed out that many OMA Operators(including Telecom Italia) support a new Work Item 'OMA Guidelines for NetworkService Description' with the scope to provide recommendations for application of NFVconcepts to OMA enablers, as expressed though the various "descriptors" used in VNFmanagement and orchestration (ETSI MANO). Finally OMA will be exhibiting in the next GSMA MWC, App Planet Hall 8.1, Stand K52.It will be possible to see demos of implementations of OMA enablers from OMAmember companies, Alcatel-Lucent, Comverse, CSR, Friendly Technologies, SmithMicro, Red Bend, Red Stone, Vodafone, Vuzix and ZTE.Contatta la Cecilia Corbi

W3CW3C celebrates its 20th anniversary with a big symposium to discuss the future of theWeb and new initiatives are startingW3C had recently celebrated its 20th anniversary (http://www.w3.org/20/) with manyactivities on going.W3C is recently focusing in the areas of Web of Things (to develop Web standards forenabling open markets of applications and services based upon connected sensorsand actuators and the Web of data) and Web Payments (to develop use cases andrequirements for existing and/or new specifications to ease payments on the Web forusers and merchants and to establish a common ground for payment service providerson the Web Platform). In the area of Social standards W3C has taken over and isdeveloping OPEN SOCIAL foundation standards works. WebRTC is still themainstream with Google and Ericsson pushing constantly. Amazon Fire TV announcedfull HTML5 support and represents the official, promising entry point of Web Standardsin the television domain.Cecilia Corbi

http://openmobilealliance.org/event/oma-lwm2m-testfest-event-workshop/mailto:[email protected]://www.w3.org/http://www.w3.org/20/mailto:[email protected]