1 / 6

CAT over AT: status and next steps – rev.1

ETSI TC SCP #47 SCP(10)0320r1 Sophia Antipolis, France, 12-14 January 2011. CAT over AT: status and next steps – rev.1. Incard A. Veneroso. A brief history. CAT over AT requirements were agreed in July 2009

alisa
Download Presentation

CAT over AT: status and next steps – rev.1

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. ETSI TC SCP #47 SCP(10)0320r1 Sophia Antipolis, France, 12-14 January 2011 CAT over AT: status and next steps – rev.1 Incard A. Veneroso

  2. A brief history • CAT over AT requirements were agreed in July 2009 • First technical architecture presented by Incard covering all reqs in Sept 2009 • Requirements improved (multiple legacy CEs and security) in Q1 2010 • Conf call in April 2010 – job split with 3GPP • CRs approved in CT1 in September 2010 Targetting Release 9 at the beginning!!!

  3. Requirements • Requirements have been mainly approved in July 2009 and partially evolved in March 2010 • No CRs in Req after March 2010 • Requirements include possibility of: • Legacy / Enhanced architecture • Multiple connected entities • Explicit routing for Enhanced • Default routing for Legacy • Security requirements (added in March 2010)

  4. Current status • 4 Proposals were discussed at TEC #36: • SCPTEC(10)529r1 by T-Mobile New proposal presented in SCP TEC #36 introducing encapsulation of tk commands/response. • SCPTEC 530r1 by France Telecom Based on Incard proposal from Sept 2009 with Explicit Routing TLV • SCPTEC 543 by France Telecom Based on Incard proposal from Sept 2009 but introducing Device Identity based routing • SCPTEC 413r2 by G&D (withdrawn) No explicit routing by Toolkit application

  5. Current status 2 Proposals have been re-posted at SCP #47: SCP(11)0023 by G&D Merge of the T-Mobile and G&D proposals Added security requirements SCP(11)0060 by France Telecom, Incard, Oberthur, Telecom Italia, Morpho, Gemalto Based on Incard proposal from Sept 2009 with Explicit Routing TLV Companion CR to API specification (ETSI TS 102 241) presented in TEC #36 5

  6. Actually two main options are avail • “Embedded commands/event” solution (G&D) • Compatible with current CT output • Low impact on Card / modem architecture • Relies on an external entity (the multiplexer) for explicit routing • No “companion” solution for API • Connected entities can generate only one event/execute one command, in addition to the legacy mechanism • Security requirements are supported  More focused on legacy • “Routing TLV” solution (FT et al.) • Compatible with current CT output, but CT docs should be extended to support multiple CEs. • Impact on Card / modem architecture • Both explicit routing and legacy are supported • “Companion” solution for API  More focused on enhanced

More Related