Transcript NGMAST 2008

Phone-controlled Delivery of NGN
Services into Residential Environments
Dr. Andreas Fasbender
Ericsson Corporate Research
September 17, 2008
Consumers get networked
 More and more electronic devices with integrated networking functionality
 Clusters of networked devices in the private domains of the users
(home/car/corporate LAN, phone PAN, etc.)
 Local networks (e.g., based on DLNA) interconnected by IMS, XML Web
Services and cloud computing technologies
2000+
CE devices
Andreas Fasbender, Stefan Hoferer, Martin Gerdes, Takeshi Matsumura, Andreas Häber, Frank Reichert
2 (18)
2008-09-17
Personal networks get connected
 High-speed fixed & mobile broadband access available anywhere
 NGN with IMS as common service control layer gaining market traction
 Consumers want services to be available across network boundaries
and consumption devices
External Service Providers
API
–
–
–
–
–
Communication services
Web access
Social networking
TV & music streaming
Video on demand etc.
Application
Servers
 Mix of operator-managed
and user-managed services
Personal Network
– QoS & charging if needed
– Standard interfaces to
Internet service providers
 Mobile phone for personalization, authentication, service control etc.
Andreas Fasbender, Stefan Hoferer, Martin Gerdes, Takeshi Matsumura, Andreas Häber, Frank Reichert
3 (18)
2008-09-17
Separating service control & delivery
Highly simplified view...
PND
On the move
In the car
CAN
PDA
PAN
Car gateway
Camera
User’s
Phone
User’s
Phone
At home
At the hotel
PDA
PC
Home
LAN
Mobile Operator
Managed Services
User’s
Phone
Home
Gateway
Camera
Control
Media
Visited
LAN
Interconnect
Home Devices
(TV, Stereo etc.)
Remote Devices
(TV, Stereo etc.)
PC
Printer & scanner
Home Operator
Managed Services
Visited Operator
Managed Services
Home
Services
Visited
Gateway
User’s
Phone
Visited
Services
3rd party &
Internet Services
Goal: Services delivered to any network & device, controlled by phone
Andreas Fasbender, Stefan Hoferer, Martin Gerdes, Takeshi Matsumura, Andreas Häber, Frank Reichert
4 (18)
2008-09-17
Media portal use case
Andreas Fasbender, Stefan Hoferer, Martin Gerdes, Takeshi Matsumura, Andreas Häber, Frank Reichert
5 (18)
2008-09-17
Requirements & features
 Requirements
– Trust relationship between user (device, identity), operator and
remote environment, independent of service provider
– Security, e.g. no uncontrolled exposure of remote appliances
or requesting device
– Support of off-the-shelf DLNA devices without SW modifications
– Usage of remote devices under full control of administrator
– Ease of use, no entering of complex bookmarks or addresses
 Features
– Authentication of users and service providers (IMS assumed)
– Secure & easy-to-use relationship establishment between
phone and remote environment (with and w/o LAN connectivity)
– Discovery and control of remote devices by service provider
– Service delivery into NAT-ed remote environments
Andreas Fasbender, Stefan Hoferer, Martin Gerdes, Takeshi Matsumura, Andreas Häber, Frank Reichert
6 (18)
2008-09-17
Assumptions in the following
 User has a mobile phone subscribed to and authenticated
with mobile operator
– Service delivery may be based on IMS signalling or not
 User has subscription to operator media portal
– However, remote access to home contents or delivery of
3rd party services can be realized using the same architecture
 User selects media services to be delivered into a CE
device in a remote environment
– Focus will be on DLNA devices only
– Other devices can be supported with similar approach
 Remote administrator grants the use of remote equipment
– Examples: Coupon at hotel check-in, password in hotspot
Andreas Fasbender, Stefan Hoferer, Martin Gerdes, Takeshi Matsumura, Andreas Häber, Frank Reichert
7 (18)
2008-09-17
Alt 1: Phone with WiFi connectivity
5 Fetch media
1
Streaming
Server
Request LAN
access
Navigate
content directory
Media Portal
Application Server
 Pro‘s
Discover
renderer
Home Devices
(TV, Hifi)
Residential
Gateway
3
2
4 Initiate playout
User’s
Phone
 Con‘s
– Simple solution
– UPnP control point on
phone enables trick-play
– Only works on phones with
WiFi and UPnP/DLNA
– Access contract with remote
LAN provider required
– No administrator control
– No QoS
 Relax local connectivity assumption, phone assumed to stay in WAN
Andreas Fasbender, Stefan Hoferer, Martin Gerdes, Takeshi Matsumura, Andreas Häber, Frank Reichert
8 (18)
2008-09-17
Alt 2: Phone with cellular connectivity
2
Request port /
external IP Residential Control
Device
8 Fetch media
3
Encode
control URI
7 Initiate playout (content URI)
Streaming
Server
Residential
Gateway
Media Portal
Application Server
 Pro‘s
1 Discover renderer
5 Navigate content directory
Request media
6
(content & control URI)
Home Devices
(TV, Hifi)
Fetch control URIs, e.g.
4 http://external-ip.address:port/
_urn:schemas-upnp-org:service:
AVTransport_control
User’s
Phone
 Con‘s
