Answer the Questions Regarding Pending Issues on Access Control Group Name: WG4 SEC Source: LG Electronics Meeting Date: 2014-07-15 Agenda Item: SEC#11.4.

Slides:

Advertisements

Similar presentations

Access Control Mechanism Discussion

Advertisements

CMDH Refinement Contribution: oneM2M-ARC-0397

SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:

Summary on the M2M CMDH Policies Management Object (MCMDHMO)

Is a Node or not Node? ARC Node_resolution Group Name: ARC Source: Barbara Pareglio, NEC, Meeting Date: ARC#9.1 Agenda.

Access Control Mechanism for User Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: Agenda Item:

Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD.

REQ WG Reuse of underlying networks, 3GPP

REQ WG Reuse of underlying networks, 3GPP

REQ WG Reuse of underlying networks, 3GPP From: Omar Elloumi (ALU) Source: Alcatel-Lucent (ATIS) Meeting Date: Agenda Item:

Device Management using mgmtCmd resource

On Persistent AE Identifiers Group Name: SEC#12.2 Source: Phil Hawkes, Qualcomm Inc (TIA), Francois Ennesser,

OneM2M-ARC BRequest_Resource Architecture Proposal to address Broadcasting/Multicasting Requirements Group Name: WG2 Source: Takanori Iwai, NEC,

Resource Announcement Procedures Group Name: WG2 Source: Rajesh Bhalla, Hao Wu - ZTE Meeting Date: Agenda Item: TBD.

App-ID Use Cases, Syntax and Attributes SEC App-ID_Use_Cases,_Syntax_and_Attributes Group Name: Architecture Source: Darold Hemphill, iconectiv,

oneM2M-OIC Interworking Technical Comparison

Common Service Entities

In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:

PRO R01-URI_mapping_discussion Discussion on URI mapping in protocol context Group Name: PRO and ARC Source: Shingo Fujimoto, FUJITSU,

3GPP Rel-13 Interworking discussions

In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:

Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management.

TS0001 Identifiers way forward Group Name: WG2 Source: Elloumi, Foti, Scarrone, Lu (tbc), Jeong (tbc) Meeting Date: Agenda Item: ARC11/PRO11.

Supporting long polling Group Name: ARC WG Source: SeungMyeong, LG Electronics, Meeting Date: x-xx Agenda Item: TBD.

Step by step approach Group Name: WG2 Source: Michael hs. Yang, LG uplus, Jaeseung Song, NEC Europe, Meeting.

Status Report on Access TP8 Group Name: WG2 Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:

Node-Specific Resource Group Name: ARC&MAS Source: LGE, Meeting Date: Agenda Item: Contribution.

Primitive End-to-End Security Requirements Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting.

App-ID Use Cases, Syntax and Attributes ARC R01-App-ID_Use_Cases,_Syntax_and_Attributes Group Name: Architecture Source: Darold Hemphill, iconectiv,

OIC INTERWORKING OPERATIONAL PROCEDURE (ADDRESSING AND DISCOVERY) Group Name: Architecture WG Source: Kiran Vedula, Samsung Electronics,

M2M Service Session Management (SSM) CSF

E2EKey Resource Group Name: SEC WG Source: Qualcomm Inc., Wolfgang Granzow & Phil Hawkes Meeting Date: SEC#20.3, Agenda Item: End-to-End Security.

Routing Problem of the Current Architecture Group Name: ARC Source: Hongbeom Ahn, LG Electronics, Meeting Date: Agenda.

M2M Service Subscription Profile Discussion Group Name: oneM2M TP #19.2 Source: LG Electronics Meeting Date: Agenda Item:

Realizing Ms Interface with OMA DM Group Name: MAS WG Source: Seungkyu Park, LG Meeting Date:

App and Management End- to-End Security Requirements Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm,

Protocol Issues related to Plugtest Group Name: TST Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date: Agenda.

M2M Service Layer – DM Server Security Group Name: OMA-BBF-oneM2M Adhoc Source: Timothy Carey, Meeting Date:

Streaming Session Support in oneM2M Framework Group Name: WG2 Source: George Foti, Ericsson Meeting Date: Work Item :WI GPP_Rel13_IWK.

M2M Service Session Management (SSM) CSF Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:

Issues of Current Access Control Rule and New Proposal Introduction Group Name: ARC 21 Source: Wei Zhou, Datang, Meeting Date:

