tsg-s oma ad-hoc recommendations tsg-s oma adhoc

TSG-S OMA AD-HOC RECOMMENDATIONS

TSG-S OMA AdHoc

CONTENTS Potential Benefits of 3GPP2 Relationship with OMA SC Action Remand Risk Factors and Company Concerns Classification of Potential Shared Work Items Basic Preliminary Assumptions 3GPP2 Risk Mitigation Plan 3GPP2 Risk Mitigation Matrix OMA/3GPP2 Organizational Links and Touch Points OMA Liaisons Received To Date Important Note to 3GPP2 Member Companies Workshops with OMA Next Steps Immediate Decisions Requested From SC Considerations Requested from the SC and OPs SC Approval Process for Shared/Transfer of Work

POTENTIAL BENEFITS OF 3GPP2 RELATIONSHIP WITH OMA

Reduction of effort Application-layer specs written in OMA with input from both

3GPP and 3GPP2 communities - no duplication of effort in 3GPP2

Timely engagement with OMA ensures that 3GPP2 is adequately represented in OMA spec development

Better service interoperability Same application layer standards implemented in all wireless

networks (CDMA, UMTS, GSM/GPRS), leading to greater interoperability and more operator revenue

Economies of scale that arise from common device and server application-layer software Vendors can offer a common set of software to all their server

and device customers, need not have differing versions for 3GPP and 3GPP2 networks

SC ACTION REMAND

The following action was remanded to TSG-S from the May 2003 SC meeting:

ACTION 2003/05-12 The TSG-S OMA Ad Hoc is directed to continue its

efforts by evaluating the risks identified in contribution SC-20030120-008D and by taking into account that it may be too premature for 3GPP2 to communicate directly with the OMA. A proposal from the Ad Hoc is to be submitted by June 30 2003 for consideration by the SC either via e-mail or, if necessary, via teleconference, for determination by the end of the July meeting cycle.

RISK FACTORS AND COMPANY CONCERNS

RISK FACTORS (SC-20030120-008D, page 5) Loss of control over schedule Solution not as optimized for CDMA networks as

would be if developed within 3GPP2 OMA product not meeting 3GPP2 requirements Lack of understanding of 3GPP2 requirements by

OMA Loss of control of solution Solution may be driven by existing legacy solutions

COMPANY CONCERN: Some companies may consider that it may be too premature for 3GPP2 to communicate directly with the OMA.

CLASSIFICATION OF POTENTIAL SHARED WORK ITEMS

TYPE DESCRIPTION EXAMPLE ACTION

1 All or most of the work item requirements are cdma2000 specific requirements

Wideband Audio Codec

These work items should be handled within 3GPP2

2 Some of the work item requirements are cdma2000 specific (e.g., architectural linkages)

MMS See Risk Mitigation strategies and table

3 Work item requirements include minimal or no cdma2000 specific issues

DRM See Risk Mitigation strategies and table

BASIC PRELIMINARY ASSUMPTIONS

OMA LIAISON INQUIRIES: 3GPP2 TSGs should be allowed to respond to technical inquiries from OMA in an expedited and unencumbered manner as coordinated by the SC or its delegate (e.g., SC OMA AdHoc or TSG-S OMA AdHoc).

3GPP2 TSG LIAISONS: 3GPP2 TSGs should be allowed to initiate technical liaisons to convey information to OMA or request information from OMA as coordinated by the SC or its delegate (e.g., SC OMA AdHoc or TSG-S OMA AdHoc).

3GPP2/OMA SHARED WORK ITEMS: There should be explicit SC approval of the initiation of shared work activities that would normally be covered within 3GPP2.

3GPP2 RISK MITIGATION PLAN

1. 3GPP2/OMA LIAISON: 3GPP2 establishes an official liaison with OMA to actively communicates issues.

a. As a part of this process, 3GPP2 stresses the importance of equal priority of both 3GPP and 3GPP2 technical requirements and development schedules. This action may include direct input to the OMA Technical Plenary regarding the on-going development of their organization and operating procedures.

b. In addition, 3GPP2 stresses OMA focus on 3GPP/3GPP2 interoperability.

c. The liaison can be used to highlight 3GPP2 issues of concern to any OMA group including the Technical Plenary.

2. OMA/3GPP2 REVIEW OF WORKPLANS: SC Delegate AdHoc monitors OMA schedule and raises issues accordingly.

a. 3GPP2 and OMA both seek to identify work areas of commonality and overlap. SC Delegate AdHoc will coordinate technical liaisons between OMA and the 3GPP2 TSGs.

b. SC Delegate AdHoc monitors OMA workplan and participates in work item prioritization process at OMA. OMA will be solicited to insure that items common between 3GPP2 and 3GPP are given the highest priority.

c. SC Delegate AdHoc documents dependencies and revisions for OMA specifications.

3. 3GPP2/OMA JOINT OR TRANSFER WORK STRATEGY: 3GPP2 retains the following options:

a. Any joint work between 3GPP2 and OMA or transfer of work from 3GPP2 to OMA must be approved by the 3GPP2 SC.

