3GPP TSG-T2 MExE
Whistler, Canada
March 27th – March 29th 	T2-010038

Liaison Statement

From:	3GPP TSG T WG2 SWG1 (MExE)

To:	3GPP TSG T WG1

Cc:	

Subject:	Conformance test requirements for application layer test

MExE Contact:	Lars Brenk
	TTPCom Danmark ApS
	+45 9631 4658
	lsb_ttpcom@hotmail.com

MExE Chairman:	Mark Cataldo
mcatald1@email.mot.com

Attachments:	

___________________________________________________________________________

The MExE group would like to thank T1 for its LS to TSG T2 regarding conformance test requirements for application layer test (Redondo Beach, CA, USA, 16th and 17th Nov, 2000).

The MExE group  has completed  a conformance table as an annex to the MExE specification, which defines the minimum set of features for a MExE device. The conformance table is attached as Annex A. However, it should be noted that the conformance table is an evolving document, which will be frequently updated to reflect the changes in the MExE specification.
 
T1 can then decide if the tests can be implemented from the conformance annex together with the main body of the MExE specification, or if T1 would like some assistance from the MExE group.

3GPP TSG-T2 SWG1 (MExE) looks forward to a continuing fruitful co-operation with TSG T WG1.

Annex E (informative):
MExE conformance requirements
The table of Conformance Requirements define the minimum set of features that a conformant MExE device must implement. 

Legend:-
M - 	Mandatory feature/requirement
O  - 	Optional feature
N/A -	Feature is not applicable: the MExE specification does not prevent from implementing a feature, however support of the  feature is not required for a MExE device to be regarded as being compliant with a specific MExE Classmark device,  and therefore optionality of the feature is not indicated in the specification.
M/O – Support as such is required. Mandatory and Optional features are gathered into a table

