Please enter the search related information in the fields below. Partial information works, e.g. "SP-21" in the "tdoc" field lists all TSG SA documents from 2021. Regular expressions mostly work in all fields (e.g. "2[34].501" in the "Spec" field lists all documents related to 23.501 and 24.501. Capitalization is disregarded, i.e. "3GPP" gives the same results as "3gpp".
Download results in JSON format
| tdoc | Title | Type / Revs | Source | Spec / CR | S/WID | Release | Meeting | Status | Links |
|---|---|---|---|---|---|---|---|---|---|
| R3-196549 | (TP for NPN BL CR 38.300) Access Control Aspects on NPN |
other revised to R3-197589 |
Nokia, Nokia Shanghai Bell |
R3-106 AI: 16.2.2.1 |
revised | [WTS] [JSN] | |||
| R3-196550 | (TP for NPN BL CR for 38.413) Access control aspects of NPN |
other revised to R3-197590 |
Nokia, Nokia Shanghai Bell |
R3-106 AI: 16.2.2.1 |
revised | [WTS] [JSN] | |||
| R3-196805 | Discussion on access control | discussion | Qualcomm Incorporated | NG_RAN_PRN | Rel-16 |
R3-106 AI: 16.2.2.1 |
available | [WTS] [JSN] | |
| R3-196824 | Discussion on initial access procedure in NPN | discussion | LG Electronics |
R3-106 AI: 16.2.2.1 |
available | [WTS] [JSN] | |||
| R3-196861 | TP for initial UE message for NPN over NG interface | other | China Telecommunication | NG_RAN_PRN | Rel-16 |
R3-106 AI: 16.2.2.1 |
available | [WTS] [JSN] | |
| R3-197000 | Consideration on NPN subscription expiration handling in Connected mode | discussion | ZTE Corporation | Rel-16 |
R3-106 AI: 16.2.2.1 |
available | [WTS] [JSN] | ||
| R3-197010 | Draft LS to SA2 for NPN subscription expiration handling |
LS out LS To: SA2 |
ZTE Corporation | Rel-16 |
R3-106 AI: 16.2.2.1 |
reserved | [WTS] [JSN] | ||
| R3-197011 | Draft LS to SA2 for NPN subscription expiration handling |
LS out LS To: SA2 |
ZTE Corporation | Rel-16 |
R3-106 AI: 16.2.2.1 |
available | [WTS] [JSN] | ||
| R3-197049 | (TP for NPN BL CR for TS 38.413): Initial UE message for NPN | other | Huawei | NG_RAN_PRN | Rel-16 |
R3-106 AI: 16.2.2.1 |
available | [WTS] [JSN] | |
| R3-197050 | [Draft] Reply LS on sending CAG ID in NAS layer |
LS out source LS: R3-194926 LS To: SA3 |
Huawei | NG_RAN_PRN | Rel-16 |
R3-106 AI: 16.2.2.1 |
available | [WTS] [JSN] | |
| R3-197153 | Discussion on open issue for access control in NG-RAN |
discussion revised to R3-197517 |
CATT | Rel-16 |
R3-106 AI: 16.2.2.1 |
revised | [WTS] [JSN] | ||
| R3-197154 | (TP for NPN Stage2 BL CR) Support for initiall access control in Non-Public Networks | other | CATT | Rel-16 |
R3-106 AI: 16.2.2.1 |
noted | [WTS] [JSN] | ||
| R3-197155 | (TP for NPN NGAP BL CR)support of Iniitial access control in Non-Public Networks | other | CATT | Rel-16 |
R3-106 AI: 16.2.2.1 |
available | [WTS] [JSN] | ||
| R3-197355 | On Initial UE Message related aspects for NPN | discussion | Ericsson | NG_RAN_PRN | Rel-16 |
R3-106 AI: 16.2.2.1 |
available | [WTS] [JSN] | |
| R3-197356 | [Draft] Reply LS on Sending CAG ID in NAS layer |
LS out LS To: SA3, SA2, RAN2 revised to R3-197591 |
Ericsson | NG_RAN_PRN | Rel-16 |
R3-106 AI: 16.2.2.1 |
revised | [WTS] [JSN] | |
| R3-197517 | Discussion on open issue for access control in NG-RAN |
discussion revision of R3-197153 |
CATT | Rel-16 |
R3-106 AI: 16.2.2.1 |
available | [WTS] [JSN] | ||
| R3-197589 | (TP for NPN BL CR 38.300) Access Control Aspects on NPN |
other revision of R3-196549 |
Nokia, Nokia Shanghai Bell |
R3-106 AI: 16.2.2.1 |
agreed | [WTS] [JSN] | |||
| R3-197590 | (TP for NPN BL CR for 38.413) Access control aspects of NPN |
other revision of R3-196550 revised to R3-197776 |
Nokia, Nokia Shanghai Bell |
R3-106 AI: 16.2.2.1 |
revised | [WTS] [JSN] | |||
| R3-197591 | Reply LS on Sending CAG ID in NAS layer |
LS out LS is reply to S3-193142 LS To: SA3, SA2, RAN2 revision of R3-197356 |
Ericsson | NG_RAN_PRN | Rel-16 |
R3-106 AI: 16.2.2.1 |
approved | [WTS] [JSN] | |
| R3-197776 | (TP for NPN BL CR for 38.413) Access control aspects of NPN |
other revision of R3-197590 |
Nokia, Nokia Shanghai Bell |
R3-106 AI: 16.2.2.1 |
agreed | [WTS] [JSN] |
20 documents (0.28307008743286 seconds)