Title: uid 440062 User Data Convergence (udc) Framework for Model Handling and Management session Rapporteur Report




Дата канвертавання19.04.2016
Памер29.84 Kb.


3GPP TSG-SA5 (Telecom Management) S5-101135

Meeting SA5#71, 10-14 May 2010, Montreal, Canada revision of S5-10xyzw

Source: Istvan Aba, Deutsche Telekom

Title: UID_440062 User Data Convergence (UDC) - Framework for Model Handling and Management session Rapporteur Report

Document for: Approval



Agenda Item: 6.7.1

1Progress status


Percentage of completion: 100% (previously 80%)

Summary of progress: -

Outstanding issues:

2Minutes


The RG session was held on May 11 Q3 and May 12 Q3

Tdoc

Title/Discussion/Conclusion

Source

S5-101380

Draft LS proposal to CT4 on UDC Provisioning ForntEnd

To be revised in S5-101467

After the first session E/// objected to the LS They see no need to have a provisioning GW and they don’t agree of the removal of the provisioning FE.

The draft LS has been rejected.

Nokia Siemens Networks










S5-101374

Reply LS on Update on status of Service User Profile Management

Approved, TS 32.181 and 32.182 shall be attached in S5-101455 and present to SA5 Plenary

Alcatel-Lucent

S5-101134r1

Agenda UDC Framework for Model Handling and Management (440062)

Approved

Rapporteur

S5-101236

pCR to 32181 - input on UDC Information models

Approved

Nokia Siemens Networks, Deutsche Telekom, Ericsson

S5-101237

pCR to 32181 - relation of UDC and SUM

Approved

Nokia Siemens Networks, Deutsche Telekom

S5-101267

pCR on 32.181, UDC Framework - Subscription and Notification Related Data

ALU: ‘requested data’ to be replaced by requested to be observed, better wording on notification conditions.

To be revised in S5-101467

Huawei, Deutsche Telekom, China Mobil

S5-101467

pCR on 32.181, UDC Framework - Subscription and Notification Related Data

Approved

Huawei, Deutsche Telekom, China Mobile

S5-101271

pCR on 32.181, UDC Framework - Information and Data Model Figure Change

Approved

Alcatel-Lucent, Deutsche Telekom, Nokia Siemens Networks, Ericsson, Huawei

S5-101283

pCR on 32.181, Chapter 8 Consolidated data model management

The late document was presented by DT.

ALU: Explain ProvGW as for provisioning of all user data

NSN: ProvGW - The main point is that this is integral part of the UDR and this is the single point for provisioning of all services of UDR.

To be revised in S5-101466

Deutsche Telekom, Nokia Siemens Networks

S5-101466

pCR on 32.181, Chapter 8 Consolidated data model management

The revised document was presented by DT.

E///: We can’t find the functional entity "Provisioning Front-End" using Ud

interface to access UDR for provisioning purpose which is defined in

23.335; don’t agree of the removal of the provisioning FE.

Pprovisioning entityGW being part of the UDR or not or being the FE is a deployment scenario. We disagree to the pRC that violates the latest approved UDC architecture.

DT: Prov FE are not removed, they are just applications in the figure using

Ud. This will be clarified in the text

ALU: Arrows between Application boxes and the UDR should be

marked Ud

DT: will be done

E///: We don't agree to the proposal to have a "Provisioning
Gateway" being deployed in UDR and accessing user data
directly., Having both ProvFE and PG, as proposed as an option during the session, also violates the UDC architecture because PG is a totally new entity and also there would be two interfaces for provisioning, which is redundant.


DT and others: This is a function every data base provides and has always

been part of GSM//3GPP. In the past 12.02 has provided the

functionality, currently SuM should do it, but it is not there yet..

DT and others: Only having ProvFE for provisioning would at least not
make the IOC EndUser accessible to the operator provisioning.

ProvFEs like all other Appl/FE are restricted to their ADM and ADMs


are true subsets of CDM,
 ProvFEs use the Ud interface with their ADM going through the
Application Data View with severe overhead,
 ProvFEs based on their access through their ADM have access to
Identifiers, ServiceProfiles but cannot create/delete EndUser


Only the function ‘Provisioning Gateway’ meets all provisioning
requirements from Clause 6.7 of 23.985


ALU: The ProvGW is a logical function.

DT: logical will be inserted

The contribution is agreed to be revised in S5-101540 with Ericsson objecting

The discussion continued offline, at a break-out session and over email. In that discussion there was still no agreement.


Deutsche Telekom, Nokia Siemens Networks











3Action items


Item

Description

Release

Owner

Status

Target

71.1

Implement the approved pCR and forward 32.181 for approval

Rel-9

Rapporteur

New

SA5#64



- -


База данных защищена авторским правом ©shkola.of.by 2016
звярнуцца да адміністрацыі

    Галоўная старонка