1 / 7

Conclusions from 3GPP/3GPP2 Common IMS Workshop

Conclusions from 3GPP/3GPP2 Common IMS Workshop. Chairs: Betsy Covell (Alcatel-Lucent) Stephen Hayes (Ericsson) SA Breakout Chairs: Dick Knight (BT) Lee Valerius (Nortel Networks) CT Breakout Chairs: Atle Monrad (Ericsson) Jack Nasielski (Qualcomm). Conclusions (1).

milek
Download Presentation

Conclusions from 3GPP/3GPP2 Common IMS Workshop

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. Conclusions from 3GPP/3GPP2 Common IMS Workshop Chairs: Betsy Covell (Alcatel-Lucent) Stephen Hayes (Ericsson) SA Breakout Chairs: Dick Knight (BT) Lee Valerius (Nortel Networks) CT Breakout Chairs: Atle Monrad (Ericsson) Jack Nasielski (Qualcomm)

  2. Conclusions (1) SA1/SA2/SA3/SA5 CRs reviewed and endorsed – See CIMS080056 SA1 targeted CRs revised and endorsed SA2 targeted CRs revised and endorsed SA3 targeted CRs endorsed and some comments generated. Need thorough technical review in SA3. SA5 workplan discussed. No CRs discussed.

  3. Conclusions (2) • CT1/CT3/CT4 CRs reviewed and endorsed – See CIMS080079 • CT1 targeted CRs revised and endorsed • CT3 targeted CRs expected at the next CT3 meeting • CT4 targeted CRs presented for information, pending architecture decision in SA2

  4. Conclusions(3) • SA WID Endorsed (CIMS-080080) • CT WID Endorsed (CIMS-080081) • Flexible Alerting and CRBT should be broken out to separate WIDs • Additional decomposition may occur as needed

  5. Conclusions(4) • Terminology: • “cdma2000 access” is a generic term to indicate the cdma family of accesses and can be used for conditions dependent on use of the access • “When used in the context of a 3GPP IPCAN”/ “When used in the context of a 3GPP2 IPCAN” is the generic term to be used when the functionality is dependent on the presence of a 3GPP/3GPP2 specified IP Connectivity Access Network (IPCAN) (eg, GPRS, EPC for 3GPP or cdma2000 PDS, CAN for 3GPP2). • “When used in the context of a 3GPP system”/ “When used in the context of a 3GPP2 system” is the generic term to be used when the functionality is dependent on the presence of a 3GPP/3GPP2 specified system (eg, GSM, UMTS, EPS for 3GPP or cdma2000 system for 3GPP2).

  6. Actions • SA1/SA2/SA3/SA5/CT1/CT3/CT4 to handle CRs/WIDs endorsed by the workshop as expediently as possible. • 3GPP2 to send a LS to SA#29 (March 10, 2008) indicating any areas where additional requirements are expected (SA must grant SA1 an exception or these automatically go into Rel 9)

  7. Coordination • For services (Flexible Alerting, etc.) SA1 endorsement of requirements is needed. • SA1, SA2 to clarify, is dual addressing for signal/bearer permitted within common IMS for simultaneous IPv4/IPv6 • SA2 guidance on how to handle proxy-SLF is needed • For R-UIM CRs, SA3 deliberation is needed, • The workshop concluded it was appropriate to document in 3GPP specifications the data and the derivation of the data used in the various security process, but not the physical storage of that data • For new IMS services (e.g., CAT over IMS), SA1 needs to decide on the documentation structure.

More Related