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 |
|---|---|---|---|---|---|---|---|---|---|
| RP-161366 | LS on Key capabilities and issues to be addressed for 5G (NGMN_LS_160708; to: RAN, SA, SA1, SA2; cc: -; contact: Deutsche Telekom) |
LS in source LS: NGMN_LS_160708 LS To: RAN, SA, SA1, SA2 |
NGMN | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
noted | [WTS] [JSN] | |
| RP-161376 | LS on NR requirements (R2-165967; to: RAN; cc: -; contact: Nokia) |
LS in source LS: R2-165967 LS To: RAN LS reply in RP-161574, RP-161916 |
RAN2 | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
replied to | [WTS] [JSN] | |
| RP-161532 | Summary for email discussion [RAN#72-07] on Multicast requirements |
pCR revised to RP-161836 |
EBU | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
revised | [WTS] [JSN] | |
| RP-161542 | Text proposal to TR38.913 v0.4.0 for updating the band range of each band proxy |
pCR revised to RP-161837 |
China Mobile Com. Corporation | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
revised | [WTS] [JSN] | |
| RP-161543 | Text proposal to TR 38.913 v.0.4.0 for abbreviation definition | pCR | China Mobile Com. Corporation | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
approved | [WTS] [JSN] | |
| RP-161544 | Text proposal to TR 38.913 v0.4.0 for correction of table index | pCR | China Mobile Com. Corporation | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
approved | [WTS] [JSN] | |
| RP-161545 | Text proposal to TR 38.913 v0.4.0 for description on target of UE battery life | pCR | China Mobile Com. Corporation | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
approved | [WTS] [JSN] | |
| RP-161546 | Text proposal to TR 38.913 v0.4.0 for section 7.10 coverage |
pCR revised to RP-161838 |
China Mobile Com. Corporation | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
revised | [WTS] [JSN] | |
| RP-161547 | Text proposal to TR 38.913 v.0.4.0 for description on inter-system mobility | pCR | China Mobile Com. Corporation | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
rejected | [WTS] [JSN] | |
| RP-161574 | Proposed reply LS to RAN2 on NR requirements |
LS out LS is reply to RP-161376 LS To: RAN2 LS reply in RP-161870, RP-161885 revised to RP-161870, RP-161916 |
Nokia, Alcatel-Lucent Shanghai Bell | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
revised | [WTS] [JSN] | |
| RP-161575 | Summary of 3GPP RAN reflector discussion: [RAN#72-05] NR positioning requirements | report | Intel Corporation (UK) Ltd | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
noted | [WTS] [JSN] | |
| RP-161576 | Text proposal to TR 38.913 from email discussion: [RAN#72-05] NR positioning requirements |
pCR revised to RP-161834 |
Intel Corporation (UK) Ltd | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
revised | [WTS] [JSN] | |
| RP-161580 | pCR to TR 38.913 on Unlicensed and Shared Spectrum | pCR | Qualcomm | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
postponed | [WTS] [JSN] | |
| RP-161599 | Way forward on remaining open issues in TR38.913 based on email discussion [RAN#72-03] | discussion | NTT DOCOMO, INC. | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
noted | [WTS] [JSN] | |
| RP-161647 | TP for TR 38.913: Requirement for URLLC Reliability | pCR | KT Corp. | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
rejected | [WTS] [JSN] | |
| RP-161648 | TP for TR 38.913: Spectrum Deployment | pCR | KT Corp. | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
merged | [WTS] [JSN] | |
| RP-161650 | Discussion on eV2X requirements | discussion | LG Electronics France | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
noted | [WTS] [JSN] | |
| RP-161651 | Discussion on eV2X in 5G RAN | discussion | LG Electronics France | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
noted | [WTS] [JSN] | |
| RP-161652 | pCR to 38.913 on eV2X requirements |
pCR revised to RP-161840 |
LG Electronics France | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
revised | [WTS] [JSN] | |
| RP-161653 | Pseudo satellites | pCR | THALES | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
withdrawn | [WTS] [JSN] | |
| RP-161683 | Cost-related requirements for future massive MIMO systems | discussion | TELEFONICA S.A. | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
noted | [WTS] [JSN] | |
| RP-161684 | Area traffic capacity & User experienced data rate KPIs | pCR | Deutsche Telekom AG | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
postponed | [WTS] [JSN] | |
| RP-161685 | Considerations on NR design requirements | discussion | Qualcomm Incorporated | FS_NR_newRAT | Rel-14 |
RP-73 AI: 9.2.1 |
noted | [WTS] [JSN] | |
| RP-161686 | Reliability requirement for use case in High speed scenario |
discussion revised to RP-161807 |
ZTE Corporation | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
revised | [WTS] [JSN] | |
| RP-161688 | pCR for Reliability requirement for use case in High speed scenario |
pCR revised to RP-161808 |
ZTE Corporation | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
revised | [WTS] [JSN] | |
| RP-161691 | Discussion on NR requirement related to NR architecture | discussion | ZTE Corporation | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
noted | [WTS] [JSN] | |
| RP-161692 | pCR for NR requirement related to NR architecture | pCR | ZTE Corporation | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
rejected | [WTS] [JSN] | |
| RP-161693 | pCR on coexistence of NR with legacy RATs |
pCR revised to RP-161835 |
Huawei | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
revised | [WTS] [JSN] | |
| RP-161694 | pCR on eMBMS requirements | pCR | Huawei | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
rejected | [WTS] [JSN] | |
| RP-161695 | Discussion on RAN2 questions about 5G requirements on URLLC and LTE-NR interworking | discussion | Huawei | FS_NR_newRAT | Rel-14 |
RP-73 AI: 9.2.1 |
withdrawn | [WTS] [JSN] | |
| RP-161742 | Area traffic capacity reference values in TR 38.913 | discussion | Ericsson | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
noted | [WTS] [JSN] | |
| RP-161743 | TP for TR 38.913: Area traffic capacity and User experienced data rate | pCR | Ericsson | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
postponed | [WTS] [JSN] | |
| RP-161744 | TP for TR 38.913: Open issues |
pCR revised to RP-161866 |
Ericsson | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
revised | [WTS] [JSN] | |
| RP-161765 | Some clarifications to NR requirements | discussion | VODAFONE Group Plc | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
withdrawn | [WTS] [JSN] | |
| RP-161791 | LS on 5G work alignment (S1-162544; to: RAN, SA2; cc: SA, SA3; contact: Vodafone) |
LS in source LS: S1-162544 |
SA1 | SMARTER | Rel-15 |
RP-73 AI: 9.2.1 |
noted | [WTS] [JSN] | |
| RP-161807 | Reliability requirement for use case in High speed scenario |
discussion revision of RP-161686 |
ZTE Corporation, CATR | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
noted | [WTS] [JSN] | |
| RP-161808 | pCR for Reliability requirement for use case in High speed scenario |
pCR revision of RP-161688 revised to RP-161849 |
ZTE Corporation, CATR | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
revised | [WTS] [JSN] | |
| RP-161833 | pCR to TR 38.912 on remaining open issues | pCR | NTT DOCOMO | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
approved | [WTS] [JSN] | |
| RP-161834 | Text proposal to TR 38.913 on NR positioning requirements |
pCR revision of RP-161576 |
Intel | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
approved | [WTS] [JSN] | |
| RP-161835 | pCR on coexistence of NR with legacy RATs |
pCR revision of RP-161693 |
Huawei | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
approved | [WTS] [JSN] | |
| RP-161836 | Summary for email discussion [RAN#72-07] on Multicast requirements |
pCR revision of RP-161532 |
EBU | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
approved | [WTS] [JSN] | |
| RP-161837 | Text proposal to TR38.913 v0.4.0 for updating the band range of each band proxy |
pCR revision of RP-161542 |
China Mobile Com. Corporation | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
approved | [WTS] [JSN] | |
| RP-161838 | Text proposal to TR 38.913 v0.4.0 for section 7.10 coverage |
pCR revision of RP-161546 |
China Mobile Com. Corporation | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
approved | [WTS] [JSN] | |
| RP-161840 | pCR to 38.913 on eV2X requirements |
pCR revision of RP-161652 revised to RP-161886 |
LG Electronics France | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
revised | [WTS] [JSN] | |
| RP-161842 | Cost-related requirements for future massive MIMO systems | pCR | TELEFONICA S.A. | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
approved | [WTS] [JSN] | |
| RP-161847 | pCR to 38.913 on NR link budget | pCR | Qualcomm Incorporated | 38.913 0.4.0 | FS_NR_newRAT |
RP-73 AI: 9.2.1 |
approved | [WTS] [JSN] | |
| RP-161849 | pCR for Reliability requirement for use case in High speed scenario |
pCR revision of RP-161808 |
ZTE Corporation, CATR | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
approved | [WTS] [JSN] | |
| RP-161866 | Text proposal for TR 38.913 on Reliability requirement |
pCR revision of RP-161744 |
Ericsson | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
approved | [WTS] [JSN] | |
| RP-161870 | Proposed reply LS to RAN2 on NR requirements |
LS out LS is reply to RP-161376 LS To: RAN2 revision of RP-161574 revised to RP-161885 |
ZTE, Nokia | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
revised | [WTS] [JSN] | |
| RP-161882 | Way forward for NR eV2X | discussion | LG Electronics | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
noted | [WTS] [JSN] | |
| RP-161885 | Draft Reply LS to R2-165967 = RP-161376 on NR requirements (to: RAN2; cc: RAN1; contact: ZTE) |
LS out LS is reply to RP-161376 LS To: RAN2 revision of RP-161870 |
ZTE | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
revised | [WTS] [JSN] | |
| RP-161886 | pCR to 38.913 on eV2X requirements |
pCR revision of RP-161840 |
LG Electronics France | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
approved | [WTS] [JSN] | |
| RP-161905 | Text proposal to TR38.913 v0.4.0 for definition of band proxies below 6GHz |
pCR revised to RP-161918 |
CMCC, Sprint | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
revised | [WTS] [JSN] | |
| RP-161916 | Reply LS to R2-165967 = RP-161376 on NR requirements (to: RAN2; cc: RAN1; contact: ZTE) |
LS out LS is reply to RP-161376 LS To: RAN2 revision of RP-161574 |
RAN | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
approved | [WTS] [JSN] | |
| RP-161918 | Text proposal to TR38.913 v0.4.0 for definition of band proxies below 6GHz |
pCR revision of RP-161905 |
CMCC, Sprint | 38.913 0.4.0 | FS_NG_SReq |
RP-73 AI: 9.2.1 |
approved | [WTS] [JSN] | |
| RP-161926 | Status report for SI Study on Scenarios and Requirements for Next Generation Access Technologies | WI status report | CMCC | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
reserved | [WTS] [JSN] | |
| RP-161927 | TR 38.913 v0.4.1 on Study on Scenarios and Requirements for Next Generation Access Technologies | draft TR | CMCC | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
reserved | [WTS] [JSN] | |
| RP-161928 | TR 38.913 v1.0.0 on Study on Scenarios and Requirements for Next Generation Access Technologies | draft TR | CMCC | FS_NG_SReq | Rel-14 |
RP-73 AI: 9.2.1 |
reserved | [WTS] [JSN] |
58 documents (0.32459378242493 seconds)