Document List for 3GPPCT6#35
List generated on : 2005-04-26 at 05:26:12 (GMT +01:00)

Abstract: Agenda for CT6-35 in Cancun DOCUMENT: Agenda for CT6-35 in Cancun
Doc.Name C6-050205 Allocations: Content Type:
File Name: C6-050205.zip
Source: WG Chairman
Abstract: Agenda for CT6-35 in Cancun
 
Abstract: DOCUMENT: CR 31.121 R99: Correction to range of available branches in
TC 7.4.2
Doc.Name C6-050206 Allocations: Content Type:
File Name: C6-050206.zip
Source: 7 layers AG
 
Abstract: DOCUMENT: CR 31.130 Allign paragraph numbering between 31.130 and TS 1
02 241
Doc.Name C6-050207 Allocations: Content Type:
File Name: C6-050207.zip
Source: Rapporteur
 
Abstract: DOCUMENT: CR 31.130 Delete version and author info from the Java sourc
e code
Doc.Name C6-050208 Allocations: Content Type:
File Name: C6-050208.zip
Source: Rapporteur
 
Abstract: DOCUMENT: CR 31.121 R99: Correction of the content for Class 1 short m
essages in TC 8.2.1
Doc.Name C6-050209 Allocations: Content Type:
File Name: C6-050209.zip
Source: 7 layers AG
 
Abstract: Original Terms of Reference for TSG-T WG3 as drafted in 1999 DOCUMENT: Terms of Reference for TSG-T WG3
Doc.Name C6-050210 Allocations: Content Type:
File Name: C6-050210.zip
Source: ETSI Secretariat
Abstract: Original Terms of Reference for TSG-T WG3 as drafted in 1999
 
Abstract: Letter from 3GPP2 raising the question on how to ensure global ICCID uniqueness DOCUMENT: ICCID uniqueness
Doc.Name C6-050211 Allocations: Content Type:
File Name: C6-050211.zip
Source: 3GPP2
Abstract: Letter from 3GPP2 raising the question on how to ensure global ICCID uniqueness
 
Abstract: DOCUMENT: Clarifications on 3GPP CT6 specifications
Doc.Name C6-050212 Allocations: Content Type:
File Name: C6-050212.zip
Source: 3GPP2
 
Abstract: Meeting report of T3-34 in Barcelona DOCUMENT: T3-34 report
Doc.Name C6-050213 Allocations: Content Type:
File Name: C6-050213.zip
Source: ETSI Secretariat
Abstract: Meeting report of T3-34 in Barcelona
 
Abstract: Addition of ISIM Remote File Management procedure DOCUMENT: CR31.116-R7: Addition of ISIM Remote File Management procedu
re
Doc.Name C6-050214 Allocations: Content Type:
File Name: C6-050214.zip
Source: Gemplus
Abstract: Addition of ISIM Remote File Management procedure
 
Abstract: Clarifies the order of the digits in EF(hiddenkey)
Consequences if not approved:
interoperability problems of the phonebook; some entries entered with one ME would not be accessible with another ME
DOCUMENT: CR31.102-R99: Essential correction of the 'hidden key' codin
g
Doc.Name C6-050215 Allocations: Content Type:
File Name: C6-050215.zip
Source: Gemplus (Rapporteur)
Abstract: Clarifies the order of the digits in EF(hiddenkey)
Consequences if not approved:
interoperability problems of the phonebook; some entries entered with one ME wou
ld not be accessible with another ME
 
Abstract: Enriched SMS PP Data Download Tests with missing parts on Error Handling 9E XX DOCUMENT: CR 11.10-4 R99: add SMS PP Data Download RP-ERROR Test Case
Doc.Name C6-050216 Allocations: Content Type:
File Name: C6-050216.zip, zip,,
Source: Gemplus (Rapporteur)
Abstract: Enriched SMS PP Data Download Tests with missing parts on Error Handling 9E XX
 
Abstract: Enriched SMS PP Data Download Tests with missing parts on RP-ERROR handling DOCUMENT: CR 31.124 Rel-6: add SMS PP Data Download RP-ERROR Test Case
Doc.Name C6-050217 Allocations: Content Type:
File Name: C6-050217.zip, zip,
Source: Gemplus (Rapporteur)
Abstract: Enriched SMS PP Data Download Tests with missing parts on RP-ERROR handling
 
Abstract: Added test on Command numbering
And alignment with TS 31.124 Rel-6 DOCUMENT: CR to 11.10-4 : Handling of command number
Doc.Name C6-050218 Allocations: Content Type:
File Name: C6-050218.zip
Source: Gemplus (Rapporteur)
Abstract: Added test on Command numbering
And alignment with TS 31.124 Rel-6
 
Abstract: Inclusion of new table of information from the apparatus supplier

Alignment with similar existing table in TS 31.124, section 5.3 DOCUMENT: CR to 11.10-4 : Table of ME’s default configuration
Doc.Name C6-050219 Allocations: Content Type:
File Name: C6-050219.zip
Source: Gemplus (Rapporteur)
Abstract: Inclusion of new table of information from the apparatus supplier

Alignment with similar existing table in TS 31.124, section 5.3
 
Abstract: This draft LS must be considered in conjunction with the input paper C6-050221 DOCUMENT: Draft LS to GERAN on 51.10-2 misalignment with Toolkit
Doc.Name C6-050220 Allocations: Content Type:
File Name: C6-050220.zip
Source: Gemplus (Rapporteur)
Abstract: This draft LS must be considered in conjunction with the input paper C6-050221
 
