TB SiteMapbreadcrumb separatorSCPbreadcrumb separatorSCP REQ ToR

Terms of Reference (ToR) for ETSI Project Smart Card  Platform (TC SCP) Requirements Working Group (TC SCP REQ) 

Approved at SCP#18

 1. Responsibilities

The main responsibilities of TC SCP REQ are:

Identify and define requirements for the TC SCP smart card platform and services related to it. Create TC SCP requirement specifications and reports. Maintain TC SCP requirement specifications and reports.

2. Tasks

The main tasks of TC SCP REQ are:

Evaluate requirements based on input from: Participants, TC SCP TEC, External bodies including 3GPP, 3GPP2, GlobalPlatform, GSMA, OMA, SIM Alliance, etc. Develop and maintain requirements specifications and reports. Ensure overall coherence and timely and expeditious evolution of the requirements specifications for the TC SCP smart card platform. Aim to ensure consistency of TC SCP specifications with the specifications of other “customer” bodies such as 3GPP, 3GPP2, GlobalPlatform and OMA.

3. Organisation

TC SCP REQ meets at least once prior to each TC SCP Plenary meeting. The specification work should be done as much as possible in the regular WG meetings. Electronic work to advance topics and documents for the discussion in a WG meeting is encouraged. However some ad hoc sessions might be organised in some cases such as:

- When there is an exceptionally high amount of work needed to accomplish an agreed target.

- When specific expertise is required.

- When there is a need for a joint session with another group.

4. Liaisons

To facilitate its work, TC SCP REQ shall identify relevant bodies and ask the TC SCP Plenary for the agreement to set up direct liaison to these bodies.

Formal liaison should be established with bodies referencing TC SCP specifications in order to facilitate the work on specifications dependence/consistency.

In some cases, informal liaison is handled by delegates attending international standardisation meetings and forums, for example ISO/IEC SC17 and the Java Card Forum.