Download
tc scp tec status report to tc scp plenary 56 n.
Skip this Video
Loading SlideShow in 5 Seconds..
TC SCP TEC Status Report to TC SCP Plenary #56 PowerPoint Presentation
Download Presentation
TC SCP TEC Status Report to TC SCP Plenary #56

TC SCP TEC Status Report to TC SCP Plenary #56

159 Views Download Presentation
Download Presentation

TC SCP TEC Status Report to TC SCP Plenary #56

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. TC SCP TEC Status Report to TC SCP Plenary #56 Paul JOLIVET, Chairman, LG Electronics Sebastian HANS, Vice chairman, Oracle SCP(12)000165r1

  2. Meetings Since Last TC SCP Plenary • SCP TEC #44 • 10-13 September 2012 • Sophia Antipolis, France, hosted by ETSI at Novotel • SCP TEC #44 bis • 21 September 2012 • Conference call / GoToMeeting

  3. Discussions, hot topics (1/3) • General issues, meeting schedule • Some questions about the target for R11 were raised • A joint session with SCP TEST was organized to discuss contactless specification clarification needs • A bis meeting was organized (conference call) to deal with 2 remaining documents, including a document provided during the meeting • An additional meeting was scheduled during TEC #44 • 15-16 Oct, 4 to 6 pm • Conference call • Focussed on specific documents

  4. Discussions, hot topics (2/3) • Contactless related topics • Joint session with SCP TEST to discuss clarifications • A new version of the proposal related to P2P was presented and discussed, the WID roadmap remains valid at this stage • P2P specification is enhanced, comments gathered during the meeting will be integrated to the document (in 111) • API related discussions • High activity arrays, no agreement could be reach • Secure Channel API: • The rapporteur presented a document to the group for discussion • Discussion to assess if this has to be a separate spec or integrated in API • Agreement to have an ad hoc meeting on this topic • A set of CRs on TS 102 705 (contactless API) was accepted

  5. Discussions, hot topics (3/3) • CAT Secure Channel • Further discussions on the two approaches • Agreement to make Work Item Descriptions (instead of TEI) • Two WIDs prepared • One only could be approved due to lack of supporters on one of them • Other topics • 3GPP2 related CR proposal on MEID coding was accepted as their specification is now published • Smart Card Web Server: a conference call to be organized prior to the next meeting to deal with proposal in 046 • No input related to eUICC even though it was mentioned in Plenary that discussions would be raised in TEC

  6. Request for advice • API : High activity arrays • No agreement could be reached in the meeting on the way forward • Some participants feel that the requirement cannot be fulfiled • SCP Plenary is requested to give guidance regarding the way forward

  7. Outcome Documents – CRs • List of TEC accepted CRs available in SCP(12)000166 • Change Requests • 5 CRs to TS 102 223 • 8 CRs to TS 102 226 • 10 CRs to TS 102 613 • 9 CRs to TS 102 705 • Statistics: • 32 CRs • Releases: • 2 on Rel-7 • 2 on Rel-8 • 8 on Rel-9 • 9 on Rel-10 • 11 on Rel-11 • Categories • 17 Cat A • 3 Cat C • 12 Cat F

  8. Outcome Documents – WIDs • Security for encapsulated CAT • SCP(12)000163 • This work item will define a mechanism that allows securing of encapsulated CAT commands and envelopes. The mechanism can be used within the terminal (TE) and on top of the AT commands defined for CAT over the modem interface. Existing security mechanisms from TS 102 484 will be re-used. • Target date for delivery of the solution is SCP #58

  9. Outcome Documents – TSs No input

  10. Outcome Documents – LSs • LS directed to SCP • None • LS copied to SCP • SCP(12)000164 • LS to GlobalPlatform on GET DATA with forwarded information

  11. Next Steps / Milestones • Rel-11 (dates to be assessed in some cases): • Encapsulated CAT • Complete, except for security • Ongoing work on CAT over AT Security part • CAT Secure Channel • Contactless P2P • Secure Channel API (especially while M2M considered to adopt this concept from SCP) • M2M API • Other topics • RFID support • eUICC • M2M

  12. Meeting Schedule TC SCP TEC • SCP TEC ad hocs • #xxx • 15 October 2012 on SCPTEC(12)000071r2 • 16 October 2012 on P2P • SCP TEC #45 • 26-30 November 2012 • Sophia-Antipolis, France • SCP TEC #46 • 21-25 January 2013 • Sophia-Antipolis, France • SCP TEC #47 • 18-21 March 2013 • Sophia-Antipolis, France