ID	Requirement	Reference	CM1	CM2	CM3	
4-1	Support of at least one MExE classmark on a MExE device	4	M	M	M	
4-2	Support of multiple combinations of MExE classmarks	4.4	O	O	O	
4-3	Support of WAP 	4.2.5	M	O	O	
4-4	If Classmark 1 services are supported by non-Classmark 1 devices, Classmark 1 services shall execute in the same manner as they execute in a MExE Classmark 1 device 	4.4.1	N/A	M	M	
4-5	Support of PersonalJava 	4.2, 6.1	O	M	O	
4-6	If Classmark 2 services are supported by non-Classmark 2 devices, Classmark 2 services shall execute in the same manner as they execute in a MExE Classmark 2 device.  	4.4.2	M	N/A	M	
4-7	Support of CLDC and MIDP	4.3, 6.2	O	O	M	
4-8	If Classmark 3 services are supported by non-Classmark 3 devices, Classmark 3 services shall execute in the same manner as they execute in a MExE Classmark 3 device.  	4.4.3	M	M	N/A	
4-9	Support of capability negotiation process	4.6	M	M	M	
4-10	Support for interaction between the MExE device and the MSE by the use of HTTP/1.1or HTTP/1.1 derived protocol (e.g. WSP)	4.6	M	M	M	
4-11	Support of the properties in the UAProf schema for capability negotiation	4.6.1	M/O	M/O	M/O	
4-12	Support of content negotiation	4.6	O	O	O	
4-13	Support of user profiles	4.7	O	O	O	
4-14	Support of more than one user profile (if user profiles supported)	4.7.1	O	O	O	
4-15	Ability to retain the user profile in the network (if user profiles supported)	4.7.1	O	O	O	
4-16	User permission for retaining the user profile in the network (if user profiles supported)	4.7.1	M	M	M	
4-17	Support of direct and indirect referencing mechanisms in retrieval of MExE preferences (if user profiles supported)	4.7.3	O	O	O	
4-18	Support of the properties in the UAProf schema for user preference information (if user profiles supported)	4.7.3	M	M	M	
4-19	Support of user interface personalisation 	4.8	O	O	O	
4-20	Support of direct and indirect referencing mechanisms in retrieval of user interface personalisation preferences 	4.8.1	O	O	O	
4-21	Ability to support VHE 	4.7.4	O	O	O	
4-22	Storage of the VHE characteristics as a part of the user profile (if VHE and user profile is supported)	4.7.4	M	M	M	
4-23	Capability to discover new services 	4.9.1	M	M	M	
4-24	Support for a browser for service discovery	4.9.1	O	O	O	
4-25	Ability to control service installation and configuration 	4.9.3	N/A	M	M	
4-26	Ability to determine which services are transferred to, resident, configured or executing on the MExE device (provide the name and, if available, version number)	4.9.4	M	M	M	
4-27	Service termination capability 	4.9.5	M	M	M	
4-28	Capability to delete a service 	4.9.6	M	M	M	
4-29	User’s ability to terminate or suspend any active connection associated with any MExE executable	4.10	M	M	M	
4-30	User’s ability to obtain information on all connections associated with any MExE executable on the MExE device	4.10	M	M	M	
4-31	Support of journalling of network events by MExE executables	4.11	M	M	M	
4-32	Management of the journal by the MExE device, with no access to it by MExE executables 	4.11	M	M	M	
4-33	Indicate whenever network activity is in progress	4.12	O	O	O	
4-34	Support of QoS management by MExE	4.13, 9	O	O	O	
4-35	Support of core software download functionality	4.14	O	O	O	
4-36	Core software download (if supported) only under control of the MExE device manufacturer	4.14	M	M	M	
5-1	Call control using WTA scripts	5.3	M	O	O	
6-1	Support of the Wireless Profile of the JavaPhone API specification (Optionality of Wireless Profile of the JavaPhone APIs as presented in Table 4 "Optionality of the Wireless Profile of the JavaPhone APIs")	6.1.2.1, 6.1.2.3	O	M/O	O	
6-2	Support of the JAR file manifest entries as per JavaPhone specification	6.1.2.3.1	O	M	O	
6-3	The use of icons to launch applications	6.1.2.3.1	O	O	O	
6-4	If icons are used as elements to launch the application, then the icon file within the JAR file named by the Main-Icon attribute shall be displayed	6.1.2.3.1	O	M	O	
6-5	Implementation of “BatteryCritical”, “BatteryNormal” event generation	6.1.2.3.2	O	M	O	
6-6	Support for the following formats in Datagram recipient addressing: raw text-only GSM SMS message, UDP datagram via IP, and WAP datagram via GSM SMS message(s)	6.1.2.3.3	O	M	O	
6-7	Support any other Java APIs which comply with the MExE security requirements in Table 6 "Security domains and actions"	6.1.2.4	O	O	O	
6-8	Support for network protocols as per Table 5 "Support for network protocols"	6.1.2.5.1	O	M/O	O	
6-9	Support of MIDlet discovery and management via a browser using MIME type text/vnd.sun.j2me.app-descriptor	6.2.3	O	O	O	
6-10	Indication of MIDlets and MIDlet suites to the user (with a tag or icon and tag) 	6.2.3	O	O	O	
7-1	Support of charging regimes of MExE services (charging mechanisms are outside the scope of MExE specification). 	7.1	O	O	O	
8-1	Support of the untrusted area	8.1	M	M	M	
8-2	Support of all three security domains together (i.e. operator, manufacturer and third party), or no security domains at all	8.1	M	M	M	
8-3	Security restrictions shall apply to MExE executables when API functionality is directly or indirectly called by MExE executables 	8.2	M	M	M	
8-4	Support for permissions of operator, manufacturer and third party security domains in the order of restriction (as defined in Table 6 "Security domains and actions" of MExE specification).	8.2.1	M	M	M	
8-5	Access by MExE untrusted executables limited to the functionality specified in the Table 7 "Executable permissions for untrusted MExE executables" of MExE specification	8.2.2	M	M	M	
8-6	Separation of the user interface input and output streams between different MExE executables (except for the MIDlets in the same MIDlet suite)	8.2.3	M	M	M	
8-7	Support of single action permission with a prompt for the user	8.3	M	M	M	
8-8	Support of session permission and blanket permission with a prompt for the user	8.3	O	O	O	
8-9	Indication to the user whenever user permission is sought by an untrusted MExE executable	8.3	M	M	M	
8-10	Ability of the user to request to be informed of the “subject” field of the certificate of the signer (if secure domains supported)	8.3	M	M	M	
8-11	Support for public key based solution of content authentication (if secure domains supported)	8.4	M	M	M	
8-12	Support of certificate chains (if secure domains supported)	8.4	M	M	M	
8-13	Support at least one level of certificate under operator, manufacturer or Third Party root public keys (if secure domains supported)	8.4	M	M	M	
8-14	Secure installation of root public keys in the MExE device (if secure domains supported)	8.4.1	M	M	M	
8-15	Prohibition to share public keys between domains (if secure domains supported)	8.4.1	M	M	M	
8-16	Support the use and management of an operator root public key on the (U)SIM (if secure domains supported)	8.5.1	M	M	M	
8-17	Prohibition of the user to add or delete any type of operator public keys (if secure domains supported)	8.5.1	M	M	M	
8-18	Support of operator and manufacturer disaster recovery root public keys (if secure domains supported)	8.5.	O	O	O	
8-19	Support of the use and management of the operator root public key (if secure domains supported)	8.5.1.	M	M	M	
8-20	Support of the use and management of the manufacturer root public key (if secure domains supported)	8.5.2	M	M	M	
8-21	Support of the use and management of the third party root public keys (if secure domains supported)	8.5.3	M	M	M	
8-22	Support of the use and management of the administrator root public key (if secure domains supported)	8.5.4	M	M	M	
8-23	Support of the administrator designation mechanism (if secure domains supported)	8.5.4	M	M	M	
8-24	Support of the certificate configuration management (if secure domains supported)	8.6	M	M	M	
8-25	Use of the CCM by MExE device to determine the third party certificates that are trusted for the use on the MExE device (if secure domains supported)	8.7	M	M	M	
8-26	Additional support of other means to enable/disable root certificates (if secure domains supported)	8.7	O	O	O	
8-27	Support of authorised CCM download mechanisms (if secure domains supported)	8.7.	M	M	M	
8-28	When the administrator is changed, then the CCM shall also be changed.  (if secure domains supported)	8.7.	M	M	M	
8-29	Support of provisioned mechanism for designating administrative responsibilities and adding third parties in a MExE device (if secure domains supported)	8.8	M	M	M	
8-30	Support of the cases: the user is the owner, the user is at remote location, the owner of the MExE-(U)SIM wants to be a temporary administrator (if secure domains supported)	8.8	M	M	M	
8-31	Support for determining the administrator of the MExE device (if secure domains supported)	8.8.1	M	M	M	
8-32	Either sandbox or fine grain Java security shall be supported	8.9.1	N/A	M	N/A	
8-33	Support for trusted applets (if secure domains supported)	8.9.1	N/A	O	O	
8-34	Verification of the certification of the application or applet (if secure domains supported)	8.9.1.2	M	M	M	
8-35	Java loading native libraries that are intrinsically part of the MExE device implementation, and MExE native libraries 	8.9.1.3	O	O	O	
8-36	No loading of other native libraries	8.9.1.3	N/A	M	N/A	
8-37	Support of the JAR file format devices for securely packaging objects that are to be downloaded and installed on the MExE device	8.10	N/A	M	M	
8-38	Support for other proprietary means of downloading and installing objects	8.10	O	O	O	
8-39	Support of MExE native library signed package installation	8.10.1	N/A	O	O	
8-40	Support for the case when a certificate containing an Administrator root public key is thus contained in a signed package, the signed package (JAR) shall contain two files: the Administrator root public key and the CCM (if secure domains supported).	8.10.2	N/A	M	M	
8-41	Support of installation of other signed data (e.g. proprietary binaries or Java classes such as native DSP code, provisioned functionality upgrades and patches) (if secure domains supported).	8.10.3	O	O	O	
8-42	Support for administrator root certificate mechanism (if secure domains supported).	8.10.4	M	M	M	
8-43	Support of alternative methods to download an administrator root certificate (if secure domains supported).	8.10.4	O	O	O	
8-44	Support of optimised signature verification of applications (if secure domains supported).	8.11	O	O	O	
9-1	Support of QoS API by MExE device	9	O	O	O	
9-2	Support of a basic QoS operations	9.1	O	O	O	
9-3	Support of MExE QoS API by MExE QoS Manager	9.2	O	O	O	
9-4	Provision of the MExE QoS Manager functions	9.2	O	O	O	
9-5	Ability to manage QoS through the MExE device's MMI	9.2	O	O	O	
9-6	QoS control by MExE QoS Manager, if it is not provided in the network control 	9.3	O	O	O	
9-7	Provision of a standard set of parameters by a QoS API to MExE executable	9.4	O	O	O	
9-8	Ability of MExE QoS Manager to deal independently with each of the several simultaneous QoS streams	9.6	O	O	O