IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Reference Model and Use-Cases for Information Service Date Submitted: Month, NN, 200x Presented at IEEE session #NN in City Authors or Source(s): Yoshihiro Ohba, Farooq Bari, Subir Das Abstract: This document describes reference model and potential use-cases of IEEE Information Service. The purpose of this document is to discuss, clearly identify the scope of Information Service with regards to IETF requirements.

IEEE presentation release statements This document has been prepared to assist the IEEE Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual and in Understanding Patent Issues During IEEE Standards Development Section 6.3 of the IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3

Information Service (IS) Reference Model IS Function UE IS Function Network IS Provider (NISP) Ia (1:n) Ia : Interface between UE and Network IS provider Ix: Interface between IS function and Information Database Ia`: Interface between two Network IS providers IS function is an MIH sub-function; The placement of IS function in the network will vary depending upon specific architecture and deployment requirements IS Function IS Function IS Function Ia (1:n) Network IS Provider (NISP) NISPUE Multi hop Model Single hop Model Ia` (1:n) Information Database Ix (1:n) Information Database Ix (1:n) Depending upon the network architecture and configuration, Ix Interface can be an internal or external interface.

Information Service (IS) Protocol Model IS Function (Client) UE IS Function (Server) NISP Ia (1:n) IS function is an MIH sub-function; The placement of IS function in the network will vary depending upon specific architecture and deployment requirements IS Function (Client) IS Function (Relay/Proxy) IS Function (Server) Ia (1:n) NISP UE Multi hop Model Single hop Model Ia` (1:n) Information Database Ix (1:n) Information Database Ix (1:n) Ia : Interface between UE and Network IS Provider Ix: Interface between IS function and Information Database Ia`: Interface between two Network IS providers

Information Service Standardization Scope IS Function UE IS Function NISP Carried over lower layer transport (L2) Carried over higher layer transport (L3 and above) IEEE Scope IEEE /IETF Scope Information Database Depending upon the network architecture and configuration, Ix Interface can be an internal or external interface. Ia (1:n)Ix (1:n) IETF Scope (?) Ia` (1:n) Ia : Interface between UE and Network IS Provider Ix: Interface between IS function and Information Database Ia`: Interface between two Network IS Providers IEEE /IETF Scope

Use-Cases Case 1: Distributed Information Service co-located with Information Database Case 2: Distributed Information Service with separate Information Database Case 3: Distributed Information Service with centralized Information Database Case 4: Centralized Information Service with co-located Information Database

Case 1: Distributed Information Service Co-located with Information Database IS Function/ Information Database IS Function Network IS Provider UE NISP Ia IS Function/ Information Database IEEE / IETF Scope Ia` IEEE /IETF Scope Ia : Interface between UE and Network IS Provider Ia`: Interface between two Network IS Providers

Case 2a: Distributed Information Service with separate Information Servers UE Information Database Information Database Ia Ix IS Function Network IS Provider IS Function IS Function Ia: Interface between UE and Network Ix : Interface between IS Function and Information Database IETF Scope (?) IEEE /IETF Scope

Case 2b: Distributed Information Service with separate Information Database UE Information Database Information Database Ia Ix IS Function Network IS Provider IS Function IS Function Ia` IEEE / IETF Scope (?) Ia: Interface between UE and Network Ix : Interface between IS Function and Information Database IEEE / IETF Scope

Case 2c: Distributed Information Service with separate Information Database UE Information Database Information Database Ia Ix IS Function Network IS Provider IS Function IS Function Ix IETF Scope ? IETF Scope (?) Ia : Interface between UE and Network IS Provider Ix: Interface between IS function and Information Database Ia`: Interface between two Network IS Providers IEEE / IETF Scope

Case 3: Distributed Information Service with centralized Information Server UE Information Database Ia Ix IS Function IS Function IS Function Network IS Provider IETF Scope (?) Network IS Provider Ia: Interface between UE and Network Ix : Interface between IS Function and Information Database IEEE / IETF Scope

Case 4: Centralized Information Service with co-located Information Database UE Network IS Provider Ia IS Function IS Function/ Information Database Ia : Interface between UE and Network IS Provider IEEE / IETF Scope

Discussion Points Are our assumptions correct? Relationship, Scope, Dependency, Single-hop vs. multi-hop Should we support all four use-cases? Some use-cases may be difficult to support Is there any other use-case we are missing here?