1 / 50

Current Status on TSG-N/TR45.2

Current Status on TSG-N/TR45.2. CWTS cdma2000 Seminar 2000/07/26 Lee, Hee Joung ( 李 喜 禎 ) LGIC, Ltd. Outline. 3GPP2 Overview & TR45.2/TSG-N Organizational Structure Published Stand-Alone Documents PN-3590 (to be ANSI-41-E) Status Post ANSI-41-E Development

gudrun
Download Presentation

Current Status on TSG-N/TR45.2

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. Current Statuson TSG-N/TR45.2 CWTS cdma2000 Seminar 2000/07/26 Lee, Hee Joung (李 喜 禎) LGIC, Ltd.

  2. Outline • 3GPP2 Overview & TR45.2/TSG-N Organizational Structure • Published Stand-Alone Documents • PN-3590 (to be ANSI-41-E) Status • Post ANSI-41-E Development • Emergency Service Ad Hoc Status (AHES) • Lawfully Authorized Electronic Surveillance (LAES) Ad Hoc Status • Authentication Focus Group Status • Q&A

  3. 3GPP2 Overview & TR45.2/TSG-N Organizational Structure

  4. Why is 3GPP2 ? • 3GPP2 Focus = ANSI41 • 3GPP1 Focus = GSM • Joint 3G Focus = ITU

  5. Who is 3GPP2 ? • CWTS • TTC + • ARIB + • TTA + • TIA +

  6. Purpose of 3GPP2 ? • The purpose of 3GPP2 is to prepare, approve and maintain globally applicable Technical Specifications and Technical Reports for a 3rd Generation Mobile System based on the evolved ANSI-41 Core Network and the relevant radio access technologies to be transposed by relevant standardization bodies. (CWTS, TTA, TTC, etc.)

  7. Structure of 3GPP2 ? 3GPP2 Organizational Partners Direct • 3GPP2 Steering Committee • TSG-S (Systems and Services) • TSG-N/WIN (ANSI41 Network & WIN) • TSG-C (cdma2000) • TSG-A (Access Network Interface) • TSG-P (Wireless Packet Data Network) • ALL-IP (Ad Hoc on ALL-IP Network)

  8. The “Pipeline” Input = SDO Requirements

  9. The “Pipeline” Output = TSG-S Release Requirements

  10. Roll-Out of ANSI-41 Services Equipment Development TIA Standards Development Roll-Out of Rel 00 Services Roll-Out of Rel 99 Services Equipment Development Equipment Development 3GPP2 Standards Development 3GPP2 Standards Development The “Pipeline” Former ANSI-41 TSG-S Release A Requirements Release 99 Release 00 2002 2001 2000 1997 1999 1996 1998 1995 TSG-S Release B Requirements

  11. Roll-Out of Former ANSI-41 Services Equipment Development TIA Standards Development Roll-Out of New 3GPP2 Services Equipment Development 3GPP2 Standards Development The “Pipeline” Existing Standards New 3GPP2 standards 3GPP2 Specifications 2002 2001 2000 1997 1999 1996 1998 1995

  12. Roll-Out of Old ANSI-41 Services Equipment Development TIA Standards Development Roll-Out of NEW 3GPP2 Services Equipment Development 3GPP2 Standards Development The “Pipeline” Before Rel 99 China National Standards 中國 國家 標準 After Rel 99 中國 國內 規格 追加 2002 2001 2000 1997 1999 1996 1998 1995

  13. TSG-N/TR45.2 TSG-N/TR45.2 Ad Hoc : LAES Ad Hoc : E911 TR 45.2.3 (WG 3) Stage-3 (Encoding & Procedures) Development TR 45.2.1 (WG 1) Stage-1 Development TR 45.2.5 (WG 5) Wireless Intelligent Network TR 45.2.2 (WG 2) Stage-2 Development TR 45.2.4 (WG 4) Message Accounting TR 45.2.6 (WG 6) International Application Authentication Focus Group ESN Assignment

  14. Current Project Status

  15. Published Stand-Alone Documents Documents published after ANSI-41.D • TSB-76: PCS Multi-band - Based on IS-41-C • IS-725-A: OTASP and OTAPA • IS-730: DCCH based on IS-41-C (for IS-136-A) • IS-735: Cellular Feature Description for CDMA • IS-737: Circuit Modes Services-Data - based on IS-41-C • IS-751: IMSI (International Mobile Subscriber Identity) • IS-756-A: WNP Phase I and Phase II • IS-764: CNAP/CNAR

  16. IS-771: WIN Phase I • IS-778: Authentication Enhancements • IS-807: Internationalization of ANSI-41 • IS-812: ANSI-41 Message Segmentation • J-STD-034: Wireless Enhanced Emergency Services • Miscellaneous Enhancements

  17. Stand-Alone Documents ANSI-41-D Integration ANSI-41-E Conversion FrameMaker PN-3590 (ANSI-41-E) • ANSI-41-E = ANSI-41-D + Stand-Alone Doc.

  18. ANSI-41-E • Documents in FrameMaker • ANSI-41 and ANSI-124 will be converted to the FrameMaker • Why FrameMaker? • Easier to publish larger Documents, Graphics and Tables • Import and Export Filters for Text, Tables and Graphics (e.g., import from MS Word ‘97 Document) • Most of all, easier editing for editor • Available for FrameMaker 6.0

  19. ANSI-41-E Integration Status • ANSI-41 Chapter 6 is completed • Working on ANSI-41 Chapter 5 Tables • Completed with Table Integration Template • Work plan • Review Ballot Comments on 2000/02-03 • Approve for Publication on April 2001

  20. Post ANSI-41-E Projects • PN-4733: Internationalization of ANSI-41 • More like Errata than Addendum to IS-807 • PN-3890: Emergency Services (E-911) • E9-1-1 Phase II • Addresses carrier position reporting to emergency services system, as mandated by the FCC under docket 94-102 • PN-4287: Pre-Paid Charging • capability to pay for services prior to usage

  21. PN-4289: WIN Phase II • Presents recommended plan for the implementation of WIN capability that support following features: • Freephone (FPH): User to originate calls to a Freephone directory number and called party to pay all charges • Advice of Charging (AOC): Subscriber to receive charging information for the services • Premium Rate Charging (PRC): Subscriber to be charged a premium rate for services • Rejection of Undesired Annoying Calls (RUAC): Allows a subscriber to block undesired annoying calls • Enhanced Preferred Language (EPL): uses WIN capabilities to provides announcement in subscriber’s preferred language

  22. PN-4410 (IS-786): Automatic Code Gapping • Developed based on wire line ACG • Purpose is to control the system overload • Under ballot review process • PN-4411 (IS-841): WNP - Phase III • SMS delivery to MDN based MC • Ballot expired on April 24, 2000 • Reviewed Ballot Responses and approved for publication: July 2000

  23. PN-4550 (IS-837): Answer Hold • Called Subscriber’s Service Feature • provides a called subscriber the capability to answer the call, but selectively delay the conversation (e.g., Call Waiting) • provide announcement to calling party (e.g., “Please Hold”) • resolve the call in the AH state prior to originating a new outgoing call or call leg • one incoming call per AH called subscriber • Completed ballot resolution • Comments to the Ballot has been all resolved, however • Due to “Do Not Approve ” vote, being re-balloted • TSG-N finished re-ballot resolution

  24. PN-4551 (IS-838): USCF • Called Subscriber’s Service Feature • provides a called subscriber to selectively redirect incoming calls (e.g., voice mail system, CFB, CFD, CF No Answer) • Applicable to voice telecommunication services • TSG-N finished re-ballot resolution • PN-4582: User Identity Module (UIM) • Addresses only R-UIM • Ballot resolution is under way.

  25. New Post ANSI-41-E Projects

  26. PN-4720: Packet Data Phase I • Project was initiated by Sprint PCS • Enhancement required for supporting roaming subscriber with Packet Data Service: • Intersystem Handoff • Assured QoS • Higher Packet Data Rate:  56 Kbps • Simultaneous Voice and Data (will carry over to Phase II) • Currently at Stage 1 development

  27. PN-4755: Packet Data Phase II • Identified Work plan for Phase II • Support ANSI41-D for Simultaneous Voice and Data in support of TR45.4 and TR45.5 • No actual Phase II work items identified • No Specific development is in progress

  28. PN-4746: LS Authentication/Privacy/Security • Provide ANSI/TIA/EIA-41 support of Authentication, Privacy and Security of Location Services • Authentication is required to allow the network to authenticate requests for Location Information (e.g., LBC application requested location information on a mobile station • Privacy is required to protect the security of the mobile station user by allowing the user to block or restrict Location Information requests. • Stage 1 Baseline: July 2000

  29. PN-4747: LS Enhancements • ANSI-41 support for location services architecture, PDE and MPC interfaces, as well as areas of uncertainty and accuracy • Development: • TSG-S (Stage 1) • TR45.2 (Stage2 and Stage 3) • Stage 1 Baseline: July 2000PDE: Position Determining EntityMPC: Mobile Position Center

  30. PN-4762 ANSI-41/IP Transport • Initiated by Nortel Networks • Specifies Internet Protocol (IP)-based Data Transfer services such that IP-based protocol stacks may be used to transport TIA/EIA-41 MAP messages • Work plan • Ready for Ballot: November 2000 • Approve for Publication: February 2001

  31. Other Standards

  32. Other Standards in TR45.2 • PN-4465 (J-STD-025-A) • Electronic Surveillance • Under Ballot Resolution • PN-4528 (ANSI-124-C) • Data Message Handler (e.g. Billing) • Ballot Resolution completed • PN-4652 (ANSI-664-A) • Cellular Features Description • Completed Ballot Resolution • Approved for publication

  33. ES Ad HocEmergency Services (E9-1-1)

  34. Background • Phase II, scheduled for October 1, 2001 • PSAPs are to receive more precise location identification, within 125 m of the caller’s location • location information could only effectively provided by technologies based in networks (using triangulation of the handset’s signal) • However • the current rules only permit network-based solutions to meet Phase II requirements • not economically or logistically feasible to upgrade or replace all current handsets to meet the date • Revised the rule to permit handset-based solutions

  35. Revision to current wireless E911 Rules • Handset based location technology • Without respect to any PSAP request for Phase II • Selling and activating ALI (Automatic Location Identification) capable handsets NLT March 1, 2001 • 50% of all new handsets activated are ALI capable NLT October 1, 2001 • 95% of all new digital handsets activated are • ALI capable NLT October, 2002

  36. Once a PSAP request is received then • Within 6 months or by October 1, 2001 • 100% ALI-capable • Implement any network upgrade or other steps necessary to locate handsets • Begin delivering to the PSAP location information that satisfies Phase II requirements • Within 2 years or by December 31, 2004, achieve 100% penetration of ALI-capable handsets

  37. Network-based location technologies • Initial rule was • implementation be fully accomplished within 6 months of PSAP request • Revised rules to deploy Phase II • to 50% of callers within 6 Month and • to 100% of callers within 18 months of PSAP request

  38. Revised Location Accuracy and Reliability • For network-base solution: • 100 m for 67 % and • 300 m for 98% of calls • For handset-based Solution: • 50 m for 67% and • 150 m for 95 % of calls

  39. Current E9-1-1 Standards Status • PN-3890: E9-1-1 Phase II • TR45.2 approved for ballot pending editorial review • Will move forward for 30-day Ballot • Publication: July 2000 • PN-4288 • Temporarily on HOLD, due to • Ripple effects from PN-3890 • Waiting for the completion of PN-3890 • Will resume development from August 2000

  40. LAES Ad HocLawfully Authorized Electronic Surveillance

  41. Background • TIA published J-STD-025 in 12/1997 • Defines interface between TSP and LEA to assist the LEA in conducting LAES • In March 1998, CDT and FBI filed separate challenges to the standard • FBI: J-STD-025 failed to incorporate “nine punch-list” items • CDT: objected to the J-STD-025 provisions on location and packet data

  42. On August 26, 1999 • FCC adopted • “Six” of the nine punch-list items • Rejected CDT’s criticisms of the location and packet data • Reaffirmed Phase II schedule • revise J-STD-025 to incorporate the six punch list items • revision to be completed by March 30, 2000 • “core” J-STD-025 provisions must be implemented by June 30, 2000 • Industry must install “Six Punch-List” items and Packet-data capability by September30, 2001

  43. Required Six Punch Lists • post-cut-through digits (also known as dialed digit extraction) • conversations of parities on hold • party join/hold/drop • subscriber-initiated signaling • use of flash-hook and other feature keys • timing information • network-generated signaling • notification that a line is ringing or busy

  44. PN-4464 (to be J-STD-025-A) • Provides requirements for Phase II • Currently under Ballot Resolution • Scheduled for publication on Sep. 2000

  45. CALEA JEM • JEM (Joint Expert’s Meeting) • current J-STD-025 raised significant technical and privacy concerns: • Packet Technologies in the CALEA insufficient • only authorized call-identifying information provided • FCC 3rd R&O requires delivering Packet-Mode by September 30, 2001 • Sponsored by TIA & T1(CALEA: Communications Assistance for Law Enforcement Act)

  46. Authentication Focus Group

  47. Authentication Focus Group • Initial Four Proposals for ESA were from • Certicom: EPAC • CipherIT: ESA • Lucent Technology: LAES • 3GPP AKA • During the initial deliberation in TR45.2 • Certicom withdraws its proposal • AFG decided not to consider CipherIT proposal • 3GPP AKA and Lucent Technologies

  48. AHAG voted for 3GPP AKA and recommended 3GPP AKA to TR-45 • TR-45 members voted for 3GPP AKA • TR-45.2 re-evaluated 3GPP AKA against ESA Stage 1 Requirements (PN-4392) • Some members proposed its evaluation against 3GPP AKA but TR45 endorsed.ESA: Enhanced Subscriber Authentication

  49. The Recent Deliberation in TR45.2.2.AFG • 3GPP AKA needs to determine the methods to provide “Home Control” • Need to determine the specific method for using CK to perform encryption • Assess AKA’s impact on performance and resources (e.g., traffic channel utilization) • TR-45 AHAG recommended SHA-1 as Local Authentication Algorithm and TR-45 endorsed it with no objection

  50. Q&A 謝 謝 Thank you very much. 감사합니다. 再 見

More Related