Adding Non-blocking Requests Contribution: oneM2M-ARC-0441R01R01 Source: Josef Blanz, Qualcomm UK, Meeting Date: ARC 7.0,

Authorization Architecture Discussion Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 28 MAY, 2014 Agenda.

Subscription and Notification Issue Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: ~23 Agenda Item:

Consideration Security Issues on Registration Group Name: WG4 (SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

Management CSF(s) Architectural choices Group Name: WG2 (ARC), WG5(MAS) Source: Catalina Mladin, InterDigital Comm., Meeting.

Specifying the Address of Management Client of Managed Entity Group Name: ARC Source: Hongbeom Ahn, SK Telecom, Meeting Date: TP#21 Agenda.

Resource subscription using DDS in oneM2M

[authenticationProfile] <mgmtObj> specialization

3GPP MBMS protocol stack

Service Framework Proposal

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

Service Enabled AE (SAE)

End-to-End Security for Primitives

Group multicast fanOut Procedure

3GPP interworking in R3 Group Name: ARC

Possible options of using DDS in oneM2M

Issues of <locationPolicy> Discussion

Proposed design principles for modelling interworked devices

MAF&MEF Interface Specification discussion of the next steps

3GPP Rel-13 Interworking discussions

OneM2M-ARC BRequest_Resource Architecture Proposal to address Broadcasting/Multicasting Requirements Group Name: WG2 Source: Takanori Iwai,

Considering issues regarding handling token

Summary of Access Control Rules Processing

CMDH Refinement Contribution: oneM2M-ARC-0397R01

MinitorEvent(UE_Reachability)

Service Layer Dynamic Authorization [SLDA]

3GPP V2X Interworking Potential Impact

Summary of the MAF and MEF Interface Specification TS-0032

Presentation transcript:

Answer the Questions Regarding Pending Issues on Access Control Group Name: WG4 SEC Source: LG Electronics Meeting Date: Agenda Item: SEC#11.4

Objective This presentation is to answer the Open Issue 5 questions that are raised by Qualcomm‘s slide (SEC ) – How does the hosting CSE obtain information about the location of the entity where the request message originated? – What shall be the resolution of location information used for access control? 2

Problem 3 The Hosting CSE does not know the location of Originator How to describe the region (or area) If the Originator is in the region defined the parameter, but denied due to ‘no location’

The well-known or simplest way of representing the area(or region) is circle Used by many Location-relevant standards and applications Area Description 3 tuples are needed 1)Longitude 2)Latitude 3)Radius (m)

5 Area Description Multiple Areas

TS-0001 defines a resource type for obtaining location of a Target Node - - Configuration information how to obtain location information of a target M2M node 6 Acquisition of Location Information of the Originator locationSource locationUpdatePeriod locationTargetID locationServer locationContainerID locationContainerName Basic Information - Source (Network/Device/Sharing) - Period to obtain location information For Network-based Location - ID of the Target M2M Node - ID of Location Server located in U/N How to link with a resource - URI of the created - Name of the

The Hosting CSE shall create the to obtain the location of the originator Set the attributes of for acquisition location of the request Originator – locationSource == Network For reliability  trust the GPS and any AE-owned location value? – locationTargetID == Originator’s Node-ID Node-ID can be IMEI or IP address that is global unique 7 Acquisition of Location Information of the Originator

Make the Hosting CSE easily determine whether the Originator is in the specified area(s) for access control – OMA NetAPI for Terminal Location Interface between Hosting CSE and Location Server in the Network (Mcn) specifies a resource type as an area-based location notification service, ‘CircleNotificationSubscription’ Hosting CSE subscribes to the notification (about originator location) service – When the Originator enters and leaves the defined area the Location Server notifies of the Hosting CSE the location change. 8 Acquisition of Location Information of the Originator

9 Area Notification Action Enter Leave Hosting CSE can easily know whether the Originator is in the area or not

Backup Slide Location Capability 3 Ways of Obtaining Location Information – Network-Based / Device-Based / Sharing-Based AE CSE AE Location Requestor Target M2M Node ( ) IN Create Location Server Location Server locationSource = ‘Network’ locationTargetID = ’ ’ locationServer = ‘locserver.lg.org’ Location Request (OMA API for Terminal Location) Performing Location (e.g., Cell-ID, OTDOA) Location Response Content = (x,y)