Network 2020 Programme - Ecosystem Update All-IP Communication Services Roadmap - GSMA
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
Network 2020 Programme – Ecosystem Update
All-IP Communication Services Roadmap
© GSM Association2015
All GSMA meetings are conducted in full compliance with the
GSMA’s anti-trust compliance policy
© GSMA2015
Agenda
Welcome and Introductions – David Pringle, Webinar Moderator
RCS roadmap developments and the benefits for operators,
manufacturers and end users
– David O’ Byrne, IP Communications Project Director,
Network 2020, GSMA
Defining an IMS Profile for Converged IP Communications
– David Hutton, Director of Technology GSMA
Update on Mobile World Congress 2015
- Rosie Shergill, Marketing, GSMA
Question & Answers - David Pringle, Webinar Moderator
© GSMA2015
Network 2020 Programme
RCS Roadmap Developments
David O’Byrne – IP Communications Project Director, Restricted - Confidential Information
© GSM Association 2015
All GSMA meetings are conducted in full compliance with the
Network 2020 GSMA’s anti-trust compliance policy
RCS 5 - A Big Step towards All-IP
Basic services, converging natively, enrich the core
calling services.
Device APIs
Defines a single/dual coherent IP
RCS Communications stack for the
In Call RCS Video industry/OEMs, integrating VoLTE,
Messaging Video calls over LTE and RCS
Incremental Voice to video
Functionality
Incremental
functionality session evolution
standards
(from SMS/MMS)
Video Chat
Extension to WiFi
RCS Voice Incremental
functionality Enriches the functionality of the
Extension to WiFi
Incremental and 3G interoperable and native
Functionality
communication services: voice,
Extension to WiFi
messaging and video (“Green Button”)
VoLTE Video
Extends the service availability/
calls connectivity to WiFi* to provide a
over seamless fixed/mobile service
LTE
‘Green Button Promise’
© GSMA2015
communication services * And to 3G for Video Call 5
Importance of native devices
Relative poor experience with early downloadable
clients
Increased success in take-up and usage statistics
with native clients
Native Blackbird clients coming on stream shortly for
most launched networks
Focus of today’s presentation is on recent RCS
developments and work underway to drive native
device implementations
© GSMA2015
RCS Specification progression
2011 2013 2015
Joyn N.A. Other
Crane Guidelines MNO
RCC 61:
No common feature set Common Core
RCS-e 1.2.2 RCS 5.1 RCS 5.2 RCS 5.3
Published as a maintenance 5.1 introduces additional new 5.2 improved central 5.3 drives technical
release of Version 1.2 of the features such as Group Chat message store, introduced convergence on a single
RCS specification, includes bug Store & Forward, File Transfer in service extension tags and solution across most of the
fixes/lessons-learnt based on Group Chat, File Transfer Store & areas of RCS
bug fixes to RCS 5.1 V4.0.
V1.2.1 IOT Forward, and Best Effort Voice
Call
© GSMA2015
What is the Common Core?
The Common Core provides use cases and feature requirements
for a prioritised set of services and has been developed to
– Provide clear requirements and guidelines for open market
devices
– Drive economies of scale and accelerate time to market
– Promote interoperability between operators based on common
requirements
What does the spreadsheet bring / how does it help?
The Core Feature list will capture the mandatory requirements for
each feature defined in the Common Core and will provide
guidance on what networks need to support if the service is
deployed.
This helps provide a clear overview summary of each service and
Timelines for being publically available
Common Core 1.0 is publically available
A maintenance update (Common Core 1.1), which delivers
alignment with RCS 5.3, shall be available by MWC
The Core Feature list shall be available by mid March.
© GSMA2015
Common Core Services and Enablers
Enablers Operator Messaging
Capability Discovery / Seamless messaging
Service Integrated messaging
Availability
Messaging for Multi-
Device / Client device
Provisioning
File Transfer
API Extensions incl.
Service Tag (indicates – Audio Messaging
the application a – Geo-location push
message was created – vCard
from)
Security against malware Voice
Data Off requirements IP Voice and IP Video
Calls (incl. [IR.92] and
[IR.94])
Messaging In-Call Services
1-2-1 Messaging incl.
standalone messaging
Group Chat
© GSMA2015
RCS 5.3 – the road to convergence
Client NNI Convergence Status
1 Capability Exchange No Convergence in RCS5.3
(Presence vs. OPTIONS)
2 Configuration: OMA DM vs. Align with on-going IREG work for
HTTP RCS5.3
3 Transport for 1st message in 1- Converged on OMA CPM but with
to-1 Chat transition period
4 Multi-media in Chat CR included in RCS5.3
5 File Transfer: MSRP or HTTP IP Comms LT studying effects of dual
approach
6 CPM vs. SIMPLE IM Converged on OMA CPM but with
transition period
7 APNs: Internet or IMS APN Aligning with IREG for RCS5.3
8 RCS IP Calls CR included in RCS5.3
9 Group Chat models CR included in RCS5.3
10 Authentication Align with on-going IREG work for
RCS5.3
11 Blacklist handling Reflected in RCS 5.3
12 Geolocation PULL
© GSMA2015
10Common Core Framework
Common Core Documents IP. Communications Profile (i.e. joyn Crane or Canadian Profile)
Service
Definition
Documents
Technical
Specifications
Features … and applicable Definition of additional UX
selection from technical procedures guidelines (optional)
SDDs
UNI / NNI
Guidelines
Correspondent Test Cases
UNI+NNI+API + UNI-NNI Guidelines
Test Cases
• Test fest
• UX Verification
• Scope approved by IP
Communications LT
• Service Definitions based only on
approved technical standards
• Service definition requests guide Resulting Accreditation Framework for the profile defined
evolution of technical standards
© GSMA2015
11Benefits of recent development
For operators
– Common Core clarifies which services are priority to launch
– Converged specification simplifies implementation
– Facilitates interoperability with other MNOs
– Wider range of native devices with faster time to market
For vendors
– Technical simplification leads to less one-time engineering,
eases equipment production
– Clearer more aligned requirements from operators
– Greater market demand
© GSMA2015The overall All-IP ecosystem is building momentum
© GSMA2015
13Network 2020 Programme
INSERT
DH IMS Profile definition for Converged
PIC Communications
Restricted - Confidential Information
David Hutton – Director of Technology, GSMA © GSM Association2015
All GSMA meetings are conducted in full compliance with the
GSMA’s anti-trust compliance policyThe need for a Converged UNI Profile
A variety of access and service specific PRDs exist within the GSMA
– IR.92 (Voice & SMS profile [via LTE])
– IR.94 (Conversational Video Service)
– IR.51 (Voice, SMS and Conversational video via EPC integrated WiFi)
– RCC.07 (RCS Client & Services Specification)
N2020 scope includes the promotion of the ‘Green Button Promise’
– Enables enriched calling with IP-based voice, video and messaging
services
– Provides inherent operator Quality of Service (QoS) for all services
Converged IP Communications services in devices (i.e. converged voice,
video and RCS services) to achieve the ‘promise’ require
– Specifications to be brought together as a single implementation,
ensuring consistency in common areas
– A converged UNI specification, based on the related access and service
specific PRDs
© GSMA2015
15Defining a UNI Specification for Converged
IP Services – Scope of Work
Base solution on existing set of access and service specific PRDs and
(where possible) cross referencing into those PRDs
Identify conflicts and issues, propose solutions
Wherever possible, avoid optionality
Be sensitive to current situation
– Recognize the current divergence in the market in terms of deployment
of VoLTE & RCS services (i.e. single/converged versus dual IMS core
architectures
– Support/take account of all variations in order to maximize relevance of
Converged PRD and not exclude any Operators
– Include access via any applicable access network (LTE and EPC
Integrated Wi-Fi access)
Existing access and service specific PRDs
Should be unchanged, except where
Issues are identified in existing PRDs as part of this work (these will be
reported to the responsible group)
© GSMA2015
16Converged UNI - Devices need to work with Separate or
Converged IMS architectures
Separate Core Networks
Device configured to work with
dual IMS core architectures
RCS Network VoLTE Network
Single Core Network
Device configured to work with
converged IMS core architectures
Combined RCS &
VoLTE Network
© GSMA2015Converged UNI - Devices should be built so they will work
on any operator’s network
Separate Core Networks
Device configured to work with
dual IMS core architectures
RCS Network VoLTE Network
Single Core Network
Device configured to work with
converged IMS core architectures
Combined RCS &
VoLTE Network
© GSMA2015Delivering on Interoperability and Availability of Native
Devices
Interconnection
Operator 1 OOppeerraattoorr22
Service level
interoperability
© GSMA2015Delivering on Interoperability and Availability of Native
Devices
Open Market
Devices
Interconnection
Operator 1 Operator 2
Service level
interoperability
© GSMA2015Delivering on Interoperability and Availability of Native
Devices
Device
Portability
Interconnection
Operator 1 Operator 2
Service level
interoperability
© GSMA2015GSMA supports OEMs to implement interoperable
IP Communications services
Device Accreditation
Portability
Framework for
Networks and Devices /
Clients
ServicIenDteefrinciotionnnDeoccutmioennts
Technical Specifications
Service Implementation Guidelines
Operator 1 Operator 2
Test CasSeesrfovri:ce level
User Ne tw ork I nt er f ac e(U N I),and
NetworkintoteNetwork
r op e raInterface
bil it y (NNI)
© GSMA2015Network 2020 Programme
INSERT
DH Update on Mobile World Congress 2015
PIC
Restricted - Confidential Information
Rosie Shergill– Marketing, GSMA © GSM Association2015
All GSMA meetings are conducted in full compliance with the
GSMA’s anti-trust compliance policyNetwork 2020 Returns to the Innovation City
© GSMA2015
24Network 2020 Located on the GSMA Pavilion
© GSMA2015
25MWC 2015 Presence Overview – Network 2020
Innovation City – Network 2020 Operator and Vendor Demonstrations
• Enriched Call Demo showing Pre-/In- & Post Call Features
(based on RCS) by Deutsche Telekom and Orange
• ‘Green Button Promise’ demo: D2 and NewNet
• Connecting the ‘Green Button Promise’ experience: jibe on
interconnection
• VoLTE to VoWifi handover demonstration from Huawei
• RCS Multidevice demo Deutsche Telekom and WIT
• VoLTE and RCS connected car: Summit Tech
© GSMA2015
26Seminar- Mobilising the All-IP Future
(Monday 9.30-11.30)
Network 2020 Programme 2015-2016 overview and presenting
the case for an ALL- IP Future
Keynote Spkr: Bruno Jacobfeuerborn, DT, Group CTO
Guest Speaker – Mobile Operator on their All-IP Strategy
Panel 1 – Interoperability and how to achieve scale
Leading Mobile Operators and Device Manufacturer
Moderator – Alex Sinclair, Chief Technology Officer, GSMA
© GSMA2015Main Agenda Conference
Keynote 3: The Road to 5G Tuesday 9.15 – 10.45am
5G requirements Wednesday 2pm-3pm
5G services Wednesday 3.15- 4.15pm
http://www.mobileworldcongress.com
© GSMA2015IP Communications Virtual Showcase
Network2020@gsma.com
© GSMA2015
29Webinars
Webinar 1, 15th January: ‘Achieving IP Communications
Interoperability – Global Industry Update’
Webinar 2, 5th February: ‘Green Button Promise’
Webinar 3, 11th February: ‘All-IP Communication Services
Roadmap - Ecosystem Update’
Webinar 4, 18th March: ‘Interconnected mobile All-IP
communications and the benefits for Operators’
© GSMA2015You can also read