Abstract: The table of PICS/Pixits in TS 51.10-2 Rel-6 related to SIM Toolkit is different from the one in the TS 11.10-4 R99, with even some errors in it

CT6 is therefore incited to ask GERAN3 for correction or alignment with the TS 11.10-4 R99 table. See draft LS C6-050220
DOCUMENT: Incoherences between TS 51.101-2 Rel-6 and TS 11.10-4 R99
Doc.Name C6-050221 Allocations: Content Type:
File Name: C6-050221.zip
Source: Gemplus (rapporteur)
Abstract: The table of PICS/Pixits in TS 51.10-2 Rel-6 related to SIM Toolkit is different
from the one in the TS 11.10-4 R99, with even some errors in it

CT6 is therefore incited to ask GERAN3 for correction or alignment with the TS 1
1.10-4 R99 table. See draft LS C6-050220
 
Abstract: DOCUMENT: CR 31.124, Rel-6: Correction of applicability table
Doc.Name C6-050222 Allocations: Content Type:
File Name: C6-050222.zip
Source: ORGA Test Systems
 
Abstract: DOCUMENT: CR 31.124, Rel-6: Essential corrections
Doc.Name C6-050223 Allocations: Content Type:
File Name: C6-050223.zip
Source: ORGA Test Systems
 
Abstract: DOCUMENT: CR 11.10-4, R99: Essential corrections
Doc.Name C6-050224 Allocations: Content Type:
File Name: C6-050224.zip
Source: ORGA Test Systems
 
Abstract: 3GPP TS 31.102 doesn't mandate that during phonebook synchronisation only that EFUID record, which contains the value DOCUMENT: CR 31.121 R99: Essential correction of TC 8.1.2
Doc.Name C6-050225 Allocations: Content Type:
File Name: C6-050225.zip
Source: Rapporteur (OTS)
Abstract: 3GPP TS 31.102 doesn't mandate that during phonebook synchronisation only that E
FUID record, which contains the value "FF FF", is updated. Update of further EFU
ID records is therefore allowed. In conclusion this means that the acceptance cr
iteria of TC 8.1.2 is not compliant to TS 31.102.
 
Abstract: DOCUMENT: CR 31.121 Rel-4: Essential correction of TC 8.1.2
Doc.Name C6-050226 Allocations: Content Type:
File Name: C6-050226.zip
Source: Rapporteur (OTS)
 
Abstract: DOCUMENT: CR 31.121 Rel-5: Essential correction of TC 8.1.2
Doc.Name C6-050227 Allocations: Content Type:
File Name: C6-050227.zip
Source: Rapporteur (OTS)
 
Abstract: According to TS 31.102, cl. 4.2.44, the BDN feature relies on the Call Control functionality provided by USAT, as defined in TS 31.111. USAT is tested in TS 31.124 and as stated during T3#33 (see T3-050174, agenda item T3-040734) the BDN related functionality tested in TS 31.121 willl be fully covered by the new BDN tests in 31.124. 

To avoid duplication of tests the superfluous BDN tests in TS 31.121 need to be removed. 
DOCUMENT: CR 31.121 R99: Deletion of BDN tests
Doc.Name C6-050228 Allocations: Content Type:
File Name: C6-050228.zip
Source: Rapporteur (OTS)
Abstract: According to TS 31.102, cl. 4.2.44, the BDN feature relies on the Call Control f
unctionality provided by USAT, as defined in TS 31.111. USAT is tested in TS 31.
124 and as stated during T3#33 (see T3-050174, agenda item T3-040734) the BDN re
lated functionality tested in TS 31.121 willl be fully covered by the new BDN te
sts in 31.124.

To avoid duplication of tests the superfluous BDN tests in TS 31.121 need to be
removed.
 
Abstract: DOCUMENT: CR 31.121 Rel-4: Deletion of BDN tests
Doc.Name C6-050229 Allocations: Content Type:
File Name: C6-050229.zip
Source: Rapporteur (OTS)
 
Abstract: DOCUMENT: CR 31.121 Rel-5: Deletion of BDN tests
Doc.Name C6-050230 Allocations: Content Type:
File Name: C6-050230.zip
Source: Rapporteur (OTS)
 
Abstract: Phonebook tests in TS 31.121 are insufficient to ensure correct BCD number/ SSC content extension support DOCUMENT: CR 31.121 R99: Introduction of BCD number/ SSC content exten
sion tests
Doc.Name C6-050231 Allocations: Content Type:
File Name: C6-050231.zip
Source: NTT DoCoMo, Rapporteur (OTS), Toshiba
Abstract: Phonebook tests in TS 31.121 are insufficient to ensure correct BCD number/ SSC
content extension support
 
Abstract: Phonebook tests in TS 31.121 are insufficient to ensure correct BCD number/ SSC content extension support DOCUMENT: CR 31.121 Rel-4: Introduction of BCD number/ SSC content ext
ension tests
Doc.Name C6-050232 Allocations: Content Type:
File Name: C6-050232.zip
Source: NTT DoCoMo, Rapporteur (OTS), Toshiba
Abstract: Phonebook tests in TS 31.121 are insufficient to ensure correct BCD number/ SSC
content extension support
 
Abstract: Phonebook tests in TS 31.121 are insufficient to ensure correct BCD number/ SSC content extension support DOCUMENT: CR 31.121 Rel-5: Introduction of BCD number/ SSC content ext
ension tests
Doc.Name C6-050233 Allocations: Content Type:
File Name: C6-050233.zip
Source: NTT DoCoMo, Rapporteur (OTS), Toshiba
Abstract: Phonebook tests in TS 31.121 are insufficient to ensure correct BCD number/ SSC
content extension support
 
