1 / 8

PSN Structure Strawman

PSN Structure Strawman. Serge Manning January 2003. PSN WG Structure. PSN WG. Bearer SWG. Signaling SWG. IP Services SWG. WG. Handles issues where packet expertise across all SWGs is needed. Deals with interactions between bearer and control planes

alta
Download Presentation

PSN Structure Strawman

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. PSN Structure Strawman Serge Manning January 2003

  2. PSN WG Structure PSN WG Bearer SWG Signaling SWG IP Services SWG

  3. WG • Handles issues where packet expertise across all SWGs is needed. • Deals with interactions between bearer and control planes • Coordination of MMD is the key function here • Work Flow • Remands contributions of specific issues to appropriate SWG(s). • Approves work output from SWGs.

  4. Bearer SWG • Initially, all stage 2 & 3 work from TSG-P moves into this SWG. • IS-835, packet bearer Stage 2 and 3 development • MMD bearer level stage 2 & 3 development • BCMCS, potentially

  5. Signaling SWG • Initially, MMD stage 2 & 3 work from TSG-N moves into this SWG • SIP related stage 2 & 3 development • Service Architecture related stage 2 & 3 development • Interfaces with services layer into the core network (e.g., SIP services) • Will not define the services themselves

  6. IP Services SWG • IP services stage 2 & 3 development • MMS • IP Location based services • Support for Services APIs (e.g., support for OSA) • Should not deal with bearer or session level issues in the core network

  7. Typical Meeting Flow • WG will open • Administrative tasks • Remand contributions to SWGs • Process relevant contributions in the WG • Recess • SWGs will meet in parallel • Administrative tasks • Process contributions • Adjourn • WG will close • Administrative tasks • Receive any outputs from SWG

  8. Open Issues • RADIUS/Diameter work

More Related