– Full admininstrator control
– Additional encryption of control
URI possible
– Works with standard Java
phones with camera (or NFC...)
– Requires residential control
logic for port & URI mgmt.
– No QoS, HTTP hickups with
video services
– No capability negotiation
Add-on: RCD manages device list & capabilities, additional hand-shake
Andreas Fasbender, Stefan Hoferer, Martin Gerdes, Takeshi Matsumura, Andreas Häber, Frank Reichert
9 (18)
2008-09-17
Pairing with remote environment
 Several alternatives
– Bluetooth or WiFi: Interoperability and security issues
– NFC: Not (yet) wide-spread (except in Japan), requires hardware
 Bar codes
– Easiest to deploy (display, print, hand-out etc.)
– Quicker penetration in
mobile phones expected
1000+ symbologies exist, standardization in OMA MCC
(QR codes or Data Matrix, as widely used in Japan)
Andreas Fasbender, Stefan Hoferer, Martin Gerdes, Takeshi Matsumura, Andreas Häber, Frank Reichert
Some issues with usability and capacity limitations,
requires autofocus & integration in phone camera API
10 (18)
2008-09-17
Alt 3: Presence-based solution (1)
2 Publish renderer (IMPU)
Presence
Server
1 Discover renderer
6 Subscribe IMPU
IMS Gw
3 Encode IMPU & PS URI
7 Notify renderer
Home Devices
(TV, Hifi)
Residential
Gateway
4 Fetch IMPU & PS URI
Media Portal
Application Server
5
Navigate content
(IMPU & PS URI)
User’s
Phone
 Residential control device integrated in gateway that hosts
IMS termination (B2BUA, SIP UA, DLNA interworking)
– Under standardization in HGI and TISPAN, ISIM optional
– Natural control point for LAN (router, TR-069, DLNA MIU etc.)
 Device capabilities & status published to PS
– Administrator or user control which devices are exposed to whom
Andreas Fasbender, Stefan Hoferer, Martin Gerdes, Takeshi Matsumura, Andreas Häber, Frank Reichert
11 (18)
2008-09-17
Alt 3: Presence-based solution (2)
9
Invite renderer
(optional QoS)
10 Initiate playout
IMS Gw
11 Fetch media
Streaming
Server
Media Portal
Application Server
 Pro‘s
Home Devices
(TV, Hifi)
Residential
Gateway
8
Retrieve renderer info,
request media playout
User’s
Phone
 Con‘s
– Operator-managed, admin
– Requires IMS gateway
controlled configuration
control logic in remote LAN
– Exposure to Internet SPs possible – Privacy management adds
complexity
– Bookmarks for access to home
and placeshift to 'known' LANs
Most flexible solution, in line with Connected Home vision of HGI et al.
Andreas Fasbender, Stefan Hoferer, Martin Gerdes, Takeshi Matsumura, Andreas Häber, Frank Reichert
12 (18)
2008-09-17
Related standardization work
 HGI
– IMS proxy in residential gateways
 3GPP/TISPAN
– IMS/NGN, CPE/CPN (Customer Premises Equipment / Network)
 DLNA/UPnP
– CE device profiles
 OMA Converged Personal Network Services
– Manage service delivery to CE devices with help of the phone
 3GPP Personal Network Management
– Redirection of service delivery between IMS UEs
 OMA Mobile Codes Consortium
– Direct and indirect bar codes
Andreas Fasbender, Stefan Hoferer, Martin Gerdes, Takeshi Matsumura, Andreas Häber, Frank Reichert
13 (18)
2008-09-17
Lessons learned in prototyping
 Proximity solutions not yet properly implemented in
mobile phones
– Standardization and better phone integration required
 Remote control of DLNA appliances requires DMR
profile compliance
– DLNA 1.5 certification starting
 QoS support requires signalling and transcoding in
gateway
– Interworking with home QoS solutions, e.g. UPnP QoS
– RTP support only optional in DLNA
Andreas Fasbender, Stefan Hoferer, Martin Gerdes, Takeshi Matsumura, Andreas Häber, Frank Reichert
14 (18)
2008-09-17
Conclusions
 Proposed solutions enable relationship establishment
between users, remote devices, and services
– Widely deployable on today’s networks
– Supporting off-the-shelf consumer appliances
– Bar codes provide an interesting alternative for pairing a mobile
phone with a remote environment and grant access for the user
– Presence-based solution supports a wide range of other services
 Tradeoff between
– Security, flexibility, quality and ease of use on the one hand
– Solution complexity and speed of deployment on the other
 Standardization underway for most parts of the solution
– Gaps on mobile phone side  Potential push for WS alternatives
– HGI & TISPAN prepare the ground for proposed solution
Andreas Fasbender, Stefan Hoferer, Martin Gerdes, Takeshi Matsumura, Andreas Häber, Frank Reichert
15 (18)
2008-09-17
Andreas Fasbender, Stefan Hoferer, Martin Gerdes, Takeshi Matsumura, Andreas Häber, Frank Reichert
16 (18)
2008-09-17