The main responsibilities of TC SCP REQ are:
define requirements for the TC SCP smart card platform and services related to
Create TC SCP requirement specifications and reports.
Maintain TC SCP requirement specifications and reports.
The main tasks of TC SCP REQ are:
requirements based on input from:
TC SCP TEC,
bodies including 3GPP, 3GPP2, GlobalPlatform, GSMA, OMA, SIM Alliance,
maintain requirements specifications and reports.
overall coherence and timely and expeditious evolution of the requirements
specifications for the TC SCP smart card platform.
ensure consistency of TC SCP specifications with the specifications of other
“customer” bodies such as 3GPP, 3GPP2, GlobalPlatform and OMA.
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
- When there is a need for a
joint session with another group.
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
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.