b. 3GPP2 may define its own requirements and submit them for incorporation into OMA requirements. Alternatively, the SC Delegate AdHoc may facilitate the participation of 3GPP2 in the OMA requirements development process.

c. SC Delegate AdHoc may facilitate 3GPP2 periodic reviews of OMA development projects to identify potential shortcomings or recommend modifications.

d. 3GPP2 always retains the right to initiate any work item from scratch or at any interim development point, regardless of the potential overlap.

4. JOINT PARTICIPATION IN OMA WORK: 3GPP2 companies actively participate in OMA. However, these companies are not authorized to directly speak for 3GPP2.

3GPP2 RISK MITIGATION MATRIX

RISK Type 2: Some cdma2000 Reqs

Type 3: No cdma2000 Reqs

Loss of control over schedule 1a, 1c, 2b, 3c, 3d, 4 2b, 1c

Solution not optimized for cdma2000 networks 1a, 1c, 3c, 4 Not applicable

OMA product doe not meet 3GPP2 Requirements 1a, 3c, 3d, 4 Not applicable

Lack of understanding of 3GPP2 Requirements by OMA 1a, 1b, 3c, 3d, 4 Not applicable

Loss of control over OMA solution 3c 3c

Solution may be driven by legacy solutions 1b, 1c, 3c, 3d, 4 Not applicable

Too premature for 3GPP2/OMA relationship 3GPP2 Risk Mitigation Plan 3GPP2 Risk Mitigation Plan

3GPP2/OMA ORGANIZATIONAL LINKS AND TOUCH POINTSOMA 3GPP2 EQUIVALENT 3GPP2

CONTACT POINT BOARD OF DIRECTORS ORGANIZATIONAL

PARTNERS ORGANIZATIONAL

PARTNERS TECHNICAL PLENARY STEERING

COMMITTEE STEERING

COMMITTEE Operations and Processes (Support Committee) TSG-S PMT Release Planning (Support Committee) TSG-S PMT Requirements WG TSG-S WG1, TSG-X

ERA Architecture WG TSG-S WG2 Security WG TSG-S WG4

TSG-S WG5 OAM&P Interoperability WG No Equivalent Developer’s Interest Group No Equivalent Instant Messaging and Presence Services WG TSG-C, TSG-X PSN Mobile Web Services WG TSG-X OSA Mobile Commerce WG No Equivalent Device Management WG TSG-C SWG1.4,

TSG-S WG4, TSG-S WG5

Data Synchronization WG TSG-C SWG1.3 Mobile Protocols WG TSG-X SWG-3 Games Services WG No Equivalent Location WG TSG-C SWG1.6, TSG-X Mobile Application WG - Mobile Application Environment TSG-C SWG1.4 - Multimedia Messaging Service TSG-C WG1,

TSG-X MMS ADHOC - Push Services TSG-X PSN,

TSG-C WG2, TSG-A,

TSG-S WG4 - STI (Standard Transcoding Interface) TSG-X - UAProf No Equivalent

SC DELEGATE

IMPORTANT NOTE TO 3GPP2 MEMBER COMPANIES

Any relationship between 3GPP2 and OMA may require additional commitment or reallocation of resources/personnel by 3GPP2 member companies.

Issues of concern Currently, even though the OMA charter includes the statement to “Be

the catalyst for the consolidation of standards fora; working in conjunction with other existing standards organizations and groups such as IETF, 3GPP, 3GPP2, W3C, JCP”, the OMA membership is heavily populated with 3GPP participants. This is the membership that makes the day-to-day decisions. 3GPP2 member companies must be prepared to participate in OMA activities.

The 3GPP2 Risk Mitigation Plan forms only the basis for “Rules of Engagement”. Like 3GPP2, all work in OMA is contribution driven. 3GPP2 member companies must be prepared to submit contributions into OMA that generally support the 3GPP2 objectives in OMA.

In addition, the coordination effort on the 3GPP2 side (i.e., the SC Delegate AdHoc activities) plus the additional technical coordination activities and work load that will be required on the part of the 3GPP2 TSGs will require also an effort from the current 3GPP2 membership.

OMA LIAISONS RECEIVED AS OF 22 AUGUST 2003

DATE 3GPP2

ADDRESSEEDESCRIPTION

11/15/02 SC + TSG-S LS to 3GPP and 3GPP2 from OMA Technical Plenary proposing cooperation on technical development

(April 03) SC Draft of OMA Cooperation Framework

Undated TSG-C LS to TSG-C with a copy to TSG-S from OMA MAG requesting input on the OMA DRM (Digital Rights Management) Content Format

6/30/03 TSG-S LS to 3GPP and 3GPP2 from OMA Requirements group requesting input on the OMA Privacy Requirements

7/17/03 TSG-S LS to 3GPP and 3GPP2 from OMA Requirements group requesting input on the OMA Push to Talk over Cellular (POC) Requirements

7/22/03 TSG-S LS to 3GPP and 3GPP2 from OMA Requirements group regarding Device Management as FYI