Abstract: 3GPP TS 31.121 does not contain tests for the USIM service DOCUMENT: CR 31.121 R99: Introduction of ACL tests
Doc.Name C6-050234 Allocations: Content Type:
File Name: C6-050234.zip
Source: NTT DoCoMo, Rapporteur (OTS), Toshiba
Abstract: 3GPP TS 31.121 does not contain tests for the USIM service "Access Point Name Co
ntrol List (ACL)" to verify that the terminal handles the ACL service correctly
 
Abstract: DOCUMENT: CR 31.121 Rel-4: Introduction of ACL tests
Doc.Name C6-050235 Allocations: Content Type:
File Name: C6-050235.zip
Source: NTT DoCoMo, Rapporteur (OTS), Toshiba
 
Abstract: DOCUMENT: CR 31.121 Rel-5: Introduction of ACL tests
Doc.Name C6-050236 Allocations: Content Type:
File Name: C6-050236.zip
Source: NTT DoCoMo, Rapporteur (OTS), Toshiba
 
Abstract: When previous CRs were implemented, the references were not updated DOCUMENT: 31.111 Rel 6 Correction to incomplete references
Doc.Name C6-050240 Allocations: Content Type:
File Name: C6-050240.zip
Source: Vodafone
Abstract: When previous CRs were implemented, the references were not updated
 
Abstract: DOCUMENT: CR 31.121, R99: Modifications due to revision of ISO/IEC 781
6-series
Doc.Name C6-050241 Allocations: Content Type:
File Name: C6-050241.doc, zip,
Source: Rapporteur (OTS)
 
Abstract: DOCUMENT: CR 31.121, Rel-4: Modifications due to revision of ISO/IEC 7
816-series
Doc.Name C6-050242 Allocations: Content Type:
File Name: C6-050242.zip
Source: Rapporteur (OTS)
 
Abstract: DOCUMENT: CR 31.121, Rel-5: Modifications due to revision of ISO/IEC 7
816-series
Doc.Name C6-050243 Allocations: Content Type:
File Name: C6-050243.zip
Source: Rapporteur (OTS)
 
Abstract: DOCUMENT: CR to 11.17: Update of references
Doc.Name C6-050244 Allocations: Content Type:
File Name: C6-050244.zip
Source: Rapporteur (OTS)
 
Abstract: DOCUMENT: CR to 51.017: Corrections and update of references
Doc.Name C6-050245 Allocations: Content Type:
File Name: C6-050245.zip
Source: Rapporteur (OTS)
 
Abstract: DOCUMENT: CR 11.10-4, R99: Too many digits in PCS 1900 for the Called
Party BCD number
Doc.Name C6-050246 Allocations: Content Type:
File Name: C6-050246.zip
Source: Rohde & Schwarz, 7 layers AG
 
Abstract: A 3G ME shall neither access EFADN nor EFEXT1 under MF\DFTELECOM. EFEXT1 contains extension data of ADN, the 3G ME shall not access this file under MF\DFTELECOM. This behaviour is not mentioned in the specification DOCUMENT: CR 31.102 Rel-4: 3G ME access to EF_EXT1 under DF_TELECOM Le
vel
Doc.Name C6-050247 Allocations: Content Type:
File Name: C6-050247.zip, zip
Source: Infineon Technologies
Abstract: A 3G ME shall neither access EFADN nor EFEXT1 under MF\DFTELECOM. EFEXT1 contain
s extension data of ADN, the 3G ME shall not access this file under MF\DFTELECOM
. This behaviour is not mentioned in the specification
 
Abstract: A 3G ME shall neither access EFADN nor EFEXT1 under MF\DFTELECOM. EFEXT1 contains extension data of ADN, the 3G ME shall not access this file under MF\DFTELECOM. This behaviour is not mentioned in the specification. DOCUMENT: CR 31.102 Rel-5: 3G ME access to EF_EXT1 under DF_TELECOM L
evel
Doc.Name C6-050248 Allocations: Content Type:
File Name: C6-050248.zip, zip,,
Source: Infineon Technologies
Abstract: A 3G ME shall neither access EFADN nor EFEXT1 under MF\DFTELECOM. EFEXT1 contain
s extension data of ADN, the 3G ME shall not access this file under MF\DFTELECOM
. This behaviour is not mentioned in the specification.
 
Abstract: A 3G ME shall neither access EFADN nor EFEXT1 under MF\DFTELECOM. EFEXT1 contains extension data of ADN, the 3G ME shall not access this file under MF\DFTELECOM. This behaviour is not mentioned in the specification. DOCUMENT: CR 31.102 Rel-6: 3G ME access to EF_EXT1 under DF_TELECOM L
evel
Doc.Name C6-050249 Allocations: Content Type:
File Name: C6-050249.zip, zip,,
Source: Infineon Technologies
Abstract: A 3G ME shall neither access EFADN nor EFEXT1 under MF\DFTELECOM. EFEXT1 contain
s extension data of ADN, the 3G ME shall not access this file under MF\DFTELECOM
. This behaviour is not mentioned in the specification.
 
Abstract: A 3G ME shall neither access EFADN nor EFEXT1 under MF\DFTELECOM. EFEXT1 contains extension data of ADN, the 3G ME shall not access this file under MF\DFTELECOM. This behaviour is not mentioned in the specification DOCUMENT: CR 31.102 Rel-7: 3G ME access to EF_EXT1 under DF_TELECOM L
evel
Doc.Name C6-050250 Allocations: Content Type:
File Name: C6-050250.zip, zip
Source: Infineon Technologies
Abstract: A 3G ME shall neither access EFADN nor EFEXT1 under MF\DFTELECOM. EFEXT1 contain
s extension data of ADN, the 3G ME shall not access this file under MF\DFTELECOM
. This behaviour is not mentioned in the specification
 
