160 likes | 273 Views
Phone-controlled Delivery of NGN Services into Residential Environments. Dr. Andreas Fasbender Ericsson Corporate Research September 17, 2008. More and more electronic devices with integrated networking functionality
E N D
Phone-controlled Delivery of NGN Services into Residential Environments Dr. Andreas FasbenderEricsson Corporate ResearchSeptember 17, 2008
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 Consumers get networked 2000+ CE devices
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 • Communication services • Web access • Social networking • TV & music streaming • Video on demand etc. • Mix of operator-managed and user-managed services • QoS & charging if needed • Standard interfaces toInternet service providers • Mobile phone for personalization, authentication, service control etc. External Service Providers API ApplicationServers Personal Network
CAN On the move PAN In the car At the hotel VisitedLAN Separating service control & deliveryHighly simplified view... At home HomeLAN Interconnect Control Media Goal: Services delivered to any network & device, controlled by phone
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
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
Alt 1: Phone with WiFi connectivity Fetch media • Pro‘s • Simple solution • UPnP control point on phone enables trick-play 5 Request LANaccess Discoverrenderer 1 2 Navigate content directory Initiate playout 4 3 • Con‘s • Only works on phones with WiFi and UPnP/DLNA • Access contract with remoteLAN provider required • No administrator control • No QoS Relax local connectivity assumption, phone assumed to stay in WAN
Alt 2: Phone with cellular connectivity Request port / external IP Discover renderer 1 2 Encodecontrol URI 3 • Pro‘s • Full admininstrator control • Additional encryption of control URI possible • Works with standard Java phones with camera (or NFC...) Fetch media 8 Initiate playout (content URI) 7 Fetch control URIs, e.g. http://external-ip.address:port/_urn:schemas-upnp-org:service:AVTransport_control 4 Navigate content directory 5 Request media(content & control URI) 6 • Con‘s • 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
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) Some issues with usability and capacity limitations,requires autofocus & integration in phone camera API
Alt 3: Presence-based solution (1) Publish renderer (IMPU) 2 Discover renderer 1 IMS Gw Subscribe IMPU 6 Encode IMPU & PS URI 3 Notify renderer 7 Fetch IMPU & PS URI 4 Navigate content (IMPU & PS URI) 5 • 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
Alt 3: Presence-based solution (2) Invite renderer (optional QoS) 9 Initiate playout 10 IMS Gw Fetch media 11 Retrieve renderer info, request media playout 8 • Pro‘s • Operator-managed, admin controlled configuration • Exposure to Internet SPs possible • Bookmarks for access to home and placeshift to 'known' LANs • Con‘s • Requires IMS gateway control logic in remote LAN • Privacy management adds complexity Most flexible solution, in line with Connected Home vision of HGI et al.
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
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
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