8/18/03 TSG-S Request to participate in OMA M-commerce survey from OMA M-commerce WG

WORKSHOPS WITH OMA

A workshop between OMA and 3GPP2 in the near future would provide valuable opportunity for mutual education, and would help address concerns of 3GPP2 companies regarding OMA. This meeting is intended for information exchange and to explore specific procedures and processes for 3GPP2 management of shared work/transfer of work activities in OMA.

Examples of how 3GPP is interacting with OMA: 3GPP working groups have prepared inventories of their current work to

identify overlaps with OMA work and areas of possible work transfer to OMA

Joint 3GPP-OMA Workshop will cover

Review of 3GPP and OMA scopes and working methods Presentation of 3GPP and OMA work plans, identification of

overlaps and dependencies 3GPP and OMA cooperation with external bodies Discussion of future 3GPP-OMA collaboration

NEXT STEPS

21 August 2003: Submit request to SC Chair and Secretariat for SC decision for three (3) Immediate Decision Items noted on slide 14. Request SC decision on all three (3) items based on a response schedule determined by the SC Chair per WPD Article 19E to be responsive to OMA by their September 2003 meeting in Berlin.

21 August 2003: As a part of the request above, the SC Chair and the Secretariat will be requested to advise the SC and the OPs of the actions on-going in the TSG-S OMA AdHoc as indicated in slide 15 and to add an agenda item to the October SC and OP meetings to discuss these issues.

21 August 2003: TSG-S will release OMA Liaisons currently open at the Plenary level to the applicable TSG-S WGs for review and action as appropriate. However, final responses will not be released to OMA until approval of Immediate Decisions items by the SC. The TSG-S Liaison Report to TSG-C will recommend TSG-C consideration of a similar action for the DRM Liaison Statement.

19 September 2003: TSG-S OMA AdHoc releases refine recommendations for processes for consideration, approval, and management of shared work/transfer of work relationship with OMA for review by SC and OP.

20-21 October 2003: TSG-S will solicit SC and OP direction on a Shared Work/Transfer of Work relationship with OMA, as indicated on slide 15 and 16.

17 October 2003: As a part of SC remanded action for TSG-S to investigate issues related to potential relationships between 3GPP2 and OMA, the OMA AdHoc will attempt to schedule a 3GPP2/OMA workshop in conjunction with the 3GPP2 super-meetings in Maui on 5 December 2003.

IMMEDIATE DECISIONS REQUESTED FROM SC

1. Based on the submission of this updated proposal, the SC will consider SC remanded ACTION 2003/05-12 to be closed.

2. Authorize an SC Delegate to coordinate communications between 3GPP2 TSGs and OMA (e.g., TSG-S OMA AdHoc, new SC level OMA AdHoc, or other).

3. Approve an official liaison relationship between 3GPP2 and OMA as indicated below: Includes SC authorization to initiate all actions under items 1 and 2 in Risk Mitigation Plan

on slide 7. Includes SC authorization for 3GPP2 TSGs to handle inquiries received from OMA and to

initiate communications to OMA groups as detailed in the first two (2) bullets of the Basic Preliminary Assumptions on slide 6.

The OMA Liaisons received to date (as indicated in slide 11 with the exception of the technical cooperation proposal) will be the first items of work.

The SC Delegate will negotiate the Liaison relationship under control of the SC.

CONSIDERATIONS REQUESTED FROM SC AND OPs

1. TSG-S OMA AdHoc intends to make recommendations regarding shared work/transfer of work relationships with OMA at the upcoming SC and OP meetings based on the following considerations: Only Type 2 and Type 3 work items, as defined on slide 5, will be

considered for shared work/transfer of work status. Candidate work items for shared work/transfer of work must be

considered and approved by the SC on a case-by-case basis as indicated in the 3rd bullet of the Basic Preliminary Assumptions on slide 6 using a process that is compliant with the requirements set forth in the SC Approval Process for Shared/Transfer of Work on slide 16.

2. The SC will need to consider authorization of an SC Delegate AdHoc to manage the PMT aspects of shared work/transfer of work activities (e.g., TSG-S PMT or other SC Delegate).

3. The SC and OP will define the conditions and procedures on the use of others’ work including IPR, copyright, etc.

SC APPROVAL PROCESS FOR SHARED/TRANSFER OF WORK

Work items being considered for shared works and/or transfer of work must be approved on case-by-case basis. It is recommended that the 15-day SC approval be adopted.

The recommendation for a work items to be considered by the SC for shared works and/or transfer of work must include the following for SC consideration: Detailed definition of the scope of work sharing/transfer Definition of expected outputs by OMA with a requested delivery schedule for each List of 3GPP2 documents that are recommended for OMA review in support of this effort Recommendation for approval from the 3GPP2 TSG(s) that would be responsible for the

work item

The recommendation to the SC must be submitted by the SC Delegate AdHoc.

The shared/transfer work effort in OMA must be monitored and the status periodically reported to the SC and approving TSGs by the SC Delegate AdHoc.

tsg-s oma ad-hoc recommendations tsg-s oma adhoc

Documents