Abstract: The description of EFARR (Access Rule Reference) under DFTELECOM is missed in the specification DOCUMENT: CR 31.102 Rel-6: Added EF_ARR under DF_TELECOM
Doc.Name C6-050251 Allocations: Content Type:
File Name: C6-050251.zip
Source: Infineon Technologies
Abstract: The description of EFARR (Access Rule Reference) under DFTELECOM is missed in th
e specification
 
Abstract: The description of EFARR (Access Rule Reference) under DFTELECOM is missed in the specification DOCUMENT: CR 31.102 Rel-7: Added EF_ARR under DF_TELECOM
Doc.Name C6-050252 Allocations: Content Type:
File Name: C6-050252.zip
Source: Infineon Technologies
Abstract: The description of EFARR (Access Rule Reference) under DFTELECOM is missed in th
e specification
 
Abstract: Service n°24 (=eMLPP) and Service n°25 (=AAeM) are defined as two services within USIM service table. The service n°25 which is required for AAeM is missed in section 5.3.11 of the susbscription related procedures DOCUMENT: CR 31.102 Rel-5: Corrections to eMLPP and AAeM
Doc.Name C6-050253 Allocations: Content Type:
File Name: C6-050253.zip, zip
Source: Infineon Technologies
Abstract: Service n°24 (=eMLPP) and Service n°25 (=AAeM) are defined as two services withi
n USIM service table. The service n°25 which is required for AAeM is missed in s
ection 5.3.11 of the susbscription related procedures
 
Abstract: Service n°24 (=eMLPP) and Service n°25 (=AAeM) are defined as two services within USIM service table. The service n°25 which is required for AAeM is missed in section 5.3.11 of the susbscription related procedures. DOCUMENT: CR 31.102 Rel-6: Corrections to eMLPP and AAeM
Doc.Name C6-050254 Allocations: Content Type:
File Name: C6-050254.zip
Source: Infineon Technologies
Abstract: Service n°24 (=eMLPP) and Service n°25 (=AAeM) are defined as two services withi
n USIM service table. The service n°25 which is required for AAeM is missed in s
ection 5.3.11 of the susbscription related procedures.
 
Abstract: Service n°24 (=eMLPP) and Service n°25 (=AAeM) are defined as two services within USIM service table. The service n°25 which is required for AAeM is missed in section 5.3.11 of the susbscription related procedures. DOCUMENT: CR 31.102 Rel-7: Corrections to eMLPP and AAeM
Doc.Name C6-050255 Allocations: Content Type:
File Name: C6-050255.zip
Source: Infineon Technologies
Abstract: Service n°24 (=eMLPP) and Service n°25 (=AAeM) are defined as two services withi
n USIM service table. The service n°25 which is required for AAeM is missed in s
ection 5.3.11 of the susbscription related procedures.
 
Abstract: The location of EFCMI  can be interpreted as following: 
Regarding chapter 10.5.16 EFCMI is located under DFTELECOM
Regarding chapter 10.7      EFCMI is located under DFGSM
DOCUMENT: CR 51.011 Rel-4: Location of EF_CMI
Doc.Name C6-050256 Allocations: Content Type:
File Name: C6-050256.zip
Source: Infineon Technologies
Abstract: The location of EFCMI can be interpreted as following:
Regarding chapter 10.5.16 EFCMI is located under DFTELECOM
Regarding chapter 10.7 EFCMI is located under DFGSM
 
Abstract: The abbreviations regarding WLAN are incomplete
Several references and descriptions of the WLAN files are incomplete.
The mimimum number of PLMN entries in WLAN files should be – regarding TS 24.234 – 10 entries, not as specified in TS 31.102 - 8 entries. 
DOCUMENT: CR 31.102 Rel-6: Modifications regarding WLAN
Doc.Name C6-050257 Allocations: Content Type:
File Name: C6-050257.zip
Source: Infineon Technologies / Siemens
Abstract: The abbreviations regarding WLAN are incomplete
Several references and descriptions of the WLAN files are incomplete.
The mimimum number of PLMN entries in WLAN files should be – regarding TS 24.234
– 10 entries, not as specified in TS 31.102 - 8 entries.
 
Abstract: The abbreviations regarding WLAN are incomplete
Several references and descriptions of the WLAN files are incomplete.
The mimimum number of PLMN entries in WLAN files should be – regarding TS 24.234 – 10 entries, not as specified in TS 31.102 - 8 entries. 
DOCUMENT: CR 31.102 Rel-7: Modifications regarding WLAN
Doc.Name C6-050258 Allocations: Content Type:
File Name: C6-050258.zip
Source: Infineon Technologies / Siemens
Abstract: The abbreviations regarding WLAN are incomplete
Several references and descriptions of the WLAN files are incomplete.
The mimimum number of PLMN entries in WLAN files should be – regarding TS 24.234
– 10 entries, not as specified in TS 31.102 - 8 entries.
 
