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 |
|---|---|---|---|---|---|---|---|---|---|
| S4-240014 | [FS_eiRTCW] proposed pCR list for TR 26.930 | other | NTT |
S4-127 AI: 10.9 |
noted | [WTS] [JSN] | |||
| S4-240015 | [FS_eiRTCW] Pseudo-CR on clarification of Scope | pCR | NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] |
| S4-240016 | [FS_eiRTCW] Pseudo-CR on updating Key Issue #1 and Solution #1 |
pCR revised to S4-240327 |
NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
revised | [WTS] [JSN] |
| S4-240017 | [FS_eiRTCW] Pseudo-CR on updating Solution #2 | pCR | NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] |
| S4-240018 | [FS_eiRTCW] Pseudo-CR on Key Issue #5: Functional requirements for service control API | pCR | NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] |
| S4-240019 | [FS_eiRTCW] Pseudo-CR on Solution #5: Procedures for service control API | pCR | NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] |
| S4-240020 | [FS_eiRTCW] Pseudo-CR on clarification of the description for KI#6: WSF discovery mechanism | pCR | NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] |
| S4-240021 | [FS_eiRTCW] Pseudo-CR on security considerations | pCR | NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] |
| S4-240022 | [FS_eiRTCW] Pseudo-CR on Key Issue #11 and solution #11: Related groups considerations | pCR | NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] |
| S4-240023 | [FS_eiRTCW] Pseudo-CR on Conclusion of FS_eiRTCW (excluding state-3 aspect) |
pCR revised to S4-240364 |
NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
revised | [WTS] [JSN] |
| S4-240024 | [FS_eiRTCW] Pseudo-CR on Annex A: Use cases | pCR | NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] |
| S4-240025 | [FS_eiRTCW] Draft TR 26.930 v0.3.0 | discussion | NTT | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
noted | [WTS] [JSN] | |
| S4-240040 | [FS_eiRTCW] Pseudo-CR on Key Issue #9 and Solution #9 : Tethered cases |
pCR revised to S4-240333 |
NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
revised | [WTS] [JSN] |
| S4-240041 | [FS_eiRTCW] Pseudo-CR on Key Issue #7 and Solution #7: Interworking with IMS network |
pCR revised to S4-240334 |
NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
revised | [WTS] [JSN] |
| S4-240042 | [FS_eiRTCW] Pseudo-CR on Key Issue #8 and Solution #8: Protocol-level interworking between RTC network and IMS network |
pCR revised to S4-240335 |
NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
revised | [WTS] [JSN] |
| S4-240061 | [FS_eiRTCW] Pseudo-CR on Annex C: Call flow examples for RTC-IMS interworking | pCR | NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] |
| S4-240137 | [FS_eiRTCW] Pseudo-CR on Solution #5: Service control API | pCR | NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
withdrawn | [WTS] [JSN] |
| S4-240169 | FS_eiRTCW Permanent Document v9.0.0 | other | NTT | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] | |
| S4-240185 | [FS_eiRTCW] Pseudo-CR on Solution #5: API and solution evaluation for service control API | pCR | NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] |
| S4-240192 | [FS_eiRTCW] Pseudo-CR on Solution #3 C-Plane signalling protocol | pCR | NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] |
| S4-240193 | [FS_eiRTCW] Pseudo-CR on Conclusion of FS_eiRTCW (stage-3 aspect) | pCR | NTT | 26.93 0.3.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
merged | [WTS] [JSN] |
| S4-240295 | [FS_eiRTCW] Draft TR 26.930 v0.3.0 |
draft TR revised to S4-240340 |
NTT | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
revised | [WTS] [JSN] | |
| S4-240327 | [FS_eiRTCW] Pseudo-CR on updating Key Issue #1 and Solution #1 |
pCR revision of S4-240016 |
NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] |
| S4-240333 | [FS_eiRTCW] Pseudo-CR on Key Issue #9 and Solution #9 : Tethered cases |
pCR revision of S4-240040 |
NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] |
| S4-240334 | [FS_eiRTCW] Pseudo-CR on Key Issue #7 and Solution #7: Interworking with IMS network |
pCR revision of S4-240041 |
NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] |
| S4-240335 | [FS_eiRTCW] Pseudo-CR on Key Issue #8 and Solution #8: Protocol-level interworking between RTC network and IMS network |
pCR revision of S4-240042 |
NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] |
| S4-240364 | [FS_eiRTCW] Pseudo-CR on Conclusion of FS_eiRTCW |
pCR revision of S4-240023 |
NTT | 26.93 0.2.0 | FS_eiRTCW | Rel-18 |
S4-127 AI: 10.9 |
agreed | [WTS] [JSN] |
27 documents (0.37186503410339 seconds)