The 5G Standard

3GPP TDocs (written contributions) at meeting

Meeting: S3-17 - 2001-02-27 to 2001-03-02, Gothenberg

meeting id: S3-17 (click id for more info on this meeting)

Click on the Tdoc to open its file.

TDoc Title Source Remarks
S3‑010001 - - -
S3‑010002 - - -
S3‑010003 - - -
S3‑010004 - - -
S3‑010005 - - -
S3‑010006 RES has to be a multiple of 8 bits - -
S3‑010007 - - -
S3‑010008 - - -
S3‑010009 - - -
S3‑010010 - - -
S3‑010011 - - -
S3‑010012 - - -
S3‑010013 - - -
S3‑010014 - - -
S3‑010015 - - -
S3‑010016 - - -
S3‑010017 - - -
S3‑010018 - - -
S3‑010019 - - -
S3‑010020 - - -
S3‑010021 - - -
S3‑010022 - - -
S3‑010023 - - -
S3‑010024 - - -
S3‑010025 - - -
S3‑010026 - - -
S3‑010027 - - -
S3‑010028 - - -
S3‑010029 - - -
S3‑010030 - - -
S3‑010031 - - -
S3‑010032 - - -
S3‑010033 - - -
S3‑010034 - - -
S3‑010035 - - -
S3‑010036 - - -
S3‑010037 - - -
S3‑010038 - - -
S3‑010039 - - -
S3‑010040 - - -
S3‑010041 - - -
S3‑010042 - - -
S3‑010043 - - -
S3‑010044 - - -
S3‑010045 - - -
S3‑010046 - - -
S3‑010047 - - -
S3‑010048 RES has to be a multiple of 8 bits - -
S3‑010049 IST implementation for non-CAMEL subscribers - -
S3‑010050 - - -
S3‑010051 - - -
S3‑010052 - - -
S3‑010053 - - -
S3‑010054 - - -
S3‑010055 - - -
S3‑010056 - - -
S3‑010057 - - -
S3‑010058 - - -
S3‑010059 - - -
S3‑010060 Update of TS 33.106 for release 4 - -
S3‑010061 - - -
S3‑010062 Correction of Location information parameters in interception event records - -
S3‑010063 - - -
S3‑010064 Add bit ordering convention - -
S3‑010065 Add bit ordering convention - -
S3‑010066 Add bit ordering convention - -
S3‑010067 - - -
S3‑010068 - - -
S3‑010069 - - -
S3‑010070 - - -
S3‑010071 - - -
S3‑010072 - - -
S3‑010073 - - -
S3‑010074 - - -
S3‑010075 - - -
S3‑010076 - - -
S3‑010077 - - -
S3‑010078 - - -
S3‑010079 - - -
S3‑010080 - - -
S3‑010081 - - -
S3‑010082 - - -
S3‑010083 - - -
S3‑010084 - - -
S3‑010085 - - -
S3‑010086 - - -
S3‑010087 - - -
S3‑010088 - - -
S3‑010089 - - -
S3‑010090 - - -
S3‑010091 - - -
S3‑010092 - - -
S3‑010093 - - -
S3‑010094 Timing of security mode procedure - -
S3‑010095 - - -
S3‑010096 - - -
S3‑010097 - - -
S3‑010098 - - -
S3‑010099 LS to T3: TR 31.900 - SIM/USIM Internal and External Interworking Aspects (update of TD42) S3 -
S3‑010100 - - -
S3‑010101 - - -
S3‑010102 - - -
S3‑010103 Add requesting node type to authentication data request - -
S3‑010104 Additional Parameters in Authentication Failure Report - -
S3‑010105 - - -
S3‑010106 Move of TS 33.200 - Network Domain Security from Rel?4 to Rel?5 S3 -
S3‑010107 Release 5 updates - -
S3‑010108 - - -
S3‑010109 - - -
S3‑010110 LS to CN4 on Additional Parameters in AFR procedure S3 -
S3‑010111 Minimum clock frequency updated - -
S3‑010112 - - -
S3‑010113 - - -
S3‑010114 - - -
S3‑010115 Response LS (to TD22) on multiple user identities S3 -
S3‑010116 - - -
S3‑010117 GSM ciphering capability Handling in Security Mode set up procedure - -
S3‑010118 - - -
S3‑010119 - - -
S3‑010120 - - -
S3‑010121 - - -
S3‑010122 - - -
S3‑010123 - - -
S3‑010124 Correction to the handling of re-transmitted authentication request messages on the ME - -
S3‑010125 - - -
S3‑010126 Optional Support for USIM-ME interface for GSM-Only ME - -
S3‑010127 - - -
S3‑010128 Response to LS (S1-010200) to T3 and S1 on the Elaboration of KEY IDENTIFICATION EVENT S3 -
S3‑010129 - - -
S3‑010130 - - -
S3‑010131 LS to TR-45: Clarification on positive authentication report S3 -
S3‑010132 LS to TR45 AHAG: Define responsibility and procedure S3 -
S3‑010133 LS to SA WG1 on UE functionality split over physical devices S3 -
S3‑010134 - - -
S3‑010135 Reply to LS on integrity protection for GERAN (Response to TD22) S3 -
S3‑010136 LS to TSG RAN on UE ciphering capabilities S3 -
S3‑010137 LS to T WG1 on testing UE procedures S3 -
S3‑010138 Definition corrections - -

page generated from database: 2024-03-25 09:25:51

Get news. Get knowledge. Get involved
Get news.
Get knowledge.
Get involved.
Image
The 5G Standard
3GPP General Enquiries:
info@3gpp.org 


Connect:

Quick Links