Abstract: Testsequences for successfully display icons of “item data objects” for the commands “Set Up Menu” and “Select Item” are missing in the test-specification. 
Regarding TS 11.14, cl. 6.6.7: DOCUMENT: CR 11.10-4 R99: Modification display icons in Setup Menu and
Select Item
Doc.Name C6-050259 Allocations: Content Type:
File Name: C6-050259.zip
Source: Infineon Technologies / Siemens / ORGA Test Systems
Abstract: Testsequences for successfully display icons of “item data objects” for the comm
ands “Set Up Menu” and “Select Item” are missing in the test-specification.
Regarding TS 11.14, cl. 6.6.7: "The SIM may provide a title icon identifier data
object and/or an item icon identifier list data object. The item icon identifie
r data object contains an icon identifier for each item."
Verification of icon display needs to be corrected, as e.g. Expected Sequence 4.
2A (SET UP MENU, BASIC ICON SELF EXPLANATORY in ALPHA ID and ITEMS DATA OBJECTS,
successful), Step 8 contains the requirement "Display "Item 1", "Item 2", "Item
3"", though the successful display of a self explanatory icon shall be tested.
Therefore the verification requirement is in contradiction to the test purpose.
Further sequences need to be aligned.
 
Abstract: Testsequences for successfully display icons of “item data objects” for the commands “Set Up Menu” and “Select Item” are missing in the test-specification. 
Regarding ETSI 102.223, cl. 6.6.7: DOCUMENT: CR 31.124 Rel-6: Modification display icons in Setup Menu an
d Select Item
Doc.Name C6-050260 Allocations: Content Type:
File Name: C6-050260.zip
Source: Infineon Technologies / Siemens / ORGA Test Systems
Abstract: Testsequences for successfully display icons of “item data objects” for the comm
ands “Set Up Menu” and “Select Item” are missing in the test-specification.
Regarding ETSI 102.223, cl. 6.6.7: "The UICC may provide a title icon identifier
data object and/or an item icon identifier list data object. The item icon iden
tifier data object contains an icon identifier for each item.”
Verification of icon display needs to be corrected, as e.g. Expected Sequence 4.
2A (SET UP MENU, BASIC ICON SELF EXPLANATORY in ALPHA ID and ITEMS DATA OBJECTS,
successful), Step 8 contains the requirement "Display "Item 1", "Item 2", "Item
3"", though the successful display of a self explanatory icon shall be tested.
Therefore the verification requirement is in contradiction to the test purpose.
Further sequences need to be aligned.
 
Abstract: The coding of Byte 15 in Event Download – MT CALL 1.1.2 is not inline with the logical description DOCUMENT: CR 11.10-4 R99: Correction of coding in MT Call Event
Doc.Name C6-050261 Allocations: Content Type:
File Name: C6-050261.zip
Source: Infineon Technologies / Siemens / ORGA Test Systems
Abstract: The coding of Byte 15 in Event Download – MT CALL 1.1.2 is not inline with the l
ogical description
 
Abstract: The coding of Byte 15 in Event Download – MT CALL 1.1.2 is not inline with the logical description DOCUMENT: CR 31.124 Rel-6: Correction of coding in MT Call Event
Doc.Name C6-050262 Allocations: Content Type:
File Name: C6-050262.zip
Source: Infineon Technologies / Siemens / ORGA Test Systems
Abstract: The coding of Byte 15 in Event Download – MT CALL 1.1.2 is not inline with the l
ogical description
 
Abstract: DOCUMENT: CR to 31.115 rel-7: Introduction of secured data download fo
r USSD
Doc.Name C6-050263 Allocations: Content Type:
File Name: C6-050263.zip
Source: Axalto
 
Abstract: DOCUMENT: CR to 31.111 rel-7: Clarification on the coding of the DCS f
ield for USSD data download
Doc.Name C6-050264 Allocations: Content Type:
File Name: C6-050264.zip
Source: Axalto
 
Abstract: DOCUMENT: CR to 31.130 rel-7: Addition of new events EVENT_FORMATTED_U
SSD and EVENT_UNFORMATTED_USSD
Doc.Name C6-050265 Allocations: Content Type:
File Name: C6-050265.zip
Source: Axalto
 
Abstract: DOCUMENT: CR to 31.102 rel-6: Alignment of MBMS procedures with TS 33.
246
Doc.Name C6-050266 Allocations: Content Type:
File Name: C6-050266.zip
Source: Axalto, Gemplus
 
Abstract: DOCUMENT: CR to 31.116 rel-6: Introduction of an explicit description
of the ISIM RFM mechanism
Doc.Name C6-050267 Allocations: Content Type:
File Name: C6-050267.zip
Source: Axalto, Cingular, Gemplus
 
Abstract: DOCUMENT: CR to 23.048 rel-5: Introduction of an explicit description
of the ISIM RFM mechanism
Doc.Name C6-050268 Allocations: Content Type:
File Name: C6-050268.zip
Source: Axalto, Cingular, Gemplus
 
Abstract: DOCUMENT: CR to 31.102 rel-7: Alignment of MBMS procedures with TS 33.
246
Doc.Name C6-050269 Allocations: Content Type:
File Name: C6-050269.pdf, zip,,
Source: Axalto, Gemplus
 
Abstract: DOCUMENT: CR 31.111 R7: Extention of BIP bearers with I-WLAN
Doc.Name C6-050270 Allocations: Content Type:
File Name: C6-050270.zip
Source: Axalto
 
Abstract: DOCUMENT: CR 31.124 Rel-6: Too many digits in PCS 1900 for the Called
Party BCD number
Doc.Name C6-050271 Allocations: Content Type:
File Name: C6-050271.zip
Source: 7 layers AG
 
Abstract: DOCUMENT: CR 31.121 Rel-4: Correction to range of available branches i
n TC 7.4.2
Doc.Name C6-050272 Allocations: Content Type:
File Name: C6-050272.zip
Source: 7 layers AG
 
