60 likes | 186 Views
Work plan for ”3 GPP2 All IP Service architecture framework (stage 0)”. 2001.8 Jae-young Ahn ETRI. Background. In Montreal All IP AdHoc Meeting (July 2001)
E N D
Work plan for”3GPP2All IP Service architecture framework (stage 0)” 2001.8 Jae-young Ahn ETRI
Background • In Montreal All IP AdHoc Meeting (July 2001) • TTA suggested to review 3GPP’s working on ” IP Based Multimedia Services Framework” by submitting the document 3GPP TR22.941 as FYI to All IP AdHoc • AdHoc recognized the need of action for it • recognizing that the task is an extra track of framework which can be categorized as ”stage 0” • Adhoc agreed to start investigation and some documentation for it • Jae-young Ahn(TTA) has been assigned to lead the activity
Motivation First cdma2000 1x phone in Korea: What’s the break through? • Current cdma2000 1x has more than 15 times of bandwidth capacity than legacy cellular. • But the End user benefit for using this is still questionable in view of service enhancement. • In the operators’ view, market for new subscription / user terminal is getting saturated so that the stimulation for new purchase are desirable. Channel capacity is Invisible for the users!
Scope of the Activity • Establishing a common vision for the promising and feasible service feature of 3GPP2’s “All IP” network , and identifying the functional requirement for the realization • It is not to standardize any architecture or protocols, but to show promising service and enabling functions for the future of 3GPP2 All IP capability • That could be the first step of leading long term vision of 3GPP2 All IP network and service evolution • Work result is to forward to TSG-S/vision group
Work Flows Vision & service architecture framework future vision group (1) • Start brainstorming • Service requirement collection : users’ view • Service capability scenario collection: suppliers’ view • Evaluation of service receptivity & impact • feasible & promising service selection Develop target service scenarios (2) Evolution plan Compare its supporting function submission (3) Requirements / service enablers Service architecture & capability enhancement
Work Plan • Request for initial comment for the scope & plan hereby • Discussion via exploder (a separated one is required) • Resolving all the initial comment on the work plan • Collecting requirements and generic service scenarios • Identify promising/target service features and priorities • Assumeing general time frames and suitable architecture based on the evolution plan (avoid the undesireable long discussion for this) • Development of an evaluation table • Examining each service scenario in light of user benefit, service receptivity, implementation cost, service value, and for more categories • Identify current/progressive service features • Verifying the selected service scenarios with current/available service features & enablers in 3GPP2 All IP • Formulation of requirements to support existing and promising services