Abstract: DOCUMENT: CR 31.121 Rel-5: Correction to range of available branches i
n TC 7.4.2
Doc.Name C6-050273 Allocations: Content Type:
File Name: C6-050273.zip
Source: 7 layers AG
 
Abstract: DOCUMENT: CR 31.121 Rel-4: Correction of the content for Class 1 short
messages in TC 8.2.1
Doc.Name C6-050274 Allocations: Content Type:
File Name: C6-050274.zip
Source: 7 layers AG
 
Abstract: DOCUMENT: CR 31.121 Rel-5: Correction of the content for Class 1 short
messages in TC 8.2.1
Doc.Name C6-050275 Allocations: Content Type:
File Name: C6-050275.zip, zip,,
Source: 7 layers AG
 
Abstract: Current Terms of Reference for T3, to be used as draft for new ToRs for CT6. DOCUMENT: Terms of Reference for T3 (current version)
Doc.Name C6-050276 Allocations: Content Type:
File Name: C6-050276.zip
Source: ETSI Secretariat
Abstract: Current Terms of Reference for T3, to be used as draft for new ToRs for CT6.
 
Abstract: DOCUMENT: CR 31.111 R6: Clarification for SMS PP Data Download
Doc.Name C6-050279 Allocations: Content Type:
File Name: C6-050279.zip
Source: Axalto
 
Abstract: Former C6-050237. Only change of authors due to discussion if local phonebook support is optional or mandatory DOCUMENT: CR 31.121 R99: Introduction of phonebook selection/ local ph
onebook handling tests
Doc.Name C6-050280 Allocations: Content Type:
File Name: C6-050280.zip
Source: Rapporteur (OTS), Gemplus, Toshiba
Abstract: Former C6-050237. Only change of authors due to discussion if local phonebook su
pport is optional or mandatory
 
Abstract: Former C6-050238. Only change of authors due to discussion if local phonebook support is optional or mandatory DOCUMENT: CR 31.121 Rel-4: Introduction of phonebook selection/ local
phonebook handling tests
Doc.Name C6-050281 Allocations: Content Type:
File Name: C6-050281.zip
Source: Rapporteur (OTS), Gemplus, Toshiba
Abstract: Former C6-050238. Only change of authors due to discussion if local phonebook su
pport is optional or mandatory
 
Abstract: Former C6-050239. Only change of authors due to discussion if local phonebook support is optional or mandatory DOCUMENT: CR 31.121 Rel-5: Introduction of phonebook selection/ local
phonebook handling tests
Doc.Name C6-050282 Allocations: Content Type:
File Name: C6-050282.zip
Source: Rapporteur (OTS), Gemplus, Toshiba
Abstract: Former C6-050239. Only change of authors due to discussion if local phonebook su
pport is optional or mandatory
 
Abstract: DOCUMENT: LS on Testing of terminals supporting card applications (GP-
051095)
Doc.Name C6-050283 Allocations: Content Type:
File Name: C6-050283.zip, zip
Source: GP
 
Abstract: DOCUMENT: LS on naming convention (SCaG Doc 34_016)
Doc.Name C6-050284 Allocations: Content Type:
File Name: C6-050284.zip
Source: SCaG
 
Abstract: DOCUMENT: CT6 SWG API Testing TS 31.213 presentation
Doc.Name C6-050285 Allocations: Content Type:
File Name: C6-050285.zip
Source: Chairman
 
Abstract: DOCUMENT: LS on AoC and SCUDIF interaction (S1-050481)
Doc.Name C6-050286 Allocations: Content Type:
File Name: C6-050286.zip
Source: S1
 
Abstract: DOCUMENT: LS on Service Parameters management (S1-050520)
Doc.Name C6-050287 Allocations: Content Type:
File Name: C6-050287.zip, zip
Source: S1
 
Abstract: DOCUMENT: CR 31.130 Rel-7: Introduction of new uicc.isim.access packag
e
Doc.Name C6-050288 Allocations: Content Type:
File Name: C6-050288.zip
Source: Axalto
 
Abstract: DOCUMENT: LS on Service Provider Name (S1-050533)
Doc.Name C6-050289 Allocations: Content Type:
File Name: C6-050289.zip
Source: S1
 
Abstract: DOCUMENT: LS on MBMS work progress (S3-050136)
Doc.Name C6-050290 Allocations: Content Type:
File Name: C6-050290.zip
Source: S3
 
Abstract: DOCUMENT: LS on AoC and SCUDIF interaction (S5-054285)
Doc.Name C6-050291 Allocations: Content Type:
File Name: C6-050291.zip
Source: S5
 
Abstract: 11..11 references updated to 7816-series revision DOCUMENT: CR to 11.11 R99 ISO/IEC 7816-series revision
Doc.Name C6-050292 Allocations: Content Type:
File Name: C6-050292.zip
Source: Nokia
Abstract: 11..11 references updated to 7816-series revision
 
Abstract: 51.011 references update due to 7816-series revision DOCUMENT: CR to 51.011 R99 ISO/IEC 7816-series revision
Doc.Name C6-050293 Allocations: Content Type:
File Name: C6-050293.zip
Source: Nokia
Abstract: 51.011 references update due to 7816-series revision
 
Abstract: 31.101 reference updates due to ISO/IEC 7816-series revision DOCUMENT: CR to 31.101 Rel-6 ISO/IEC 7816-series revision
Doc.Name C6-050294 Allocations: Content Type:
File Name: C6-050294.zip
Source: Nokia
Abstract: 31.101 reference updates due to ISO/IEC 7816-series revision
 
Abstract: 31.102 reference updates due to ISO/IEC 7816-series revision  
DOCUMENT: CR to 31.102 R99 ISO/IEC 7816-series revision
Doc.Name C6-050295 Allocations: Content Type:
File Name: C6-050295.zip
Source: Nokia
Abstract: 31.102 reference updates due to ISO/IEC 7816-series revision
 
Abstract: 31.102 reference updates due to ISO/IEC 7816-series revision DOCUMENT: CR to 31.102 Rel-4 ISO/IEC 7816-series revision
Doc.Name C6-050296 Allocations: Content Type:
File Name: C6-050296.zip
Source: Nokia
Abstract: 31.102 reference updates due to ISO/IEC 7816-series revision
 
Abstract: 31.102 reference updates due to ISO/IEC 7816-series revision  
DOCUMENT: CR to 31.102 Rel-5 ISO/IEC 7816-series revision
Doc.Name C6-050297 Allocations: Content Type:
File Name: C6-050297.zip
Source: Nokia
Abstract: 31.102 reference updates due to ISO/IEC 7816-series revision
 
Abstract: 31.102 reference updates due to ISO/IEC 7816-series revision DOCUMENT: CR to 31.102 Rel-6 ISO/IEC 7816-series revision
Doc.Name C6-050298 Allocations: Content Type:
File Name: C6-050298.zip
Source: Nokia
Abstract: 31.102 reference updates due to ISO/IEC 7816-series revision
 
Abstract: 31.102 reference updates due to ISO/IEC 7816-series revision  
DOCUMENT: CR to 31.102 Rel-7 ISO/IEC 7816-series revision
Doc.Name C6-050299 Allocations: Content Type:
File Name: C6-050299.zip
Source: Nokia
Abstract: 31.102 reference updates due to ISO/IEC 7816-series revision
 
Abstract: 31.103 reference updates due to ISO/IEC 7816-series revision  
DOCUMENT: CR to 31.103 Rel-5 ISO/IEC 7816-series revision
Doc.Name C6-050300 Allocations: Content Type:
File Name: C6-050300.zip
Source: Nokia
Abstract: 31.103 reference updates due to ISO/IEC 7816-series revision
 
Abstract: 31.103 reference updates due to ISO/IEC 7816-series revision DOCUMENT: CR to 31.103 Rel-6 ISO/IEC 7816-series revision
Doc.Name C6-050301 Allocations: Content Type:
File Name: C6-050301.zip
Source: Nokia
Abstract: 31.103 reference updates due to ISO/IEC 7816-series revision
 
Abstract: DOCUMENT: CR to 31.111 Clarification on additional TERMINAL PROFILE
Doc.Name C6-050302 Allocations: Content Type:
File Name: C6-050302.zip
Source: NTT DoCoMo
 
Abstract: DOCUMENT: CR 31.121 R99: Introduction of SDN tests
Doc.Name C6-050304 Allocations: Content Type:
File Name: C6-050304.zip
Source: NTT DoCoMo, Rapporteur (OTS)
 
Abstract: DOCUMENT: CR to 31 102 rel-6: Number of stored MSKs
Doc.Name C6-050305 Allocations: Content Type:
File Name: C6-050305.zip, zip
Source: Axalto
 
Abstract: DOCUMENT: CR to 31 102 rel-7: Number of stored MSKs
Doc.Name C6-050306 Allocations: Content Type:
File Name: C6-050306.zip
Source: Axalto
 
Abstract: DOCUMENT: CR 31.121 Rel-4: Introduction of SDN tests
Doc.Name C6-050307 Allocations: Content Type:
File Name: C6-050307.zip
Source: NTT DoCoMo, Rapporteur (OTS)
 
Abstract: DOCUMENT: CR 31.121 Rel-5: Introduction of SDN tests
Doc.Name C6-050308 Allocations: Content Type:
File Name: C6-050308.zip
Source: NTT DoCoMo, Rapporteur (OTS)
 
Abstract: DOCUMENT: CR 31.121 R99: Extension of phonebook tests
Doc.Name C6-050309 Allocations: Content Type:
File Name: C6-050309.zip
Source: NTT DoCoMo, Rapporteur (OTS)
 
Abstract: DOCUMENT: CR 31.121 Rel-4: Extension of phonebook tests
Doc.Name C6-050310 Allocations: Content Type:
File Name: C6-050310.zip
Source: NTT DoCoMo, Rapporteur (OTS)
 
Abstract: DOCUMENT: CR to 31 102 rel-7: Clarification on ADM access condition
Doc.Name C6-050311 Allocations: Content Type:
File Name: C6-050311.zip
Source: Axalto
 
Abstract: DOCUMENT: CR 31.121 Rel-5: Extension of phonebook tests
Doc.Name C6-050312 Allocations: Content Type:
File Name: C6-050312.zip
Source: NTT DoCoMo, Rapporteur (OTS)
 
Abstract: DOCUMENT: CR to 31 102 rel-6: Editorial corrections in TS 31 102
Doc.Name C6-050313 Allocations: Content Type:
File Name: C6-050313.zip, zip
Source: Axalto
 
Abstract: DOCUMENT: CR to 31 102 rel-7: Editorial corrections in TS 31 102
Doc.Name C6-050314 Allocations: Content Type:
File Name: C6-050314.zip
Source: Axalto
 
Abstract: DOCUMENT: LS to 3GPP2 on: ICCID uniqueness
Doc.Name C6-050315 Allocations: Content Type:
File Name: C6-050315.zip
Source: Axalto
 
Abstract: DOCUMENT: LS to 3GPP2 on: Clarifications on 3GPP CT6 specifications
Doc.Name C6-050316 Allocations: Content Type:
File Name: C6-050316.zip
Source: Axalto
 
Abstract: DOCUMENT: CR to GSM 11.11 Rel-99: Editorial changes
Doc.Name C6-050317 Allocations: Content Type:
File Name: C6-050317.zip, zip
Source: Rapporteur
 
Abstract: DOCUMENT: CR to 51.011 Rel-4: Editorial changes
Doc.Name C6-050318 Allocations: Content Type:
File Name: C6-050318.zip
Source: Rapporteur
 
Abstract: DOCUMENT: Status of CT6 deliverables and Work Items
Doc.Name C6-050319 Allocations: Content Type:
File Name: C6-050319.zip
Source: MCC
 
Abstract: DOCUMENT: CR to 31.103 rel-6: Editorial changes
Doc.Name C6-050320 Allocations: Content Type:
File Name: C6-050320.zip
Source: Axalto
 
Abstract: DOCUMENT: CR 11.10-4 R99: Essential Corrections
Doc.Name C6-050321 Allocations: Content Type:
File Name: C6-050321.zip
Source: Anite
 
Abstract: DOCUMENT: CR 21.111 ISO/IEC 7816-Series Revision (R99)
Doc.Name C6-050323 Allocations: Content Type:
File Name: C6-050323.zip
Source: Rapporteur
 
Abstract: DOCUMENT: CR 21.111 ISO/IEC 7816-Series Revision (Rel-4)
Doc.Name C6-050324 Allocations: Content Type:
File Name: C6-050324.zip
Source: Rapporteur
 
Abstract: DOCUMENT: CR 21.111 ISO/IEC 7816-Series Revision (Rel-5)
Doc.Name C6-050325 Allocations: Content Type:
File Name: C6-050325.zip
Source: Rapporteur
 
Abstract: DOCUMENT: CR 21.111 ISO/IEC 7816-Series Revision (Rel-6)
Doc.Name C6-050326 Allocations: Content Type:
File Name: C6-050326.zip
Source: Rapporteur
 
Abstract: Misalignment of 31.102 EF-EHPLMN with EHPLMN requirements in 23.122 DOCUMENT: CR 31.102 - Correction to EF-HPLMN
Doc.Name C6-050327 Allocations: Content Type:
File Name: C6-050327.zip
Source: Cingular Wireless
Abstract: Misalignment of 31.102 EF-EHPLMN with EHPLMN requirements in 23.122
 
Abstract: DOCUMENT: CR 51013 Correction of TP-DCS used for uncompressed 8 bits d
ata SMS envelope (Rel-5)
Doc.Name C6-050328 Allocations: Content Type:
File Name: C6-050328.zip, zip
Source: Rapporteur
 
Abstract: DOCUMENT: CR 51.013 Correction of FWK_ERP_EFSE script file syntax (Rel
-5)
Doc.Name C6-050329 Allocations: Content Type:
File Name: C6-050329.zip
Source: Rapporteur
 
Abstract: DOCUMENT: CR 51.013 Correction of security level in API_2_ENH_GSDL tes
t (Rel-5)
Doc.Name C6-050330 Allocations: Content Type:
File Name: C6-050330.zip
Source: Rapporteur
 
Abstract: DOCUMENT: CT 51.013 Restore files content in API_1_SVW_UPDRSBS_BSS_1.c
lr file (Rel-5)
Doc.Name C6-050331 Allocations: Content Type:
File Name: C6-050331.zip
Source: Rapporteur
 
Abstract: DOCUMENT: CR 02.19 R98 ISO/IEC 7816-series revision
Doc.Name C6-050332 Allocations: Content Type:
File Name: C6-050332.zip
Source: Sun Microsystems
 
Abstract: DOCUMENT: CR 02.19 R99 ISO/IEC 7816-series revision
Doc.Name C6-050333 Allocations: Content Type:
File Name: C6-050333.zip
Source: Sun Microsystems
 
Abstract: DOCUMENT: CR 42.019 R4 ISO/IEC 7816-series revision
Doc.Name C6-050334 Allocations: Content Type:
File Name: C6-050334.zip
Source: Sun Microsystems
 
Abstract: DOCUMENT: CR 42.019 R5 ISO/IEC 7816-series revision
Doc.Name C6-050335 Allocations: Content Type:
File Name: C6-050335.zip
Source: Sun Microsystems
 
Abstract: DOCUMENT: CR to 31.102 for discussion: Define new bits in EF_PBC for P
hone Book Sychronization
Doc.Name C6-050336 Allocations: Content Type:
File Name: C6-050336.zip
Source: China Mobile, Giesecke & Devrient
 
Abstract: DOCUMENT: CR to TS 31.122 R99 - Correction of ISO/IEC 7816 Series Refe
rences
Doc.Name C6-050337 Allocations: Content Type:
File Name: C6-050337.zip
Source: Aspects Software
 
Abstract: DOCUMENT: CR to TS 31.122 Rel-4 - Correction of ISO/IEC 7816 Series Re
ferences
Doc.Name C6-050338 Allocations: Content Type:
File Name: C6-050338.zip
Source: Aspects Software
 
Abstract: DOCUMENT: CR to TS 31.122 Rel-4 - Release 4 Test Case Updates
Doc.Name C6-050339 Allocations: Content Type:
File Name: C6-050339.zip
Source: Aspects Software
 
135 Numbers Reserved... (7 Withdrawn)
With 0 Revisions   And   0 Addenda
Last Reservation/Withdrawal On '2005-04-26 at 06:26:00 (GMT +01:00)'

116 Files Uploaded (with Correct Filename)
Last Upload On '2005-04-22 at 16:26:50 (GMT +01:00)'